Information about AdSense ads and site speed

Friday, April 09, 2010 | 12:34:00 PM

Labels:

Earlier today, our Websearch team announced that we now consider the speed it takes for a website to load when ranking it in Google search results on google.com. As an AdSense publisher and website owner, you may have questions about this change, so we'd like to take a minute to give you more details.

This change is part of our efforts to provide the best possible search experience for our users, as we've found that faster sites create happy users. Our internal studies show that visitors tend to spend less time on sites that respond slowly, and additional recent data shows that improving site speed also reduces operating costs. For these reasons, we're now taking site speed into account in our search rankings.

Site speed is just one of over 200 signals we use to determine search ranking, and because it's a new signal, it doesn't carry as much weight as the relevance of a page. In fact, less than 1% of all search queries on google.com are affected by the site speed signal. We launched this change a few weeks back after rigorous testing. If you haven't seen much change to your site rankings, then this site speed change possibly did not impact your site.

In general, a website would have to be particularly slow for its ranking to be affected. We look at the time it takes to load all components of a page that contribute to page speed, including images, rich media, and Javascript/HTML/CSS code.

AdSense is built to load ads quickly so there's no need to change your AdSense setup. Even so, we are working to speed up our ads products further. In addition, we also want to give you some suggestions of things you can do on your side, like enabling compression for your site, enabling caching of images, JavaScript, and CSS, and minimizing the size of your JavaScript with Closure Tools.

If you'd like to learn more about speeding up your website, or evaluate your site's speed, we encourage you to look at Site Performance in Webmaster Tools and try developer tools such as Page Speed, YSlow, and WebPageTest.org. Please note that at this time, the only way to determine whether your site has been affected is if you've seen a recent change in your search ranking.

For more information on this change, please visit our Webmaster Central blog.

13 comments :

Manuel Lemos said...

I used PageSpeed and it complains a lot of the weight Google AdSense and Analytics slow down page loading.

It complains namely of AdSense Ads not combining multiple external Javascript requests:

There are 3 JavaScript files served from pagead2.googlesyndication.com. They should be combined into as few files as possible.

* http://pagead2.googlesyndication.com/pagead/show_ads.js
* http://pagead2.googlesyndication.com/pagead/expansion_embed.js
* http://pagead2.googlesyndication.com/pagead/sma8.js

Javascript having too short refresh times:

The following cacheable resources have a short freshness lifetime. Specify an expiration at least one month in the future for the following resources:

* http://googleads.g.doubleclick.net/pagead/test_domain.js
* http://kona.kontera.com/javascript/lib/2010_04_08/KonaBase.js
* http://kona.kontera.com/javascript/lib/KonaLibInline.js
* http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif
* http://pagead2.googlesyndication.com/pagead/abglogo/abg-en-100c-000000.png
* http://pagead2.googlesyndication.com/pagead/expansion_embed.js
* http://pagead2.googlesyndication.com/pagead/show_ads.js
* http://pagead2.googlesyndication.com/pagead/sma8.js

Loading unused CSS styles:

http://googleads.g.doubleclick.net/pagead/ads?client=ca-pub-2951707118576741&output=html&h=250&slotn... inline block #2: 101 bytes of 1.5kB is not used by the current page.

* #ads ul.auma
* #ads ul li.adma
* .adma .adc
* .adma .adt
* .adma .adb

http://googleads.g.doubleclick.net/pagead/ads?client=ca-pub-2951707118576741&output=html&h=90&slotna... inline block #3: 615 bytes of 1.5kB is not used by the current page.

* #ads ul.auma
* #ads ul li.adma
* .adma .adc
* .adma .adt
* .adma .adb

Not leveraging the proxy caches:

Due to a bug in some proxy caching servers, the following publicly cacheable, compressible resources should use "Cache-Control: private" or "Vary: Accept-Encoding":

* http://googleads.g.doubleclick.net/pagead/test_domain.js
* http://pagead2.googlesyndication.com/pagead/expansion_embed.js
* http://pagead2.googlesyndication.com/pagead/show_ads.js
* http://pagead2.googlesyndication.com/pagead/sma8.js


Do you plan to fix these problems?

Bob said...

@Manuel,

I would recommend implementing the asynchronous form of Google Analytics code.

http://code.google.com/apis/analytics/docs/tracking/asyncTracking.html

Manuel Lemos said...

Thanks Bob, I was really not aware of that.

I wonder if AdSense will also have asynchronous/deferred loading versions.

Bob said...

I suspect this to be the case.

Devmentia said...

Doesn't this punish the small operator who has less control over their, usually shared, hosting? Or those in countries that have lesser infrastructure? At the same time, allowing bigger business to throw money at the speed problem and gain a better ranking?

Manuel Lemos said...

Bob, do you mean AdSense is already asyncronous?

I know it uses iframes, but I still notice a significant page loading delay for each ad.

Paco Tomei said...

Besides the slowdown introduced by the Adsense code, HTML validation generates all source of errors.

Web Developer said...

if the user uses cyber roam the google ads are clicked but not opened, at that situation the publisher will get paid?

by
siva
www.itassociation.co.in

Leroy said...

I've been watching my site performance for a while, normally 50 to 60% of sites are faster than mine. Other than compressing, which I'm not really into, all the issues with my site are Google products?
DNS; a gif-logo w/ Google search bar
DNS; gif files stored w/ Picasa
and of course Google Analytics.

Compression sort of goes against the bloated code requirements from W3C.

However I am saving 1,480 characters as I slowly replace the older Google Search Bar code with the newest version.

Kim Woodbridge said...

My sites that have adsense do seem slighly slower than those that do not. It seems, however, that the slowdown has to be significant to really affect ranking.

Rune Mai said...

Each adsense block takes 300-400 ms to load and even though this is async it still slows the pageload down (from a user point of view a page seem slow if central elements on the page loads slowly).

is 300-400ms normal for adsense to load? what can be done to improve this?

Mike said...

its kind of ironic for google to lecture on how to speed up sites when a lot of time its adsense that slows down sites the most! why? because it forces you have to insert inline javascript, a big no no.

i had a leaderboard at the top of the page. i removed it and it speeded the site up more than anything.

if they switched to iframes instead of javascript it would help but they cant because then they cant easily read the source page for context.

what they might want to do is to modify adsense to load after the page loads and then copy itself to publisher designated positions at the top.

fe said...

I've done a proof of concept that pushes google ads to be truly async, allowing the main page to render faster see "Google Ads Async (asynchronous)" http://blog.figmentengine.com/2011/08/google-ads-async-asynchronous.html