Possible low hanging optimization fruit
Jan. 29th, 2013 11:39 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
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?
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?