Currently, Hype's export does not know what you may do with a document even if it is seemingly empty -- having an API means that we must include all API facilities.
As others have mentioned in the thread, it is a good feature request to provide more export possibilities for further size reductions -- along with a more pure and SEO-friendly HTML structure output.
Hey now 
.
Okay, it can always be optimized more -- but I will make a strong point that nearly every release we have worked quite a lot to keep the size down and find all kinds of tricks to use!
But really, there's also a point where feature variant differences may be outweighed by caching and CDN-ability.
How ads calculate weight is just plainly broken. Having n! different possibilities means that it couldn't be on a CDN, and then ends up counting as file weight in ads. And the flip side is that Hype, in trying to be intelligent about splitting up between a thin/full to only deliver on-demand the required one means both get included as ad weight, even though only one would ever go to visitors.
Sounds like this is the worst of both worlds as described above 
.
This post hopefully sheds a little more light on the analysis which determines thin vs. full: