3 ms·
Not only are they bad, they slow down the rendering speed of the pages they're on. http://twitter.com/SlexAxton/status/12663859611 http://twitter.com/SlexAxton
by asnyder 17y ago
Not only are they bad, they slow down the rendering speed of the pages they're on.
http://twitter.com/SlexAxton/status/12663859611 http://twitter.com/SlexAxton/status/12663859611
- aschobel 17y agoWe use it via FBML and JavaScript SDK and the slow down seems to be minimal. We load their script right before </body>. Biggest annoyance is that it doesn't degrade very gracefully when FB has availability problems, you get a white square in the page in Firefox.
- woid 17y agoI think they can solve it when using Javascript SDK on modern browsers. IFRAME could be loaded offscreen and when it finishes then it does postMessage to notify the parent window. Javascript SDK injector then unhides the IFRAME. Easy to do, but they are probably busy doing other stuff.
- woid 17y agoWell it depends how you look at it. It definitely adds to network traffic and CPU load. But IFRAME content and javascript-injected IFRAME are both loaded asynchronously. Browsers are pretty good in progressive rendering of page content these days. So user should see the main page first and then it starts loading these additional resources. So no big deal IMHO. The button should not degrade user experience during page loading.