Forum Moderators: martinibuster

Message Too Old, No Replies

Adsense Load Speed

         

Maleda

8:56 am on Nov 10, 2015 (gmt 0)

10+ Year Member Top Contributors Of The Month



Can anyone share best practises on improving the load speed of Adsense ads. They seem to be getting slower and slower!

robzilla

10:44 am on Nov 10, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Place fewer ads per page or disable image ads if you can take the hit. The rest is pretty much out of your control.

Kaszinky

12:28 pm on Nov 10, 2015 (gmt 0)

10+ Year Member



It depends what you mean exactly. Ads themselves are loading more and more slowly, I mentioned it in another topic, and we don't have control over this. Now, there are some tiny things which can be done, to slightly improve things, but it might not be noticeable.

- Don't use responsive ads. Responsive ads load only once the whole page and content (images) are loaded.

- Place the adsense code the earlier as possible in the HTML code. Then you can use CSS to position the ad at its right place. This is not always convenient, and be carefully not to violate Adsense's policy .

- If you are using the async code, you can put the "adsbygoogle.js" call in the <head> section.

- You can use text-only ads. Text ads are loading faster, but can generate less incomes.

- You can disable third part ad networks. This is faster if Adsense is not checking the inventory of these networks. Also, it seems like these networks are again slower than Adsense to serve graphics. However, this can also reduce your incomes.

- You can disable IBA. Less analysis and guessing = some microseconds saved. But it will also impact your incomes.

- If your site relies on heavy images (like a gallery), you can delay the loading of these images. This is going to prioritize the load of the ads by creating less downloading concurrency.

Maleda

12:53 pm on Nov 10, 2015 (gmt 0)

10+ Year Member Top Contributors Of The Month



Hi Kaszinky, thanks for the feedback! You've answered my question, I didn't think there was much more we could do (we're already doing your first 3 points) but just wanted to put it out there to see if there was something we were missing!
Load times are painfully slow, I've noticed this has been raised in the 'Ask the Adsense Guy' feed so fingers crossed it's resolved, I'm sure this is one of the main reasons that Active View Viewable is not as high as it should be!

Kaszinky

2:42 pm on Nov 10, 2015 (gmt 0)

10+ Year Member



Yes, I am sure that the load time of ads has a very big impact on earnings. I do not know why it's getting that bad. I wonder if this is on purpose, showing ads "later" , might make them pop up at the eyes of visitors. Or Adsense's servers are too busy, dealing with too sophisticated algorithms. Or, they might be permanently DDos-ed (I guess that Google's servers are constantly facing attacks). Also, it's possible that Google tests/analysis medias on the fly before serving them to detect potential exploits or abuses.

Now, the thing is, for some reasons, my leaderboard banner which is on top of pages, ALWAYS load again more slower, than a 300x600 banner located lower in the page source code. I don't understand this. And by slower, I mean, the leaderboard, will show a graphic may be 2 or 3 seconds after the 300x600. May be inventory is bigger for leaderboard and top of page placement, so it takes longer to select one, I don't know.

By the way, to complete my first answer, in order to optimize a bit more things, you can detect yourself (with server side language, or on client side with javascript) if the page is being displayed on a mobile device or not. If it's on a mobile device, serve a more appropriate ad, like for example 300x100 text-only. My recommendation, always serve text only ads, and avoid 300x250 on mobile devices.

Addendum: by mobile devices, I mean smartphones. On tablets (which are also mobile devices in a way), also prefer text ads only, but you can use traditional desktop sizes.

netmeg

8:38 pm on Nov 10, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Don't use responsive ads. Responsive ads load only once the whole page and content (images) are loaded.


To my mind, that's a good thing, not a bad thing.

We've had some success with overall speed by putting all kinds of slower loading stuff (Google fonts, js, css, other scripts) into Google Tag Manager and serving it that way, including parts of the AdSense code. You might take a look at that.

Maleda

8:46 pm on Nov 10, 2015 (gmt 0)

10+ Year Member Top Contributors Of The Month



Thanks for the suggestion Netmeg - will definitely take a look at that!

Kaszinky

9:52 pm on Nov 10, 2015 (gmt 0)

10+ Year Member



To my mind, that's a good thing, not a bad thing.


Maleda asked how to load ads faster. In that case, using responsive ads is a bad idea, because ads will start loading only after the whole page is completed.

jimbanks

8:33 pm on Dec 4, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I think the issue might be all the remarketing tags that fire when the adsense block fires.

If you use a container tag solution like Ensighten you are able to allow or disallow the remarketing tags to fire.

Install the Chrome extension Ghostery and fire the page if you want to see what is happening.

I'd definitely use a container tag and run some experiments without having to tweak the code every time.

keyplyr

9:52 am on Dec 5, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



For desktop, Adsense is in containers which load first, then float to where I want them to display. I've never noticed any significant delay time specific to the ads.

For mobile I use responsive ads, but displayed at the bottom of the page so it makes little difference if the "loads after all content" theory is true or not :)

eeek

8:05 pm on Dec 6, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



To my mind, that's a good thing, not a bad thing.


It can be a good thing, but not if it makes the page jump around the screen while the user is trying to read.

keyplyr

11:47 pm on Dec 6, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Won't jump around with async.