In this article · 10 sections
A website can be well built and still feel slow because of third-party scripts: code loaded from other companies' servers. Each one seems small: a chat widget here, an analytics tag there, a Facebook feed in the footer. Together they can add seconds to load time and make the page feel sluggish when tapped.
Common culprits
- Live chat and chatbot widgets
- Multiple analytics and tracking tags (GA4, Meta Pixel, Google Ads, Hotjar, etc.)
- Embedded YouTube videos and Google Maps
- Social media feeds and share buttons
- Review widgets
- Web fonts from external servers
- Pop-up and notification tools
- A/B testing tools
Why they're costly
- More downloads from more servers, each with its own connection setup
- JavaScript execution that blocks the main thread, hurting responsiveness (INP)
- Layout shifts when widgets appear late
- No control: if their server is slow, your page waits
Step 1: Audit what's loading
- Open PageSpeed Insights and look at "Reduce the impact of third-party code"
- In Chrome DevTools (F12) → Network, filter by "3rd-party" or sort by domain
- List every external script, what it does and who uses its data
Often you'll find tags nobody remembers adding, or tools from old campaigns.
Step 2: Remove what you don't use
If no one has looked at the heatmap tool in six months, remove it. If a social feed gets no clicks, replace it with a simple "Follow us" link. Removing a script is the biggest speed win of all.
Step 3: Consolidate tracking
Load tracking through Google Tag Manager so tags are managed in one place, fire only where needed, and can be removed without touching code. See Google Tag Manager for beginners.
Step 4: Delay non-essential scripts
Many scripts don't need to load immediately: - Chat widgets: load after a few seconds, or when the user scrolls or taps a chat button - Embedded videos and maps: use a click-to-load facade. See lazy loading - Review widgets: load when the section comes into view
Add defer or async to script tags where appropriate.
Step 5: Replace heavy widgets with lighter options
- A simple WhatsApp link button instead of a heavy chat widget
- Static review highlights linking to Google, instead of a live widget
- Self-hosted fonts instead of external font services. See web fonts and speed
- Static share links instead of social share scripts
Step 6: Preconnect to essential domains
For third-party domains you do need early (like a payment gateway on checkout), a preconnect hint can save time:
<link rel="preconnect" href="https://checkout.example.com">
Use it sparingly, only for important early connections.
Privacy bonus
Fewer third-party scripts also means less data shared with other companies, which helps with privacy expectations and the DPDP Act. See DPDP checklist.
A balanced approach
You don't need to remove all tracking. You need tracking you actually use. Keep GA4 and the ad pixels you're running campaigns with; question everything else.
Script audits are part of our speed optimisation and maintenance plans. Ask us to review your site.