[wp-trac] [WordPress Trac] #11453: Use compression for CSS and JS file output

[WordPress Trac]

#11453: Use compression for CSS and JS file output
-----------------------------+----------------------------------------------
 Reporter:  micasuh          |       Owner:                                     
     Type:  feature request  |      Status:  new                                
 Priority:  normal           |   Milestone:  Future Release                     
Component:  Optimization     |     Version:  2.9                                
 Severity:  normal           |    Keywords:  css, js, minify, compression, speed
-----------------------------+----------------------------------------------

Comment(by micasuh):

 Replying to [comment:10 Denis-de-Bernardy]:
 >(PHP-level gzipping and minifying) are much less so, and they're prone to
 introducing more trouble than benefits.
 Good point. Like novasource said, we should look to analyze cost benefit
 to include it or not. Are there many known problems with using
 minification scripts like YUI compressor?

 I'd make a guess that most Wordpress websites only contain only a small
 number of both static CSS and JS files. Thus, there's no increased CPU
 load if these are minified once per file and then cached to serve to end
 users. While I can't predict what kind of problems this would introduce,
 it seems that user error would lead to a big majority of problems.

 Replying to [comment:13 hakre]:
 > I've never seen google loading my CSS and JS files and I strongly doubt
 a speed-rating mechanism will rate their downloads in the future.
 Google's new algorithm, nicknamed Caffeine, will start rollout in the new
 year. Included in this newer, rebuilt search system is attention to page
 speed, as indicated in the link in the ticket description.

 I agree that Google spiders or bots probably won't rate download speeds of
 individual files. it is, however, very possible and likely to take account
 of total time and rendering speed of the sites it visits in consideration
 for ranking. If not using this method, it will use another similar method
 that Matt Cutt's hinted at in the video.

 And while I love dalmaatieur's enthusiasm, I really do hope we can target
 Wordpress 3.0 in the long-term. I'd like to change the status back to
 Milestone 3.0 if no one else opposes.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11453#comment:14>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software