Faster Google Plus One Button

Jul 27, 2011 • 8:20 am | comments (10) by twitter Google+ | Filed Under Google Search Engine Optimization

Google Plus One Button FastYesterday morning I posted on how Webmasters were dropping the Google Plus One button because it was slowing down their site.

Well, that worry may have been reduced because Google announced they have speed up those buttons to be three times as fast. Yes, 3X the speed! Even better, you do not need to change the code on your site to see the speed increase - it is automatic.

If three times as fast is not fast enough for you, you can switch the code to the asynchronous code version. To get the new code, just go over here and make sure the asynchronous option is checked off in the advanced options.

Are you willing to now add the button back, now that it is faster?

Forum discussion at Google Webmaster Help & WebmasterWorld.

Previous story: Panda 2.3 Confirmed Out: July 22nd


SEO Consult

07/27/2011 01:40 pm

"Even better, you do not need to change the code on your site to see the speed increase - it is automatic." - You do need to change the code if you already had the old code on your'll need to change the JQuery snippet to the new async snippet.

Black Seo Guy

07/27/2011 01:54 pm

Thanks god..I'm going to add it today. I guess they heard all the fuss and needed to do something. "Black Seo Guy "Signing Off"

Nick Stamoulis

07/27/2011 02:46 pm

Google has really been on a speed kick lately. I appreciate that they took the complaints of site owners to heart (even if they didn't mean it) and sped up the Google+1 button. I think Google realized that if they want site owners to implement it on their site, it better not hinder site speed.


07/27/2011 04:26 pm

"make sure the asynchronous option is checked off in the advanced options."  From the department of redundancy department comes this question:  Does that mean it has a check mark in the box or no check mark?

john lewis uk

07/28/2011 08:40 am

Well its a good news that speed is increase 3 times. It should be fast as nobody have a lot of time to spend now a days. I feel great that Google note down this and make positive change in it. Thanks to Google.


07/28/2011 01:12 pm

Will not add it back as I dont see the point or it right made my site waste bandwidth and used up more  RAM. Whats the use anyway ..all customers are on facebook or twitter and no one is on Google plus Ill save my resources and time for something the I know is actually bringing in revenue.  

Michael Oryl

07/31/2011 01:37 am

This change appears to have broken the button on my site.  It stopped showing up.  I put it on a basically blank test page, the same code, and it worked.  But on my live site I got a blank space (not using async code). I started removing stuff from the page to see what was breaking it.  Guess what I found. Nothing.  I stripped the page of everything and it still didn't work.  For a moment I thought it was that my site had as the base URL instead of all lowercase like my test page, but then that seemed to not fix it consistently, either. I have no idea.  My guess is that they are caching something now, and that has inhibited my ability to troubleshoot the issue.


08/02/2011 02:20 pm

I managed to reduce a little bit more the overhead of the snippet, like for the Google Analytics one. Check it out at :)

Black Fairy

08/03/2011 02:45 pm

me site seems ever so much slower, am i going to have to remove the code and add the new one all over again :-( so time we know this will make a difference...happy for someone to peruse to see what they think of the speed..already have flash in the header so dont want to slow things down... ta x


03/05/2012 01:11 am

I followed the same method as I use to inject Google Analytics and Quantcast to add Google Plus into my hamster game site. This is the code I used: var d = document; var google_plus = d.createElement('script'); google_plus.src = ''; google_plus.type = 'text/javascript'; google_plus.async = true; var first_script = document.getElementsByTagName('script')[0]; first_script.parentNode.insertBefore(google_plus, first_script); I went with HTTP instead of HTTPS to avoid any potential lag overhead when Google serves from secure HTTP. See the Google Plus example at

blog comments powered by Disqus