HelpWithWebGet Help Now
← Back to Blog
Speed5 min read

Third-Party Scripts Are Killing Your Site Speed

Tracking pixels, chat widgets, analytics, ads — each one slows you down. Here's how to find the worst offenders and cut them without losing features.

ByDino Bartolome

You installed 15 “small” tracking scripts over the last two years. Each felt tiny at the time. Together, they've added 3-5 seconds to your page load. Here's how to find them, cut them, and keep what actually matters.

The hidden cost of third-party scripts

  • Every script you embed:
  • Adds network requests
  • Blocks rendering (usually)
  • Runs JavaScript on the main thread
  • Potentially loads *its own* scripts (chains)

A “small” 30KB chat widget might pull in 10 more dependencies totaling 500KB. You never see that until you audit.

Find your scripts

Open Chrome DevTools → Network tab → reload. Filter to JS. Sort by Size or Time.

Also check: DevTools → Performance → record a load. The “Scripting” section at the bottom shows how long each script blocked the main thread.

Common offenders (and alternatives)

Google Tag Manager Pulls in everything. If you're using it to load 5+ tags, expect 500ms+ of blocking.

Alternative: Use direct snippets for anything hot-path. Keep GTM for marketing tags you really do change often.

Live chat widgets (Intercom, Drift, etc.)

Often 300-500KB, and they run continuously.

  • Alternatives:
  • Lazy-load the widget — only load when user clicks a chat button
  • Use a lighter widget (tawk.to, Crisp) if real-time chat isn't critical
  • Replace with a contact form for most sites

Heatmap / session recording tools

Hotjar, FullStory, Microsoft Clarity all add weight.

Alternative: Run them for 2 weeks, gather data, remove them. Don't leave them on forever.

Ad networks

AdSense, ad servers, trackers — these can be 1MB+ and are typically the single biggest performance killers.

Alternative: If ads are core to your revenue, you have to accept the cost — but at least minimize impact with lazy loading and reserving ad slot space (for CLS).

Multiple analytics

Running GA4 + Hotjar + Mixpanel + Segment + Amplitude — each one costs you.

Alternative: Pick one or two. Most small sites only need GA4 + a simple heatmap tool.

The “does this still matter?” audit

Once a year, go through every third-party script and ask:

  1. Do we still use the service?
  2. Does anyone look at the data it produces?
  3. Could we replace it with something lighter?
  4. Does it need to load on every page, or just some?
  5. Does it need to load immediately, or can it defer?

Making scripts less painful

If you have to keep a script:

  • Add `async` or `defer` so it doesn't block rendering
  • Lazy-load — only load after user interaction
  • Self-host if possible (some scripts allow it)
  • Load on idle: window.requestIdleCallback(() => loadScript())
  • Use a tag manager with performance budgets so you can see costs

How much faster can you get?

Most sites I audit can remove 2-3 scripts entirely and defer 2-3 more, saving 1-3 seconds of load time. Sometimes more.

Need help?

I audit third-party scripts regularly — most audits take an hour and save 30-50% of your mobile load time. Send me a message if you want one done on your site.

Need Help With Your Website?

I fix these problems every day. Send me a message and I'll take a look.

Get Help Now