How Optimized Are High Traffic Websites?

16 Nov 2010

I'm a performance junkie. I like to build things and use things that are fast. Performance is a feature, and if you don't stay on top of it, it'll cripple you. I've blogged about steps web developers can take to speed up their websites, and have an open source library to help ASP.NET developers build faster websites. Today, I decided to look at a few popular websites and see how well they are doing.

First, the setup. I ran this with YSlow 2.1.0, I disabled the CDN, DOM and Empty SRC rules (I thought the DOM might have an impact when comparing, say Google to Facebook, but it was negligible). The results, from fastest to slowest are:

Score: 98

Score: 98

Score: 96

Score: 96

Score: 83 (old)
Score: 94 (new)

Score: 91

Score: 86

Score: 84

Score: 77

The sites that don't have great scores largely don't combine their css/js/sprites and/or don't set expiration headers on all their assets.

I have mixed feelings about YouTube's score. On the one hand, all of these are probably irrelevant when 99% of your bandwidth and load time are videos. On the other hand, its YouTube/Google, you expect them to cross their Ts and dot their Is.

Wikipedia trailing the pack, by a considerable margin, is unfortunate. A site that sees so much traffic, is based on an open source platform, and isn't profitable should be doing much better.

Amazon's score is shocking. There's an oft cited study by amazon that showed their sales dropped 1% for every 100ms slower their page was. Maybe things have changed in 3 years and we should all stop quoting it. Amazon's homepage scores a more respectable 93, but even here there's obvious room for improvement.

Twitter has obviously worked hard to improve its load time.

Facebook didn't have the best score, but that 1 page loaded insanely fast. Obviously that tells us that YSlow's score isn't the end all and be all, but I still think its a useful tool.

Bing was another surprise. I've been critical of Microsoft's developer-focused sites, yet had no doubt that bing would do much better. I didn't think it would be the best (or even above google). This, again, makes me believe that there's a disconnect between devdiv and developers (remember, Rails has a lot of this stuff built-in).

My latest project, mogade.com scores 98. This is done through aggressive (yet simple) nginx tuning, and a small ruby library (very similiar to Metsys.WebOp for .NET) which leverages the YUI jar and this little CSS cache busting class.

blog comments powered by Disqus