Third Party Scripts
summary
Many sites load resources from 30+ hosts and the common pattern of "copy this piece of JavaScript" creates performance, reliability and security risks (one provider compromise can affect many sites; Outbrain is cited). Tools mentioned include SPOF‑O‑Matic, WebPagetest, Write Capture and resource timing; proposed fixes range from Common 3rd‑Party Objects libraries and shared delivery domains to sandboxed iframes, Content Security Policy, Web Components and script preloading/dependency controls. Document.write remains a major pain point that breaks async strategies.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:50Welcome
- 2:40Overview
- 3:25Security Issues
- 5:20State of the Art
- 7:00WebW3C
- 7:15C3PO
- 8:40Web Components
- 10:00What happens now
- 12:15Poll
- 13:38QA
- 17:18Use Cases
- 19:30DNS Resolution
- 22:06Conditional Loading
- 29:21Proxying
- 34:37Performance
- 38:19Impact of Scripts
- 40:14Security Policies
- 41:12Can we share connections
- 45:52Single point of failure
- 48:00Script tracking
- 50:06Widgets
- 52:18Browser Vendor Guide
related talks
26mScripting in the 3rd Party True Tales of Horror and Hope
25mMaster Scripts & Third Parties in Next.js
46mDeep dive into third-party performance
29mYour Scripts In My Page - What Could Possibly Go Wrong?
13m"Don't Let Third Parties Slow You Down"
40mHostile JavaScript: Attacking and Defending the Browser
47m30 Tips for Secure JavaScript
57mYour Website Is Running Code You’ve Never Seen