Third-Party Scripts: How Chat Widgets, Trackers and Embeds Slow Your Website

On this page

1. What counts as a third-party script
2. How they slow your site down
3. Step 1: List everything your site loads
4. Step 2: Measure what each one costs
5. Step 3: Remove, restrict or delay
6. Don't break your tracking
7. Keep it from creeping back

You can compress every image and install the best caching plugin, and still have a slow website. Often the culprit isn't your site's own code at all, but the scripts it loads from other companies: chat widgets, tracking pixels, embedded videos, review badges and ad tags. Each one was added for a good reason. Together, they can make up a large share of the code on your pages. Here's how to find them, measure their cost and decide what stays.

What counts as a third-party script

A third-party script is code loaded from someone else's server rather than your own. On a typical business website that includes:

• Analytics and tag managers: Google Analytics, Google Tag Manager, heatmap and session-recording tools
• Ad and remarketing pixels: Meta, Google Ads, LinkedIn and others
• Chat and support widgets: live chat, chatbots and floating WhatsApp widgets
• Embeds: YouTube videos, Google Maps, Instagram feeds, booking and calendar widgets
• Trust and marketing tools: review widgets, pop-up and notification tools, cookie banners
• Ads: display ad networks on blogs and content sites
• Spam protection: CAPTCHA scripts, sometimes loaded on every page instead of only where forms are

How they slow your site down

• Extra connections: every new domain means the browser has to look it up and connect before downloading anything
• Heavy JavaScript: many widgets download far more code than their small bubble or badge suggests, and budget phones take longer to process it
• Slower taps and clicks: while a phone is busy running third-party code, it can't respond to the visitor, which hurts Interaction to Next Paint (INP)
• Layout jumps: ads, banners and embeds that appear late push content around, hurting CLS
• Chains: one tag often loads several more scripts, which load more again
• No control: the provider can change or enlarge its script at any time, and your site slows down without you changing anything

For what INP and CLS mean, see Core Web Vitals explained.

Step 1: List everything your site loads

Scripts get added in many places over the years, so check them all:

1. Plugins: chat, pop-up, analytics, social feed and review plugins
2. Header and footer code: your theme options, page builder settings or a "header scripts" plugin, where pixels are often pasted
3. Google Tag Manager: open the container and list every tag, including old campaign tags nobody removed
4. Individual pages: embeds added to single pages or landing pages

For each item, write down who added it, what it's for and whether anyone still uses it. It's common to find the same analytics tag installed twice (once by a plugin and once in Tag Manager), pixels from an agency you stopped working with, or a heatmap tool whose trial ended long ago.

Step 2: Measure what each one costs

• PageSpeed Insights: run your key pages on mobile and look for the section on third-party code, which lists each provider and how much main-thread time it uses. See speed test tools explained.
• Chrome DevTools: the Network tab shows every request and which domain it came from. Its request blocking feature lets you block one script's domain, reload, and see how the page behaves without it.
• Test before and after: whenever you add a new tool, run the same page through PageSpeed Insights before and after, so you know what it costs.

Step 3: Remove, restrict or delay

Script	Common problem	Better approach
Old pixels and trial tools	Loading for no reason	Remove them
Chat widget	Heavy code on every page, before anyone chats	Load it only when the visitor taps a chat button, or after they interact with the page
WhatsApp widget plugin	Scripts for a feature a simple link can do	A plain click-to-chat link button needs no script; see WhatsApp on your website
YouTube and map embeds	Players and map code load on page open	Preview image that loads the real embed on tap, and only on pages that need it
Social feeds and review widgets	Heavy scripts for a small section	Show a few curated items directly on the page, or load the widget lower down and lazily
CAPTCHA	Loaded site-wide	Load only on pages with forms, if your form plugin allows it

Performance plugins such as WP Rocket, LiteSpeed Cache and Perfmatters include options to defer or delay JavaScript until the visitor scrolls, taps or moves the mouse. This can make a big difference, but test carefully: delayed scripts sometimes break sliders, menus or forms, so check every important feature afterwards. Features change between versions, so check what your current plugin offers.

Don't break your tracking

Delaying analytics and ad pixels speeds up the page, but it has a trade-off. Visitors who leave within a second or two may not be counted, and ad platforms may see fewer conversions. After any change:

• Submit a test enquiry and confirm it still shows up as a conversion in Google Analytics and your ad accounts
• Compare visitor numbers for a week or two before and after
• Keep conversion tags reliable, even if you delay less important scripts more aggressively

Tag Manager helps you organise tags, but it doesn't make them free. A container full of tags still loads all of them.

New to Tag Manager? Our guide to Google Tag Manager basics explains how to set it up, test it and keep the container lean.

Keep it from creeping back

• Keep a simple list of every third-party tool on the site, who owns it and why
• Agree a rule with your team and agencies: new scripts get tested for speed before going live
• Review the list every few months and remove anything unused
• Keep ad landing pages especially lean, since paid visitors are the most expensive ones to lose; see landing page mistakes

If you suspect third-party scripts are dragging your site down, a WordPress speed optimisation audit will show exactly what each one costs. Running ads? I also build fast, lean landing pages that keep tracking intact.