Why not artificially deferring all the ads, external images, nifty effects, etc. until the content is fully loaded? Instead of all the scripts being run on the moment, make them register somewhere and launch them one by one from the body onload event.
I played around with the idea some time ago, it isn't difficult to implement. Mostly. Some 3rd party code is a PITA to adapt to this schema. Other than that, it worked: all the content loaded and was displayed at once, and then all the external imagery started showing.
Of course, for something like this to be really useful, some kind of API or standard should be in place, and all the adserving companies should adapt to it. Not likely.
Slashdot Mirror
Why not artificially deferring all the ads, external images, nifty effects, etc. until the content is fully loaded? Instead of all the scripts being run on the moment, make them register somewhere and launch them one by one from the body onload event.
I played around with the idea some time ago, it isn't difficult to implement. Mostly. Some 3rd party code is a PITA to adapt to this schema. Other than that, it worked: all the content loaded and was displayed at once, and then all the external imagery started showing.
Of course, for something like this to be really useful, some kind of API or standard should be in place, and all the adserving companies should adapt to it. Not likely.