Possible low hanging optimization fruit

[foxfirefey]

So, I've been doing some heavy web page optimization at my day job and on a whim I ran an analyzer on some DW pages and found what I think could be a very easy-to-make-happen optimization: we're not gzipping the JS/CSS static files when we serve them.

Examples:

* The new entry page: 221.2KiB (70% reduction) -- quite the savings when the entire bundle is 349.9 KB
* My reading page: 149.3KiB (68% reduction) -- when the total page is 541.5 K, so decent

Would this be as easy to set up as I think it would, or are there other reasons not to do it?

Comments

[pauamma]

Maybe? Since they're static, I would expect the browser to cache them, so I'm not sure how
much difference it'd make. (If they're not browser-cacheable, maybe start there?)

Also. if we compress them, maybe do it at codepush time? There would be little point in gzipping them over and over again.

[foxfirefey]

They are cached--however, it could help first impressions or after code pushes and whatnot.