So, even if I didn't beat his score (only for 3 points), I'm pretty happy with the results, since it's the most I can get without touching the server settings (which I can't since I'm on a shared hosting plan) or reducing the graphic richness of my blog (both skin and contents).
Plan to a better YSlow score
Even if YSlow's most important rules are Gzip the content, remove Etag and add an Expires Header, I noticed that reducing the number of components also improves a bit the score related to that rules since it reduces the number of files that are not compliant.
Here is the list of the changes I made to my blog:
- I merged all the minified files into one file
- I also merged all the CSS into just one file (leaving outside only the styles for printing)
- Then I changed the skin definition to use the Gzip handler developed by Rodiniz to serve the two merged files
I wanted to use CSS Sprites to merge the CSS background images, but that would have exceeded the 4 hour limit of the challenge, so I left it out.
Unfortunately the WebResource.axd file cannot be compressed, and this is where the B comes from for rule number 4.
This is a manual tuning, but I'm planning to automate the merging process so that all the blogs powered by Subtext can benefit from this performance improvement.
PS: Someone might say that Mads's score is not not 67 but somewhat higher: this is because if you "AutoRun" YSlow the DOM tree is parsed sometime before the onload is complete, while if you run the tool manually, it will include also everything that an onload handler might have added to the DOM. So I always tested, today and in my previous list, running YSlow manually after the page has completely loaded.