ATTN Big Media: Web page speed matters!

July 4th, 2010 | by Sajal Kayan |

I am not a front-end kinda guy, but these days my latest obsession is to test and improve web page loading times. With this blogpost, I intend to show with examples of some selected websites and what are they doing right and what *desperately* needs to be improved. As I learn more about this I will be posting more in-depth posts on these issues.

Why does it matter?

These days almost everyone is on high-speed ‘broadband’ connections so the sites should load fast. Right? No! With faster connectivity, users get more impatient and expect websites to load faster.

E-Commerce websites have done studies which proove faster sites results in more sales. Google has also been advocating to webmasters to improve their pageload times. Now pageload is a signal for ranking in Google, abit a minor signal, but it still matters.

Overall faster websites results in a higher user retention. Faster websites also lower operational costs. Not directly related, but an optimized website is also less susceptible to Frontend SPOF.

Analysis of pageload time

My favorite tool for this is webpagetest.org. They also have an active forum where users can discuss results and exchange tips on making it faster.

Some test results :-

Site Alexa Rank First View Repeat View
My Sites
Main blog page 436,669 1.512s 1.038s
A single post page on my blog. 436,669 0.822s 0.648s
Thaindian.com Homepage 5,368 0.740s 0.514s
A story page on Thaindian News 5,368 4.517s 3.411s
Sites for Geeks/nerds
Stack Overflow 445 2.233s 1.734s
A single thread at Stack Overflow 445 2.846s 2.645s
Slashdot.Org 1,393 3.773s 2.175s
A single thread at Slashdot 1,393 3.817s 2.100s
New media
The Huffington Post 152 6.945s 4.044s
A single post on HuffPo 152 7.563s 4.416s
TechCrunch 357 16.462s 14.760s
An individual post on TechCrunch 357 10.987s 6.764s
ReadWriteWeb 1,996 17.766s 11.643s
A single post on ReadWriteWeb 1,996 18.890s 10.408s
Big media
Google News 1 3.253s 1.365s
Single story on Google News 1 2.688s 1.238s
Yahoo! News 4 3.174s 1.707s
Single story on Yahoo! News 4 5.310s 2.335s
New York Times 91 7.038s 2.200s
Single single story on NYT 91 4.650s 4.507s
BBC 40 7.485s 3.427s
Single story on BBC 40 7.148s 3.851s
CNN 58 10.197s 2.528s
An Article on CNN 58 7.989s 3.523s
MSNBC 9 8.172s 6.638s
Single story on MSNBC 9 12.064s 4.191s
The Washington Post 316 9.878s 3.828s
Single story on WaPo 316 15.435s 4.530s
ABC News 492 14.761s 4.205s
Single story on ABC News 492 8.697s 3.037s
RollingStone 3,376 18.700s 3.572s
An article on RollingStone 3,376 10.707s 2.905s
Fox News 201 26.755s 8.761s
Single story on Fox News 201 16.281s 5.839s

The Sajal Kayan award for excellence in web development goes to FOX News
Test conditions :-

  • First View is simulated to act as the first time the visitor visits the website, the Repeat view is when the user visits the website again after a while, probably closes and reopens the browser in between.
  • All tests were done on Internet Explorer 8. Yes, I know you hate IE, I hate it more than you! But since the majority of the web uses this browser we test on IE8. Also IE8 performs significantly better than its predecessors. Some of the sites tested may take upto 2x the time to load on IE7 due to lower parallel downloads per host.
  • The tests were done from a test machine in Dulles, VA Provided by AOL set to work at DSL speeds(1500 Kbps down, 384 Kbps up and 50ms latency)
  • The timings above show when the window.onload event was triggered. It is possible that the page was usable well before that. Very rarely is also possible that for the page needs to do more stuff after onload in order to be usable.
  • Each test was repeated 5 times and its average was taken
  • I have tried to be as fair as possible in selection of pages for the test. I didnt use pages filled with videos/many images, etc.
  • Tests were conducted during this weekend(July 3rd and 4th) so traffic to those site would be much lower than usual.

You can see from the table above, that except for Google News, Yahoo! News and (to some extent) The New York Times and BBC, all other websites have not yet given a minute of thought on Frontend performance of their web pages. This needs to change. Even one of the biggest evangalist of Frontend performance Google, forgot to set correct cache control headers for images on Google News.

I place more emphasis on individual story pages since those are the pages which a first time user would encounter first – coming via search, links, tweets etc…

Now, when browsing un-optimized sites from Thailand, the load times increased exponentially due to a much higher latency and occasional packet loss.

Finally! compare each of the above link visually in IE7 in video mode. WaPo single story is missing due to a bug. For each URL, 3 first-view tests will be run from ‘Dulles, VA – IE7′ and the median run will be used for comparison.

How to improve?

Essential reading :-

An optimizers goal should not be simply to get the total load time low. Thats important, but more important is the time in which the website kinda becomes usable. This for a news publishing site is being able to display the title and body of the story. The user can start reading the content while other parts of the website loads. This for Thaindian News story page hovers around 0.9 to 1.5 seconds!

  • http://www.sajalkayan.com/page-speed-analysis-search-engine-roundtable.html Sajal Kayan » Page Speed Analysis: Search Engine Roundtable

    [...] am planing to do a series of posts on analyzing popular websites I visit frequently. By now I am so obsessed to optimize for speed that I’ve run out of sites to optimize, hence I’m doing it for other [...]

blog comments powered by Disqus