I like to base my decisions of cost/benefit analysis. mod_pagespeed consumes too much resources regarding its benefits on regular websites (i.e. sites with up to 10 million pageviews per month, without a CDN or a battery of Squid servers in front of them). Why? Because it consumes a truckload of resources to crunch down pages. The net gains (lenth-wise) are unsubstantial when compared to the benefits of GZip encoding.
However, the scale is tipped in favour of mod_pagespeed if an only if:
- You have too many visitors (more than 10M uniques per month) because the small gains are multiplied by a HUGE factor.
- You are using a Squid battery / CDN or similar approach, because mod_pagespeed will crunch through the page once, its static copy will be saved on the CDN and served as a static resource a few thousand times.
- You do not have a lot of dynamic content, because that would require mod_pagespeed to always run which, in turn, causes a performance loss which is more noticeable than its gains.
So, on the sites you and I will most likely run for the rest of our lives, mod_pagespeed makes no real sense. If you are a fan of aggressive CDN caching and don't have lots of dynamic content, then yes, mod_pagespeed will work wonders for you!
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!