[wp-trac] [WordPress Trac] #11453: Use compression for CSS and JS file output
WordPress Trac
wp-trac at lists.automattic.com
Thu Dec 17 03:59:22 UTC 2009
#11453: Use compression for CSS and JS file output
-----------------------------+----------------------------------------------
Reporter: micasuh | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: 3.0
Component: Optimization | Version: 2.9
Severity: normal | Keywords: css, js, minify, compression
-----------------------------+----------------------------------------------
Comment(by novasource):
Denis-de-Bernardy is correct about minify if it consumes a lot of CPU.
Have to analyze on cost-benefit. At least on hosts like Dreamhost, lots of
minify could push high volume sites into mandatory private virtual host
mode.
re: concatenation--will Google's scheme include # of HTTP requests in the
speed factor? If not, then concatenation is 0 value for this purpose.
Concat is only a good idea if you have static JS or CSS files. If your
concat includes dynamic JS or CSS content, or changes on page-to-page,
then you've defeated the advantage of concat because the browser cannot
cache it.
CDN makes a lot of sense for static files on a high traffic site but only
makes sense to relieve load on primary host. You'd have to get tons and
tons and tons of hits for that to make sense, and at that point you
probably need professional services that put you in a different league.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/11453#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list