My quest as WordPress Performance Junkie Blogger always leaves me with the question: what else i could possibly do to improve performance to by blog? Errr… without getting my hands dirty with lots of coding, APIs and IDEs. According to YSlow, the first thing i had to do was adding Expires Headers to all of my CSS backgound images, .js and .css files. Yahoo! claims that the number of page views with a primed cache is 75-85%, where a “primed cache” already contains all of the components in the page.
After reading Jeremy‘s post on How To Add Good Expires Headers to Images in Apache 1.3 i decided to move all the CSS related files from S3 back to my server. I checked if mod_expires and mod_headers modules were available for Apache and followed the instructions for Speed Up Sites with htaccess Caching.
The impact of Cache-Control is phenomenal as seen on YSlow. A visit to the home page of this blog with a Prime or Full Cache, results to only 6 HTTP requests instead of 42 or 20.9Kb transfered instead of 422.2Kb. That is 99.8% decrease is HTTP requests and 99.9% decrease in bandwidth consumption!
Amazon S3 is a great service and Paul’s idea was amazing but until i find an easy way to implement Expires Headers to files served from S3 i’ll stick with the convenience of my home made cache solution. When it comes to performance, it certainly matters what the readers perceive as faster and more responsive blog.
*This setting can be hacked. For Firefox use Fasterfox
**According to online resources is not a good idea to use more than 2 different domains. Sub domains included
[bike trick photo via]