Blog Post

How Royal Wedding Impacted Web Performance

Published
April 29, 2011
#
 mins read
By 

in this blog post

I read an article yesterday predicting that the Royal Wedding was going to be a big stress test to the Internet. To observe the impact of the Royal Wedding on the Internet, I decided to monitor some of the popular websites that provided coverage for the Royal Wedding: Yahoo,  CNN, Youtube, the Official Site, Facebook,  Twitter,  BBC,  MSNBC & the Telegraph

We monitored the web performance of each website from all of our global agents, using Internet Explorer 8 as a browser. The goal was not to compare the performance of the sites, but to see how well each website handled the traffic during the ceremony.

Based on the collected data BBC and Yahoo experienced slow performance and had availability issues. Youtube and Facebook also experienced slowness later in the day starting around 6 am ET, when the US East Coast woke up.

News Outlet Category:

Web performance of news websites during royal wedding

Social Media Category:

Web performance of news websites during royal wedding

Other Sites:

Web performance of news websites during royal wedding

BBC Scatterplot view:

BBC Web Performance Scatterplot During Royal Wedding

Yahoo Scatterplot view:

Web performance of news websites during royal wedding

We also monitored the performance of the major CDNs (Edgecast, Cotendo, Akamai, Limelight, CDnetworks…) but the data did not reflect any major impact on their performance.

URls monitored:

Definitions:

  • Response Time: The time it takes from the request being issued by the browser, to the Last Byte received from the server for the primary URL.
  • Web Page Response Time: The time it takes from the request being issued, to receiving the Last Byte of the final element on the page. It reflects the impact of all the requests in the webpage.
  • Wait Time: The time from the connection to the server established and the request sent, to the First Byte of response from the server. It reflects the performance of the server in processing the request.

Mehdi – Catchpoint

I read an article yesterday predicting that the Royal Wedding was going to be a big stress test to the Internet. To observe the impact of the Royal Wedding on the Internet, I decided to monitor some of the popular websites that provided coverage for the Royal Wedding: Yahoo,  CNN, Youtube, the Official Site, Facebook,  Twitter,  BBC,  MSNBC & the Telegraph

We monitored the web performance of each website from all of our global agents, using Internet Explorer 8 as a browser. The goal was not to compare the performance of the sites, but to see how well each website handled the traffic during the ceremony.

Based on the collected data BBC and Yahoo experienced slow performance and had availability issues. Youtube and Facebook also experienced slowness later in the day starting around 6 am ET, when the US East Coast woke up.

News Outlet Category:

Web performance of news websites during royal wedding

Social Media Category:

Web performance of news websites during royal wedding

Other Sites:

Web performance of news websites during royal wedding

BBC Scatterplot view:

BBC Web Performance Scatterplot During Royal Wedding

Yahoo Scatterplot view:

Web performance of news websites during royal wedding

We also monitored the performance of the major CDNs (Edgecast, Cotendo, Akamai, Limelight, CDnetworks…) but the data did not reflect any major impact on their performance.

URls monitored:

Definitions:

  • Response Time: The time it takes from the request being issued by the browser, to the Last Byte received from the server for the primary URL.
  • Web Page Response Time: The time it takes from the request being issued, to receiving the Last Byte of the final element on the page. It reflects the impact of all the requests in the webpage.
  • Wait Time: The time from the connection to the server established and the request sent, to the First Byte of response from the server. It reflects the performance of the server in processing the request.

Mehdi – Catchpoint

This is some text inside of a div block.

You might also like

Blog post

When SSL Issues aren’t just about SSL: A deep dive into the TIBCO Mashery outage

Blog post

Preparing for the unexpected: Lessons from the AJIO and Jio Outage

Blog post

The Need for Speed: Highlights from IBM and Catchpoint’s Global DNS Performance Study