You've heard it many times - third party content can easily cause an otherwise well performing website to become sluggish and slow. And depending on how this content is loaded, it can also introduce single points of failure (SPOFs). When a large cloud provider or content delivery network (CDN) exper

PerfPlanetCal is a curated calendar of web performance events, conferences, and meetups around the world. Through event listings, PerfPlanetCal offers insights into web performance topics, including performance optimization techniques, browser performance tools, and user experience metrics. Developers and performance enthusiasts can discover opportunities to network with peers, learn from industry experts, and stay updated with the latest trends in web performance.

Web Performance Calendar

Third-party content creates single points of failure (SPOFs) when loaded as render-blocking resources. Analysis of 15.78 million websites shows 67.7% load at least one render-blocking third party, with 60% using different CDNs than their primary content. Common culprits include Google Fonts, CDN-hosted libraries (cdnjs, jsdelivr), and consent management services. The article demonstrates how to detect render-blocking third parties using WebPageTest, Chrome DevTools, and other tools, then test for SPOFs by simulating failures through DNS overrides or request throttling. Self-hosting critical assets and using async loading patterns can eliminate these risks.

Third Parties and Single Points of Failure

How Prevalent are Third Party SPOFs Today?

How to Detect Render-Blocking Third Parties