Chat widgets, plugins and third party scripts that slow your site

Updated November 14, 2026 · 4 min read
Short answer

Every widget you add from another company, such as chat, reviews, booking, maps, video or tracking, loads its own code from its own servers, and on phones that code competes with your page. List everything loading on your site, delete what nobody uses, delay what is not needed right away, and load chat and video only when a patient asks for them.

What counts as a third party script

A third party script is any code your site loads from another company. On a practice website the usual list looks something like this:

  • Chat or AI assistant widgets
  • Online booking or intake embeds from your EHR or scheduling vendor
  • Review widgets and testimonial carousels
  • Analytics, tag managers, advertising and social media pixels
  • Call tracking scripts that swap phone numbers
  • Embedded maps and YouTube videos
  • Accessibility overlays, cookie banners and font services

Each one was added for a reason, often by a different person in a different year. Few practices have ever seen the whole list in one place.

How they slow a page down

Third party code costs you in two ways.

Network. Each script means more requests to more servers, each with its own connection to set up. If a script is loaded in a way that holds up the page and its server is slow, your whole page waits for someone else's server.

Processing. Once downloaded, the code has to run, and on a phone it runs on a modest processor. While a chat widget starts up or a review carousel builds itself, the phone may not respond to taps. That delay is what Interaction to Next Paint measures: the gap between a tap on your Book button and anything visibly happening. Google's guidance on INP points to long tasks from running scripts as a main cause. See Core Web Vitals in plain English.

See your Surge Score in about a minute

Does ChatGPT recommend your practice?

The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.

Take an inventory

Before cutting anything, find out what is there.

  1. Run your homepage through PageSpeed Insights on mobile and look through the diagnostics for third party code, which shows which outside companies load code and how much time it takes.
  2. Ask your web vendor for a written list of every script, tag, plugin and embed on the site, with who added it and why.
  3. If you use a tag manager, have someone open it and list every tag inside. Tag managers are where old campaigns tend to live on long after they end.
  4. Note which pages each item loads on. A chat widget meant for every page is different from a map needed only on the contact page.

Put it all in one spreadsheet, with a column for the owner and a column for whether anyone still uses it.

Keep, delay or delete

Go down the list and put each item in one of three groups.

  • Delete: tracking for ad campaigns that ended, a second analytics tool nobody reads, a social feed nobody watches, duplicate tags, apps installed for a trial. Google's guidance is simple here: routinely audit and clean out redundant third party scripts.
  • Delay: anything not needed in the first few seconds. Scripts can be marked to load without holding up the page. Maps and videos further down can load when the patient scrolls to them.
  • Keep, but limit: tools that drive bookings. Load them only on the pages that need them. An insurance checker belongs on the insurance page, not on every blog post.

Every deletion also shrinks the list of companies receiving data about your visitors, which matters for a medical practice.

Facades: load chat or video only when someone asks

A facade is a lightweight stand in that looks like the real widget but is just an image and a button. The real chat or video loads only when the patient taps it. Google's Lighthouse documentation recommends facades for video embeds such as YouTube and Vimeo and for chat widgets.

For a practice, this can be one of the easiest wins available. Every visitor pays the cost of a chat widget that loads automatically, but only the visitors who open it get anything from it.

The tradeoffs are real. There is a short delay the first time someone taps, and features such as unread message badges will not work until the real widget loads. If your chat is an important after hours booking channel, test the facade on a phone to make sure it still feels quick. See AI chat on a medical website.

Privacy is a second reason to cut

Speed is not the only cost. Advertising and social media pixels on pages where patients describe symptoms, request appointments or read about specific conditions can send information about those visits to other companies. That is a privacy question as well as a speed question, and it deserves a careful look rather than a default of leaving everything on.

When you review your scripts for speed, flag every tracking tag on a page where a patient might reveal health information, and ask whether it needs to be there at all. Fewer tags mean a faster site and less data leaving it. See tracking pixels on pages where patients enter health information.

Checklist

  • You have one written list of every script, tag, plugin and embed on the site
  • Each item has an owner and a reason to exist
  • Tags for ended campaigns and unused tools are deleted
  • Analytics and below the fold embeds load after the main content
  • Chat and video embeds use a facade or load on tap
  • Booking and insurance tools load only on the pages that need them
  • No advertising pixel runs on pages where patients enter health information

Frequently asked

Should I remove the chat widget to speed up my site?

Not necessarily. If chat brings in bookings, keep it and load it lightly, with a facade so it starts only when someone taps. If nobody has booked through it in months, removing it may be the simplest speed improvement you can make.

Does a tag manager slow down my site?

The bigger cost is usually what is inside it. A tag manager container that has collected years of old tags can load a lot of code on every page. Review its contents at least twice a year and remove anything tied to finished campaigns or tools you no longer use.

Can my web vendor just make the scripts load faster?

Partly. They can load scripts so they do not hold up the page, defer less critical ones, connect early to important outside servers and use facades. They cannot make another company's code smaller. Removing a script is the only way to remove its cost entirely.

What about the booking widget from my EHR?

Keep it, because it is how patients book, but load it on the booking page or when the patient taps Book rather than on every page. Ask the vendor whether a lighter embed or a direct link to their scheduler is available.

Sources

  1. Third-party JavaScript performance, web.dev (Google)
  2. Efficiently load third-party JavaScript, web.dev (Google)
  3. Lazy load third-party resources with facades, Chrome for Developers
  4. Optimize Interaction to Next Paint, web.dev (Google)
  5. Interaction to Next Paint (INP), web.dev (Google)
Prefer to talk it through?

Book a strategy call with the team.

Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.

AI patient discovery audit

Is AI recommending you, or your competitor?

See who ChatGPT, Gemini and Perplexity recommend to patients in your area.

Free. Built by physicians.