Keynote: Ad Networks Failed, Not News Sites

10 comments

Advertising networks and widgets are being cited as the key factors in the performance problems experienced by major news sites during the crush of Internet traffic Thursday as news broke about the death of pop star Michael Jackson.  

Keynote Systems, which provided early data on the sluggishness of news sites Thursday, released an analysis late Friday that highlighted the role of third-party content. “Our measurement data shows that for sites reported as having performance slowdowns yesterday, internal content delivered quite fast, however content that came from other sources contributed most to the site slowdowns,” said Shawn White, director of external operations at Keynote Systems.

Many news web sites use advertising networks rather than serving ads from their own servers. This practice allows them to outsource some of their ad sales, but ties their site performance to the speed of the ad network’s servers.

Keynote’s analysis highlights the challenges of including third-party content in high-traffic sites, even as social networks help the web grow ever-more interconnected. It also exposes a tough problem for ad-supported sites in an online economy built around pageviews – the moments of heaviest Internet traffic offer potential gains, but can also be the most difficult to monetize.

Organization with significant news traffic can optimize for spikes, but ad servers and the content they provide are often outside the control of the IT organizations of the news site, according to Keynote’s White.

Delays Frustrate Users
“This is an important distinction, because in some cases, depending upon how a site is constructed or how the Web browser is used, a page may display perfectly fine with a blank area where a third party image should have been shown,” he said. “In other cases, the entire Web page will wait until that last image is downloaded from the third party advertisement service, frustrating the reader.”

ABC.com’s news content “was consistently served in a matter of seconds whereas some of the third party content took much longer,” according to Keynote, which said news sites should require third party content providers such as ad networks to certify the capacity of their networks, perform regular load tests from around the globe, and have strong Service Level Agreements (SLAs) in place.

Speed and the ‘Widget Economy’
The performance of third-party content is also key in the “widget economy” developing around social networks. Last summer white-label social network provider Ning cited performance issues in banning a popular widget developer from its platform. Facebook has also had to turn off third-party apps that slowed the site’s performance.

Here are several useful resources for addressing third-party content performance:

RELATED STORIES:

About the Author

Rich Miller is the founder and editor at large of Data Center Knowledge, and has been reporting on the data center sector since 2000. He has tracked the growing impact of high-density computing on the power and cooling of data centers, and the resulting push for improved energy efficiency in these facilities.

Add Your Comments

  • (will not be published)

10 Comments

  1. That explains why I didn't notice any slow downs because I use AdBlock Plus and many filters. ;)

  2. mrbene

    Most ads can be set up so they load after the content - but publishers set them up to load before the content, so that they get more ad impressions. And it's the publisher, not the ad network, that decides to sequence pages that way. Also, "consistently served within a matter of seconds" is a long time in the internet world. I'd agree that ad networks can degrade the user experience - but I'd submit that publishers who configure their sites to be dependent on 3rd parties to load are engaged in poor design.

  3. Eric Porres

    Mr Bene brings up an excellent point regarding page design and coding which supports the loading of images, ad assets, etc. Surprising that few if any news sites took action to correct during spike in traffic, as it would be a relatively trivial task for a webdev team. Wonder what comscore will reveal about day in the end.

  4. @mrbene, exactly. The way applications are delivered to the "viewer" seems to be one of the last steps in the development process. Usually much to late to do anything about it! That's why we are seeing more people using Application Delivery Controllers to do the integration work of this third party content, and if it does not make it on time to the page build either leaving it out completely, or replacing it with content from another provider. You could even script the process, so that you had a choice of a number of content providers, and the first to deliver is the one that get's it's content on to the page.