A slow mobile site and huge uncompressed images

Updated November 14, 2026 · 4 min read
Short answer

Most practice websites are slow on phones for a few fixable reasons: oversized photos, too many third party scripts and underpowered hosting. Test your key pages on mobile with PageSpeed Insights, fix the images first, and aim to pass Google's Core Web Vitals thresholds for real visitors.

Why mobile speed is the number that counts

Your office tests the website on a desktop over fast office internet, and it feels fine. Your patients open it on a phone, often on a cellular connection, often in a hurry. That is the experience that decides whether they wait for the page or go back to the search results.

It is also the version Google looks at. Google's documentation says it uses the mobile version of a site's content, crawled with a smartphone agent, for indexing and ranking. A site that is quick on desktop and sluggish on phones is, for practical purposes, a slow site.

Test it in five minutes

Go to PageSpeed Insights, which is free from Google, and test three pages: your homepage, your busiest service page and the page where patients book.

Look at two different things on the results page:

  • Field data, labeled as what real users are experiencing. It comes from the Chrome User Experience Report and covers the previous 28 days. This is the closest thing to the truth about your patients.
  • Lab data and the performance score, from a simulated load on one device. It is useful for finding causes, but it is not what your patients saw.

Google's Core Web Vitals give you the targets. Largest Contentful Paint, which measures how quickly the main content appears, should happen within 2.5 seconds. Interaction to Next Paint, which measures how fast the page responds to a tap, should be 200 milliseconds or less. Cumulative Layout Shift, which measures how much the page jumps around while loading, should be 0.1 or less. A page passes when real visits meet all three at the 75th percentile.

Smaller practice sites often do not have enough traffic for field data. In that case, use the lab results, and also open the site on your own phone with wifi turned off. For more, see how to test your website's speed.

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.

The usual culprit is images

A professional photographer delivers files several thousand pixels wide. Someone uploads them straight to the homepage slider, five of them, and the page asks every patient's phone to download photos large enough to print as posters.

Google's image guidance notes that images are often the largest contributor to overall page size. The fixes are well known:

  • Resize each image to the largest size it will actually display
  • Compress it and use a modern format such as WebP or AVIF
  • Serve smaller versions to phones, which developers do with responsive image markup
  • Load images further down the page only when the patient scrolls to them, but never delay the main image at the top
  • Replace autoplaying sliders with one strong image

See images: the most common reason practice websites are slow.

Other things that slow practice sites

After images, the common causes on medical practice sites are:

  • Third party scripts: chat widgets, review widgets, booking widgets, several analytics and ad tags, heat maps and accessibility plugins, each loading its own code
  • Video backgrounds on the homepage
  • Heavy page builder themes that load features you do not use
  • Many custom fonts
  • Budget shared hosting that responds slowly before anything else can load
  • Old plugins that nobody has reviewed in years

Third party scripts deserve special attention because each one was added for a reason and nobody wants to remove theirs. List them, ask what each one is for, and remove any that cannot show its value. More in chat widgets, plugins and third party scripts.

What to fix first

Work in this order, retesting after each step:

  1. Compress and resize every image on the homepage, top service pages and booking page.
  2. Remove scripts and plugins that no one can justify.
  3. Delay chat and review widgets so they load after the main content.
  4. Remove video backgrounds and homepage sliders.
  5. If the server is still slow to respond, move to better hosting.
  6. Only then look at deeper code changes.

Do not chase a perfect score of 100. A page that loads its main content quickly for real patients, responds immediately to taps and does not jump around has done its job.

Speed and ranking, honestly

Google says Core Web Vitals are used by its ranking systems, and also that good scores do not guarantee top rankings and that it always seeks to show the most relevant content, even if the page experience is not great. Speed will not rescue a page that does not answer the patient's question.

The stronger reason to fix speed is what happens to the visitors you already have. A patient who gives up while your homepage loads never sees your booking button. For the full picture, read does speed affect your Google ranking.

Checklist

  • You have tested your homepage, top service page and booking page on mobile
  • You know whether real visitors pass Core Web Vitals, or that you lack field data
  • Every image is resized, compressed and in a modern format
  • Homepage sliders and video backgrounds are gone
  • Every third party script has an owner and a reason
  • Chat and review widgets load after the main content
  • You have opened the site on your own phone on cellular data

Frequently asked

What is a good PageSpeed Insights score for a practice website?

Google's tool treats a lab score of 90 or above as good. The more important result is the Core Web Vitals assessment from real visitors, when your site has enough traffic to show it. A passing assessment with an imperfect score is better than the reverse.

Does our website platform make us slow?

It can, but the platform is rarely the whole story. Most practice sites on any major platform can be made reasonably fast by fixing images, scripts and hosting. If you cannot control those things on your platform, that is a real limitation worth weighing.

Will a chat widget hurt our speed?

Many chat widgets load a lot of code. Set them to load after the main content, or only after the patient interacts with the page, and check the speed before and after. If a widget adds real bookings, keep it and tune it; if not, remove it.

How often should we test speed?

After any change to the site, after adding any new widget or tag, and once a month as a routine check. Speed tends to decay as people add things, so a regular check catches the slide early.

Sources

  1. Web Vitals, web.dev
  2. About PageSpeed Insights, Google for Developers
  3. Mobile-first Indexing Best Practices, Google Search Central
  4. Image SEO Best Practices, Google Search Central
  5. Understanding Google Page Experience, Google Search Central
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.