Looking at Google PageSpeed

Written on May 1, 2015
Estimated reading time : 7 mins
Tags : | google | performance | server |

Why was I interested in PageSpeed

  • I wanted an easy way to optimize my website - namely js & css minification & combining, keeping track of modifications on those files & cachremoval with it, increasing page load time etc.
  • I had heard some good things about Google Pagespeed & I set out to explore it.

About Google PageSpeed

  • Introduced by Google at its Google I/O conference back in 2010.
  • Set of Tools to Analyze and optimize your website :
    1. Pagespeed Service
      • Currently looks to be defunct since Google is not accepting new signups.
      • Google optimizes your web site and serves it from Google infrastructure for maximum performance
      • Expected to have a price in the future (if it goes live)
    2. Pagespeed Insight API
    3. Pagespeed Module
      • Open source module which runs on an Apache or Nginx server to automatically rewrite and optimize resources.

In this blog, I will primarily concentrate on the Pagespeed module since its the true heart of the Google Pagespeed tool set.

Pagespeed Module


  • I configured my pagespeed setup since I knew which settings would work best for my website.
  • PageSpeed brings together several capabilities like lazy loading images, image sprites, extend cache life, remove render blocking js, combine & minify js/css, move inline js/css to external files etc which are usually achievable via various plugin & adding extra code
  • The performance increase was pretty good - it reduced pageload time by 1-2 sec.
  • However I was able to achieve the same by optimizing the code myself - in a lot of places !
  • So I think Google Pagespeed is extremely useful for websites where you cannot optimize the code yourself due to lack of full knowledge on the possible impacts (eg : legacy sites).


Feel free to share this article :

submit to reddit

Add your thoughts, questions, doubts, suggestions as comments below :