<b>Third-party scripts: the slow guests you invited</b>

<b>Third-party scripts: the slow guests you invited</b>

Chat widgets, analytics, ad tags, A/B tools — each is a 'third-party script', code loaded from someone else's server. Any one feels harmless, but together they're often the biggest drag on INP (Interaction to Next Paint) and LCP (Largest Contentful Paint), because they run on the same single work line as your own code.

Think of them like guests who bring their own loud speakers to your dinner party — you don't control their volume.

How to take back control:
— List them: DevTools <b>Network</b> tab, sort by domain — anything not yours is third-party
— Add <code>async</code> or <code>defer</code> so they don't block the page build
— Question each one — does that old heatmap tool still earn its slot?
— Load chat and social widgets only after the page is interactive

<b>Try this:</b> Open the Network tab and count your third-party domains. If it's over ten, you've found a real, fixable source of slowness — and trimming two or three often helps more than any image tweak.