Google mod_pagespeed?
Jon Stahl <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAM8toDcUaNT6s6N8=fRDvDBLNa7ozZe2L=EgtCiu00YkQ9npxA@mail.gmail.com> |
Many of you are surely familiar with Google's PageSpeed tool for diagnosing slow pages. A few years ago they put out an Apache module, mod_pagespeed to implement some of their best practices as a webserver-level set of transformations. https://developers.google.com/speed/pagespeed/module I looked at it and at the time, thought it was neat, but Plone out of the box (or with caching) already did a lot of its main best practices. And so I put it aside for a while. Recently, I was looking at it again, and was delighted to see that Google has continued to develop it very aggressively, and has added a *ton* of features that seem highly relevant to Plone sites, including: * An Ngnix module (!) * Automatic domain sharding * Highly flexible automatic image recompression and optimization * SPDY support * Javascript and CSS optimization (over and above what ResourceRegistries does) * Canonicalizing Javascript libraries (e.g. Jquery, etc.) * Lazy image loading * Automatic image spriting of CSS background images I've not seen much discussion of this in a Plone context... are folks out there using it in production deployments? Would love to hear about your experiences. Seems like it is a low-cost and very useful bag of best practices to (carefully) deploy on any site where speed matters (and isn't that most sites?). --Jon --- Jon Stahl http://jstahl.org 206.226.0818 ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk