Google’s Button is Slow…And so is Facebook’s.

Bookmark and Share

Jun ‘11 2

There, I said it!

Yes Google, who built speed into its core values, has an entire website dedicated to making the web faster, developed PageSpeed, invents protocols named “SPDY”, and makes bad ass videos showing how quickly their browser loads web pages from the local disk, has their own take on the Like Button.

And it’s slow. Not only is it slow, it is slower than Facebook’s Like Button, which I didn’t think was possible.

Check out the painful WebPageTest results here:

Let’s assume it’s the first time we get to experience the joy of these buttons (clear cache):

Google +1 Facebook Like
Load Time 2.2 sec. 1.8 sec.
Bytes 66 KB 92 KB
Requests 8 9

2 seconds to render a button? A button. Really.

It’s okay, +1 will soon be everywhere, so they are sure to be cached super-well? No. Repeat view (cached) results:

Google +1 Facebook Like
Load Time 1.8 sec. 0.8 sec.
Bytes 25 KB 4 KB
Requests 4 1

The worst part is that this button will almost certainly impact SEO ranking in Google, making it essential for most websites. And speed is also a ranking factor. I’m confused.

Facebook’s Like button is also required for maximizing traffic. Let’s see what they both look like — together:

Our bare minimum hope for first impression load time is 2.5 seconds. According to Google, entire pages should load this fast!

Google, Facebook: I don’t think you need me to make recommendations on how to fix it. I know you can do it – please make it a priority.

Please also provide an asynchronous JS snippet as a recommended option in your instructions like you did with Google Analytics.

You hurt me today Google, and you’re hurting the web. I thought you and me were like THIS:

Experimental Artz version 8974530


Most Popular Stories

Bookmark and Share

12 Responses to “Google’s Button is Slow…And so is Facebook’s.”

Leave a Reply »

  1. steve squawked... June 3rd, 2011 at 7:54 am

    +1 (hah!)

  2. anyone shouted... June 3rd, 2011 at 11:32 am

    for google +1 download button js plusone.js to your own server and rename the path then u done

    for facebokk using iframe make it fast

    dont forget twitter follow button. use same trick as google +1

  3. Pavel Paulau warned... June 3rd, 2011 at 2:50 pm

    I guess local plusone.js wouldn’t work…

  4. anyone stated... June 7th, 2011 at 4:57 am

    you need to update frequently for changes :)

  5. hzlzh proclaimed... June 8th, 2011 at 12:33 am

    Did you try to local plusone.js and they other js that should be used into your host.
    I just only cached plusone.js, but still feel very slow loading +1.

  6. Stoyan tipped... June 8th, 2011 at 2:37 am

    I’m on it, man!

  7. Nicolas Chevallier blurted... June 9th, 2011 at 12:59 am

    it’s still surprising from Google to do this kind of error, especially when we know they have recruited qualified engineers!

  8. Around the web | alexking.org barked... June 12th, 2011 at 11:08 am

    [...] Google’s Button is Slow – And so is Facebook’s. – It’s both difficult and frustrating to explain to clients that the reason their sites are slow is because of 3rd party scripts; typically ads and social buttons. (thanks Chris) [...]

  9. Nick articulated... June 14th, 2011 at 8:56 am

    +1 is crazy slow.
    And most of Facebook’s stuff breaks W3 Validity. Sheesh!

  10. Simon Doerksen squawked... June 22nd, 2011 at 10:51 am

    sillyness! you shouldn’t need to work around third party embed scripts with iframes and the like! c’mon google you are better then this..

  11. Totti Anh Nguyen howled... September 7th, 2011 at 5:19 pm

    You are right. I’m also experiencing this painful sluggishness.
    Thanks for sharing :)

  12. Kevin Leary tipped... December 22nd, 2011 at 7:24 am

    This couldn’t be more true! I just implemented a TechCrunch style approach to the main page on http://blog.openviewpartners.com that loads in each sharing widget when a user mouses over a post. The page request (according to pingdom tools) went from 15 seconds to 3 seconds. I have to say that LinkedIn was actually the slowest re.

Leave a Reply

Please index me, experiment!

“Boy, that escalated quickly… I mean, that really got out of hand fast!” — Ron Burgundy