I always find it ironic that performance on the web is more or less determined by whether you’ve added AD-networks to your site. Ironic in that its usually the companies promoting web performance that are also the ad networks killing it.
I recently stumbled on TNW and was reading an article, and noticed an amount of jank that would actually be difficult to try to purposely do.
For those who want to know, this wasn’t TNW’s fault. Well, they do listen to scroll events which is a no-no, but by all means, its not the end of the world.
The world kind of ends when you open up the dev tools to see whats underneath;
Ten megabytes of data transferred.
So many scripts running from so many domains.
Oh the jank, even chrome is fairly up front about it.
15 + iFrames…
A 220ms script pause caused by…. (drum roll)…
A full 1.39 seconds to paint the area. This appears to be caused by an ads overlay for the entire screen.
I wonder how these ad network code are allowed on pages with so many issues, its difficult to know why they spin up so much but they do take an amazingly large amount of time to run.