Last week Google released two new tools to help people make their websites faster.
The first one is a Firefox extension called “Page Speed” which gives you a performance analysis of the website you’re viewing as well as lots of tips on how you can make the website faster if you’re the website owner.
The second one is an Apache module called “mod_pagespeed”. Enabling it in Apache causes Apache to analyze the resources it’s serving and optimize them on the fly before serving them. We have installed mod_pagespeed on all of our servers (except web1-web20 which run rhel4). It is disabled by default for all websites but if you are using a static app all you have to do to enable mod_pagespeed for your website is to add this line to your .htaccess file (or create a new .htaccess file if you don’t have one yet):
If you’re using a Django app or any other app that comes with your own Apache instance you can also easily enable mod_pagespeed like this (assuming your app is called “django” and your username is “username“):
mkdir -p $HOME/mod_pagespeed/cache/ $HOME/mod_pagespeed/files cd $HOME/webapps/django/apache2/modules cp /usr/lib/httpd/modules/mod_pagespeed_ap24.so . vi ../conf/httpd.conf # Or another editor if you think "vi" is too simple... # add the following: LoadModule pagespeed_module modules/mod_pagespeed_ap24.so ModPagespeed on SetOutputFilter MOD_PAGESPEED_OUTPUT_FILTER ModPagespeedFileCachePath "/home/username/mod_pagespeed/cache/" # save and exit cd ../bin; ./restart
Note that if you’re using Apache-2.2 the module’s path is /usr/lib/httpd/modules/mod_pagespeed.so
If you’re using your own Apache instance you can also configure which filters you want to enable or disable. If you’re using a static/php/cgi or a php-based app like WordPress, Drupal or Joomla then it is not currently possible to configure which filters you want because the current version of mod_pagespeed doesn’t seem to support filter configuration per virtual hosts. For these apps you will be using the default “core filters” chosen by Google. These are:
- add_head: adds a head to the document if it encounters a <body> tag before finding a <head> tag.
- combine_css: replaces multiple distinct CSS files with a single CSS file, containing the contents of all of them.
- rewrite_css: parses referenced and inline CSS and minifies them.
- inline_css: reduces the number of requests made by a web page by inserting the contents of small external CSS resources directly into the HTML document.
- rewrite_images: rescales, and compresses images; inlines small ones.
- insert_img_dimensions: inserts
<img>tags that lack them and sets them to the image width and height.
- extend_cache: rewrites the URL references in the HTML page to include a hash of the resource content. Thus if the site owner changes the resource content, then the URL for the rewritten resource will also change.
For the official docs on mod_pagespeed and its filters see http://code.google.com/speed/page-speed/docs/using_mod.html
Enjoy the new mod_pagespeed and let us know if you notice any difference in the loading time for your pages.
Update: Be aware that mod_pagespeed is still in beta and therefore might have some bugs. In particular we’ve had reports saying that it can saturate the number of Apache processes available for your site and cause some requests to hang. We’ll roll-out future versions as Google release them but in the mean time if mod_pagespeed is causing problems for your particular site the best thing to do is to just not enable it for your site for now.
Update 1 August 2011: Removed deprecated
Update 24 August 2015: mod_pagespeed is no longer on by default – you must use “ModPagespeed On” in your .htaccess to activate it (see above).
Update 16 June 2016: For CentOS 6 and CentOS 7 servers, the paths to the mod_pagespeed modules are:
Update 12 July 2017: Almost all customers have been migrated to CentOS7 and Apache 2.4, so the Django docs have been updated:
LoadModule pagespeed_module modules/mod_pagespeed_ap24.so
- Removed deprecated