Not planned Load Facebook et al. at the end using AJAX

[rellek]

Hi,

I'd like to suggest loading those Facebook, Twitter and Google scripts at the end, maybe using AJAX. It's quite often lately that connect.facebook.com doesn't respond so your site is loading and loading and loading and sometimes not even stuff like your header image is loaded.

So loading those scripts when everything else is done would 'fix' that, I think.

 

[sonnb]

It also makes an issue that you have to press Back button several times to navigate to previous page as it counts the frame load is one load times.

 

[karll]

Yes, at least something should be done about it.

Personally, I've disabled the Facebook "recommend/like" button because it's so slow that it makes my site look bad. (A secondary reason I disabled it is that Facebook is evil.)

 

[aiman.h.kallaf]

Strongly Agree
my shared host is already slow as it is

 

[silence]

Absolutely it happens with both the Facebook and Twitter buttons. I have also disabled them.

 

[Rob]

I've seen this be a major problem too

 

[Triops]

Support it!
I would even prefer to have a 2-clicks solution implemented, since in some countries, for example Germay, a lot of people don't like/trust Facebook and moreover there might be a legal privacy protection issue if you activate facebook per default without opt in:
http://www.heise.de/ct/artikel/2-Klicks-fuer-mehr-Datenschutz-1333879.html
http://www.heise.de/extras/socialshareprivacy/

So, with 2-clicks there will be never a connecting and legal issue when loading forums index or threads, because although Facebook/Twitter/Google+ is clearly visible to the users, its activated after the first click only - as an opt in on every page.

 

[Adam Howard]

I'd take this even further and suggest the photo be a static image (not dependent on Facebook's servers) & that the actual script not be loaded unless someone clicks on that button.

I've seen this done on a few site & it surely does improve the overall load & management.

 

[rellek]

@Adam Howard
Yeah, this is basically what @PyroM meant. Heise online (see his links) "invented" this because we have some really crazy guys who do the privacy protection in Germany. And this solution (image from the own webspace and after the click the real script is loaded) seems to comply with the privacy protection law.

 

[Adam Howard]

@Adam Howard
Yeah, this is basically what @PyroM meant. Heise online (see his links) "invented" this because we have some really crazy guys who do the privacy protection in Germany. And this solution (image from the own webspace and after the click the real script is loaded) seems to comply with the privacy protection law.

Not a fan of the two click system, so not exactly what I was talking about.

Take my words for face value.... Social media buttons as static content (images) and nothing loaded until you click on them.

 

[rellek]

Not a fan of the two click system, so not exactly what I was talking about.

Take my words for face value.... Social media buttons as static content (images) and nothing loaded until you click on them.

I'm sorry, I don't get it. What's the difference between your suggestion and what heise online implemented? Look here:
http://www.heise.de/ct/artikel/2-Klicks-fuer-mehr-Datenschutz-1333879.html

It's at the end of the article above "Kommentare lesen (184 Beiträge)". You have to click the Facebook thing (which is an image hosted at heise.de) and this loads the actual facebook script from facebook.com.

 

[Triops]

And there is no problem to change the code a little to have the static images on your own server, if you prefer.
Facebook, or Twitter, or Google+ scripts are then only loaded from the foreign servers, when the appropriate static is clicked.

 

[wmtech]

We have created an add-on for Xenforo 1.2 to load the social share buttons from local server. It uses some code from Heise, mentioned in the post from PyroM above.

Available for download from here:
http://xenforo.com/community/resources/authors/wmtech.40565/

 

[Chris D]

We no longer use the native share buttons from various services and this approach has zero JS overhead on load and allows us to support many more share links.

As such, this is no longer needed.