even their blog mentions this, but they did nothing yet:
[adsense.blogspot.com...]


many other poeple got this issue:
[google.com...]

no solution so far

bumpdump

I've seen other webmasters commenting here on this forum about using the G Adsense js as an external js to reduce size and somehow increase performance. I never tried it, perhaps you would want to look on that.

I'm there too, not happy with G Agdense load time or size.

I agree. Google makes such an issue of page load time, but they don't offer an asynchronous solution for Adsense. I essence (at least hypothetically), they are penalizing anyone who participates in the Adsense program. Do no evil.

This is definately an area where Google doesn't walk the talk. They talk about bandwidth and speed, but don't institute what should be simple optimizations.

Adsense and Analytics both slow us down.

If you're worried about your Webmaster Tools, Labs, Performance data you can easily influence it. Several times now in the past year I've conveniently turned off javascript in my browser using a Firefox addon. Then making sure PageRank is enabled in the Google Toolbar I surf my sites, which I would do anyway, while keeping them up to date. My DSL connection pageload times go from 5 seconds to 2 seconds per the Google Labs performance tool, and this is with pages successfully showing Amazon Product ads (Amazon ads, server produced in IFrames, do not require javascript).

For my sites javascript "on" "off" is pretty much Adsense ads on and off.

There are probably so few people surfing our sites with the Google Toolbar and PageRank turned on that the performance data can be influenced. In fact it may be the webmasters themselves feeding Google the poor performance data. I frequently tour my sites with tons of apps running and frequently with the PageRank stat on, delaying the Window onload event substantially.

So make sure you turn off Pagerank when you tour your own sites, or turn off javascript (if you can) and turn pagerank on and watch your Page Load performance increase drastically.

What's truly annoying was the first step Google took to solve this problem was to remove any sign of the poor Adsense and Analytics performance from the Webmaster Tools Labs report. If you use Firefox and the actual Pageload speed tool, you'll see all the problems.

Finally turning off image ads may produce enough of a pageload performance boost that reduced load time might increase earnings more than the additional image ad bidders. Plus image ads are far more likely to be CPM, so for lower traffic, high content sites, these CPM ads degrade earnings by displacing the better paying CPC ads. Google has not figured out how to calculate the true "effective CPM" for CPC ads on lower traffic pages(Another topic!).
With image ads on Adsense loads several more javascripts and of course the images (and flash) must load too, really delaying the onload event. This slow loading may even cut the traffic Google sends your sites.

i am not talking about a low visited website.
If i turn off javascript and stuff and i visit it will count for less than 0.1%

for turning off the images on adsense it may be a solution but when i tried it my revenues were 35% cutted off, so it's not a solution for me.

regards google analytics i already load it after onload event with appendChild

in fact imo atm there aren't any solutions for speed up adsense

count for less than 0.1%

But the real question is how many of those visitors actually have the Toolbar PageRank feature on. Not many I'll bet. So why not try it? The thought being webmasters may be the source of there own poor performance data.

I don't doubt that image ads do boost earnings on very high traffic sites.

Regarding a performance fix. Until about 2006 I successfully displayed targeted adsense ads inside IFrames, truly boosting site performance. This is allowed by the TOS. Google broke this functionality, I believe, at the time they added "section targeting". At that time targeting in an Iframe went away big time. Truly a shame. In fact at that time the Adsense Advisor dujour contacted me with Sticky mail hoping to work on the IFrame problem. I shouldn't have turned him down, but I was losing money!
Adsense could generate the ads on their servers and serve them in an IFrame (like Amazon) and use an ajax transaction to verify the referrer string fed to the Iframe. But it seems Google wants to use as much of the visitor's CPU and bandwidth as possible thereby off loading their servers.
Have you ever looked at the code on their home page? It used to be so pristine; not compliant, but pristine! Now it's huge mess!

Part of the Adsense code structure is obviously there and mandated as an attempt to thwart any tricks one might try to deceive the code with alternative, hidden content. I get the impression that even premium Adsense users take a performance hit, which is truly surprising.

March 2011 update, Adsense is still rendering slowly and I still can't find any means of speeding up total pageload with adsense on it.

I keep hearing about people placing adsense high up on their pages using placement divs and executing the javascript from their footer but I cannot find a good working example that doesn't interfere with the Google Javascript. Anyone? I know this doesn't load the page faster in total but at least it doesn't block pages early on.

The real question is - how do we stop adsense from slowing down pageload times as much as possible, or at least delay the 300ms-500ms slowdowns until later in the code?

I know this has been mentioned elsewhere in the forum for other slow loading external resources but it's worth repeating here.

Assign a defined amount of browser real-estate to the AdSense blocks such as:
<div id="adsense" style="height:100px; width:800px;">
...AdSense code in here...
</div>

That will allow the browser to continue to render the rest of the page while waiting for google to respond.

Without a predefined block the browser has to wait for that response to complete before it can continue. It might save a bit of time. But other than that it's up to google to "do as they say".

where you want the ad to display...
<div id="top_ad"></div>

the code in the footer...
<div id="footer" style="display: none;">
---ad code un modified ---
</div>

below put javascript....

<script type="text/javascript">
window.onload = function() {
document.getElementById('top_ad').appendChild(document.getElementById('footer'));
document.getElementById('footer').style.display = '';
</script>

Ad will delay loading...

I would be cautious about using "style="display: none;". A certain bot may interpret it as hidden text and frown upon it.

dude23124 the adsense javascript has some onload events of its own, does the code you posted conflict with that? I read somewhere that using javascript onload to trigger more javascript onload defeats the whole onload event. Elsewhere I read that Google determines where on a page the ad is as part of its payment algo so would these ads be considered above the fold or in the footer ?

I mark up my pages similarly to sevencubed (create space with a div, and then use css to position the adsense block in it)

Remember, the highest paying ads are given to the Adsense units in the order they appear in your HTML.

Getting this order right can be tricky sometimes when using the css method.

Except for CTR experience, I don't think above or below the fold is involved with payment calculation.

It's strictly the highest paid ads are given to the ad units in the order they appear in the HTML. This applies only to ad units, not adlinks.