On a quest for ultimate website performance

Lately I've been diving into the world of website performance optimization. This article is the first entry in a series about website optimization.
A lot has been written on this subject already but I figured it would be great anyway to share my experiences with you all in order to consolidate what I've learned and because I may even come up with something new. You never know!
The site I'm using as a 'showcase example' for my optimization odyssey is Eurobands. I could have used my own blog but it's currently not in a very easy to maintain state and it's running a less widely known publishing system compared to the one Eurobands is using: Pivot. Eurobands is running WordPress which is used by a much larger audience which is why I figured this site would be a better candidate to dedicate my article to. My own site will get the royal treatment as soon as Pivot 2.0 comes out.
Two types of performance
There's two different ways to look at a website's performance. First of all there's raw server performance. How many page request can a server handle before it collapses under load and more important: how fast can it process them. On a high volume website this aspect of performance is very important because it determines how many users a machine can serve before additional server capacity is needed. This article is not about this kind of performance tuning. WordPress comes with a pretty robust caching engine built in which makes it perform as fast as it possibly can.
The second way to look at performance is what we could call 'perceived performance'. It's the speed at which your site appears to perform to the user. Even if your server is capable of serving all files required to render your website's pages in a visitor's browser as fast as it gets, your site may still appear slow to the user. A fast pipe doesn't necessarily result in a fast website. Slow client-side performance can have a plethora of causes. There's an awful lot to gain on the front end side of the game which is what this article is about.
(continue reading...)
Filed under: programming
Number of comments:
Number of trackbacks:
Tagged with: 






