Forum Moderators: Robert Charlton & goodroi
Google has started to include site speed in web search rankings.
You're telling me with the experience you have that it takes WMT to tell you how slow a sites might possibly be. Though I am from Texas, I have a Missouri mentality. I'll believe it when I see it.
Duh, why use it then to begin with.
Likely millions every day.
Thirdly these 200 other factors Google takes into account don’t mean squat if site speed becomes a primary figure in site evaluation as it did in Adwords.
Related to Google Analytics, I mentioned above the new Asynchronous Tracking Code [google.com] version that became available to all GA users last December. Sounds like a good idea to me.
BillyS and others - I wouldn't necessarily worry about the speed of your site versus Google's declared overall averages.
I've mentioned this elsewhere... it is NOT about the "happy user" it is about google being happy with not having to wait for your server to send material to their bots! Do it quicker, they can do more without expending more resources (time really is money for google).
Does the page load time include AJAX calls that fire when the document onload event triggers?
As always, we can never know for sure, but my rankings started dropping a LOT two weeks ago. I didn't do anything to the site. So I wondered if my host had changed something or had been down. Nothing reported on webmaster tools... Hmmm.
So I go and read the news: WOW site speed is "1%" of ranking. Then I go and fix what was wrong. Site is "fast" now according to google. Bam, rankings back. That 1% sure made a 99% difference in my case....
These suggestions are based on the Page Speed Firefox / Firebug plugin. In order to find the details for these sample URLs, we fetch the page and all its embedded resources with Googlebot. If we are not able to fetch all of embedded content with Googlebot, we may not be able to provide a complete analysis.
...
When looking at flagged issues regarding common third-party code such as website analytics scripts, one factor that can also play a role is how wide-spread these scripts are on the web. If they are common across the web, chances are that the average user's browser will have already cached the DNS lookup and the content of the script. While these scripts will still be flagged as separate DNS lookups, in practice they might not play a strong role in the actual load time.