3 ms·
> 2. compress No, you don't need to waste CPU cycles on compression for each connection. You can store the .css.gz on the filesystem along with the .css and ha
by the8472 10y ago
> 2. compress
No, you don't need to waste CPU cycles on compression for each connection. You can store the .css.gz on the filesystem along with the .css and have the webserver pick up the appropriate file based on Accept-encoding.
That way you can precompress with the slowest compression options.
- diamondo25 10y agoOf course, there are multiple ways to optimize it (like storing stuff at a CDN), but I'm pretty sure 95% of the people do not precompress their assets.