Slashdot Mirror
Ad Networks the Laggards In Jackson Traffic Spike
miller60 writes "Advertising networks are being cited as the major bottlenecks in performance woes experienced by major news sites during the crush of Internet traffic Thursday as news broke about the death of pop star Michael Jackson. An analysis by Keynote found that many news sites delivered their own content promptly, only to find their page delivery delayed by slow-loading ads. The inclusion of third-party content on high-traffic pages is a growing challenge for site operators. It's not just ads, as social media widgets are also seeing wider usage on commercial sites. How best to balance the content vs. performance tradeoffs?"
Even at times of average load you can see delays as the browser goes off to find some unresponsive ad server. Google analytics and other stat-gatherers can be a problem too. It's annoying when it prevents the appearance of a page. Seems easily solvable within the browser though, set content from other domains to be on a shorter timeout. If the site fails because some off-server content isn't available, that's a badly-designed site. Ordinarily I'd just miss out on a few ads. Boo hoo!
Whenever the ad servers get to a critical overusage point, replace them with a set of text ads. Or better yet, replace them with a text ad for AdBlock Plus. Hey, a guy can dream, right?
Ryan Fenton
The best way to deal with this sort of thing is to do regular checks as to how long hitting the address that's going to be loaded takes, in a cron job or whatever, and if it goes over a certain threshold, turn off that provider.
Sure, you'll lose a bit of ad revenue, but you won't have pissed off users who think your site is broken.
They *are* loading the "primary content" first. They just differ with you as to what constitutes "primary".
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Yeah this is news? Man the main reason why I originally started blocking ads was not because I necessarily objected to them, it was because the ad servers always seem to hang up the page loads. Web 2.0 as it is called simply made this problem even worse with sites cross loading content. Web 2.0 sucks!
Did you ever wake up in the morning, with a Zombie Woof behind your eyes? -- FZ
The worst part about stories like this is having to skip past the 3 dozen Slashdot posts that all say "I don't see ads because I block them! Hyuk! Hyuk!"
Yes, we all get it. Lots of Slashdotters block ads. We know. We've read it a million times on this site. Could you just shut the hell up so we can comment on the actual story? Thank you.
Comment of the year
I think those comments can be meaningful. I avoid doing massive ad blocking, but in some cases, I've blocked ads from locations that created major slowdown in page loads.
It's an example of why ad delivery services are failing us: In modern browsers, delays for ad loading do happen from time to time, regardless of the size of your internet tubes. Bad performance makes even users that aren't ad averse want to block them, just for the performance gain, just like aggressive DRM makes users that have no problem paying for software be tempted to become pirates.