Third-Party Scripts and Performance: How to Identify and Fix the Worst Offenders

Most performance projects start with images and fonts. The pages that still feel slow after the hero is optimised often have a different problem: third-party JavaScript. Tag managers, chat widgets, A/B tests, and social embeds compete with your first paint and the interactions INP measures.

We start with a cold inventory: view source for external script hosts, DevTools Network grouped by domain, and tag manager preview logs per template. Lighthouse's third-party audit ranks transfer size and main-thread blocking by origin. DevTools Performance shows when those scripts run, not only how large they are.

• Map every external host before you debate which tag to cut

• Rank offenders by CPU and blocking time, not only kilobytes

• Delay or fence tags that do not need the first paint

• Re-run lab and scheduled monitoring after one change at a time

Read more: how to identify and fix the worst third-party scripts