Google Page Speed Online - Part Two - The Tips Are Helping A Lot!

General Blogs

By Salar Golestanian @ Tuesday, April 05, 2011 :: 1:35 AM :: 741 Views :: 0 Comments ::

Last week I talked about Google's new tool to see 'how fast your web page is?' and salaro.com was a respectable 78. I had a quiet moment today to test some of the recommendations. Since the cacheable resources had a short freshness lifetime. So by specify an expiration at least one week in the future for the .gif, .jpg, .js and so on, I gained more than 5% improvement so now the site is as fast as wordpress.org so I am very happy. The mobile child portal iphone.salaro.com is even faster now at 85%

Here are some speed test results from last week and what they are this week:

salaro.com was 78 and now >> 89
iphone.salaro.com was 77 mobile set to false now >> 86
iphone.salaro.com was 60 with mobile set to true now >> 71
dotnetnuke.com was 72 today it is >> 65
wordpress.org last week was 83 and today is >> 78
Joomla.org last week was 42 and today is >> 41
Drupal.org last week and today >> 93
Mirosoft.com >> 78

Wow - How did that happen? that was a little too easy to beat WordPress.com and only a few points behind Drupal.

Clearly Drupal remains the king and looking at Google recommendations, one can see that they have obviously looked closely and have done what was necessary. So they have mostly done a good job. I was curious why Joomla was so bad. I was curious why Google is suggesting they should use keep alive.

expiration for iis6

However I was very excited that having spent only 5 minutes on applying just one Tip, I improved by more than 5% and now the site is running faster than WordPress.org, DotNetNuke.com, Joomla.org.

Here is what I did:

The server that we are running salaro.com on a 2003 MS server with SQL 2005. IIS 6 is not as good as IIS 7 in allowing you to do individual expiry for different items. But the globally enabling content expiration, seems to do the trick.

In IIS7 it is a little different as below and I have seen more granular approach - But this is the equivalent to above where you need to find the HTTP Response Header and add the HTTP response Header with expire of web content set at 7 days or more.

The next task is to reduce

I found this article
that seems to cover a lot of ground but it does not seem to be a 5 minute job. So finding time will be difficult for this task.

On SalarO.com we have 479.1KiB of JavaScript that is parsed during initial page load. Deferring the parsing of the JavaScript to by reduce blocking of page rendering is good idea. This is what we have on Salaro.com:

http://salaro.com/ScriptResource.axd?... (86.3KiB)
http://salaro.com/ScriptResource.axd?... (84.3KiB)
http://salaro.com/ScriptResource.axd?... (70.5KiB)
http://salaro.com/.../jquery.min.js (70.4KiB)
http://salaro.com/ScriptResource.axd?... (34.1KiB)
http://salaro.com/ScriptResource.axd?... (33.7KiB)
http://salaro.com/ScriptResource.axd?... (28.8KiB)

So I need to do some research on this subject and hope this article can help.