oogle Page Speed Online – Part One – Just how fast is your web page?

oogle Page Speed Online – Part One – Just how fast is your web page?

Google Page Speed Online is very intriguing. It provides a quick and easy way to accurately measure the speed of your website directly from the web. Previously available only as a browser add-on, Google Labs launch allows you to analyze your site from anywhere and receive instant feedback on making it faster. So I thought I try it on Salaro.com currently ‘DNN 5.6.1’ before I upgrade it to version 5.6.2. I was actually rather worried before I try it. I was expecting dreadful result as the server is windows 2003 and we have not done any speed optimization. yet the result was encouraging at a score of 78 (out of 100)

There are a lot of tools online that only measure server response time, giving an inaccurate picture of your site’s speed. A Supper fast servers will return your the page fast, but visitors to may still be waiting for images to download or javascript to be executed. In contrast, Page Speed Online uses a webkit-based renderer to time all components of your site for a more complete picture of its performance.

Here are some speed test results:

    salaro.com >> 78
    iphone.salaro.com >> 77 mobile set to false
    iphone.salaro.com >> 60 with mobile set to true
    dotnetnuke.com >> 72
    wordpress.org >> 83
    Joomla.org >> 42
    Drupal.org >> 93
    http://nopcommerce.salaro.com >> 62 (runs from my broadband at home)
    Mirosoft.com >> 78

Clearly Drupal is the king. But i intend to use the help I am getting from Google to speed things up for www.salaro.com

I think Page Speed Online is an important tool for the web because it’s lowering the bar for people who are not technical and yet want to do performance analysis on their sites.  No longer does one have to download desktop software, install a plugin or even have a copy of the browser that you’re testing – Use any browser and let the tool do the job.

Details for Salaro.com are as follows:

High Priority Suggestions that wins for the least development effort:

The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:

http://salaro.com/…/loading.gif (expiration not specified)
http://salaro.com/…/container.css (expiration not specified)
…….

Medium Priority Suggestions but much more work to implement:
The following images served from salaro.com should be combined into as few images as possible using CSS sprites.
http://salaro.com/…/Menu_Hover_LT.gif
http://salaro.com/…/Menu_BG.gif
http://salaro.com/…/Menu_Left.gif
….

461.3KiB of JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering.
http://salaro.com/ScriptResource.axd?… (84.3KiB)
http://salaro.com/ScriptResource.axd?… (82.2KiB)

Low priority. Are suggestions that represent the smallest wins. You should only be concerned with these items after you’ve handled the higher-priority ones: For me I am not going to bother and just concentrate on high and medium priority as I am sure this would be enough to take it close to Druple.org result.

Minify JavaScript, Specify a cache validator, Minify CSS, Optimize the order of styles and scripts, Optimize images, Minify HTML, Put CSS in the document head, Remove query strings from static resources, Specify a Vary: Accept-Encoding header