Mod_pagespeed - Why So Hasty Just Yet?
The net’s been loud with google’s mod_pagespeed lately.
According to the project page:
This all sounds very nice, so what are my objections? Read along.
First, I’m always very critical of automatic optimisation techniques. They shade developer responsibility and awareness and can do some disastrous, unintended modifications in the background.
My points are:
- A web developer should have a clear knowledge about optimization techniques and do them in the template, css, etc.
- Don’t impose additional load on the web server just because you lack the knowledge or you’re just lazy
- There’s much more to web sites than performance. How about SEO? Are you sure that an automatic reorganization of your html source is SEO friendly? Maybe mod_pagespeed is harmless in 99% of the cases, but still TAKE A DAMN LOOK.
- mod_pagespeed can be a very nice tool supporting development, though! You can use it to check out possible optimizations, opportunities that you might have missed. Use it as some kind of HTML+CSS template generator that transforms your first-run code to something possibly more optimized which you can alter by hand.
So as a summary, I’m sure mod_pagespeed can be a very nice tool in development mode to spot possible optimization opportunities, and also for large static-html CMS, etc. providers so that big chunk of unoptimized and messy static html pile gets a major performance upgrade, but I’d encourage every web developer to do these optimizations by hand or semi-automatically.