Did last Thursday’s Facebook outage affect your site? If not, you’re one of the lucky/smart ones. Here are a couple of good reads from Catchpoint and Keynote on the subject. Outages like this are clearly a wake-up call for site owners. I’ve been writing about this issue for a while now — most recently, coincidentally, just a couple of weeks ago — and thought it might be useful to round up these posts.
If the issue of third-party performance is new to you, this post will help you (1) understand the impact of all those harmless-looking little snippets of code, and (2) regain control over your rogue third-party content.
Is this day and age, third-party content providers need to make their scripts load asynchronously in order not to bog down page load. StumbleUpon didn’t, and as a result, we removed their script from our websites.
As we’ve all internalized by now, third-party scripts are the one of the most common points of failure for sites. Despite this, measuring the impact of third-party content on a site’s usability is often an afterthought — if it even gets thought about at all. Here’s how you can use a free tool like WebPagetest to test your site’s vulnerability to third-party failure.
There’s a growing awareness of the fact that third-party content can cause a major hit to your website’s performance. Good. Great. Now we need to tackle what I’ve dubbed “fourth-party calls”. Not only can these insidious server calls leach performance, they also have massive security implications.
I see a lot of widget bandwagon-hopping, with people loading up their site with every new button and third-party tool that comes along, with little regard for the end result. Today, widgets are to websites what animated gifs were in 1996. Here are a couple of tips for you die-hard widget junkies.
Inspired by this popular blog post, this short webinar goes into greater depth about three speed-zapping third-party culprits on your site.