Page speed matters: a practical guide for medical practices

11 guides · Updated November 14, 2026
Short answer

A slow practice website loses patients before they read a word, and many of them are on a phone. Google measures speed with three Core Web Vitals taken from real visits: how fast the main content appears, how quickly the page responds to a tap, and how much the layout jumps. Many practice sites can pass all three with ordinary fixes to images, scripts and hosting.

Why speed is a front desk problem

Think of your website as the first few seconds of a phone call. If the line rings and rings, some callers hang up. A web page that shows a blank screen on a phone does the same thing, and you never see the patients who left.

Speed also shapes the visits you do get. A booking button that does nothing for a second after a tap gets tapped twice, or abandoned. A page that jumps as a banner loads sends a thumb to the wrong link. None of this shows up in your practice management system. It shows up as fewer new patient calls and online bookings than your traffic should produce.

Google cares for related reasons. It says Core Web Vitals are used by its ranking systems, while relevance still comes first. That is why this series spends as much time on patients as on rankings.

Start here

If you only have time for four guides, read these in order. Together they take you from understanding the numbers to handing your web vendor a fix list.

The full list below covers hosting, platforms, widgets, rankings and what patients do while a page loads.

What you control, and what your vendors control

Speed problems on practice sites come from four places, and each has a different owner.

  • Content: photos, videos and sliders. Your team usually adds these and can often fix them without help.
  • Widgets and tags: chat, reviews, maps, tracking pixels and booking embeds. You decide which vendors are on your site, so you decide which stay.
  • Platform and hosting: the template, the server and caching. These belong to whoever built and hosts the site.
  • The scheduler and portal: usually loaded from your EHR or booking vendor, and only that vendor can speed them up.

When you raise speed with any of them, ask for numbers, not adjectives. "The site is fast" is a claim. "The homepage passes all three Core Web Vitals on mobile" is something you can check yourself in five minutes.

Three things practice owners often get wrong

Chasing a perfect lab score. The 0 to 100 performance score is a simulation. Google's Core Web Vitals come from real visits, and passing those is the goal.

Testing on the office computer. A new desktop on fast office internet hides almost every problem. Your patients are on phones, often older ones, on cellular data. Always test mobile first.

Using an outdated scorecard. Interaction to Next Paint replaced First Input Delay as a Core Web Vital on March 12, 2024. A report that still grades you on First Input Delay is measuring the wrong thing.

Every guide in this series

  1. 1
    What page speed is and how Google measures it: Core Web Vitals in plain English

    Google measures page speed with three Core Web Vitals: Largest Contentful Paint, how fast the main content appears (good is 2.5 seconds or less); Interaction to Next Paint, how fast the page responds to a tap (200 milliseconds or less); and Cumulative Layout Shift, how much the page jumps (0.1 or less). Each is scored from real visits, separately for phones and computers.

  2. 2
    How fast should a medical practice website load?

    Aim for the main content to appear within 2.5 seconds, taps to respond within 200 milliseconds and almost no layout jumping, for at least three out of four real visits on phones. Those are Google's good thresholds for Core Web Vitals, and they are the right target for your homepage, top service pages, location pages and booking path.

  3. 3
    How to test your website's speed, and which number actually matters

    Run your key pages through Google's free PageSpeed Insights on the mobile setting and read the top section first: the Core Web Vitals assessment from real visitors. That pass or fail result is the number that matters. The 0 to 100 performance score below it is a lab simulation, useful for finding problems but not the grade Google uses.

  4. 4
    Mobile speed versus desktop speed: why the phone score is the one to fix

    Your mobile score is lower because speed tests simulate a mid range phone on a slow mobile connection, and real phones have less processing power than office computers. Fix mobile first: Google uses the mobile version of your pages for indexing and ranking, and it scores phones and computers separately.

  5. 5
    Images: why photos slow down practice websites, and how to fix them

    Images are often the heaviest part of a web page, and practice sites tend to use big ones: the team, the office, the providers. Resize each photo to the size it is shown, save it in a modern format such as WebP or AVIF, give it fixed dimensions, and never lazy load the main photo at the top of the page.

  6. 6
    Cheap hosting and what it costs you in patients

    Hosting shows up in speed tests as server response time, or Time to First Byte, and Google's guidance is to aim for 0.8 seconds or less. If your pages are slow before a single image loads, the server is the bottleneck, and no amount of photo compression will fix it. Better hosting, caching and a content delivery network often will.

  7. 7
    Wix, Squarespace, WordPress: does the platform change your speed?

    Less than most people think. Hosted builders like Wix and Squarespace handle hosting and image processing for you but limit how far you can tune; WordPress lets you control everything and leaves everything to you. On any platform, the photos, widgets and apps you add usually decide whether the site is fast.

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

    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.

  9. 9
    Does speed affect your Google ranking? The honest answer

    Yes, but less than many vendors imply. Google says Core Web Vitals are used by its ranking systems, yet it also says it always tries to show the most relevant content even when page experience is poor. Speed rarely lifts a weak page past a better one; it matters most when competing pages are similarly useful.

  10. 10
    Speed and conversions: what patients do while a page loads

    While a page loads, a patient is deciding whether to wait, tap back or try the next practice. Published experiments, mostly from retail, show that faster pages can lift sales, but there is no public healthcare benchmark worth quoting. The reliable way to know what speed is worth to you is to measure bookings and calls before and after a fix on your own site.

  11. 11
    A one hour speed checklist for practice managers

    In one hour, without a developer, you can measure your key pages, find the oversized images and unneeded widgets, check hosting and Search Console, and hand your web vendor a short, specific list of fixes. Work in four 15 minute blocks and write down every number with the date.

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.

Frequently asked

How fast should my practice website be?

Aim for Google's good thresholds on mobile: the main content visible within 2.5 seconds, taps answered within 200 milliseconds and a layout shift score of 0.1 or less, for at least three out of four real visits. Those are the numbers Google uses, and many practice sites can reach them without a rebuild.

Does page speed affect my Google ranking?

Somewhat. Google says Core Web Vitals are used by its ranking systems, but also that it always tries to show the most relevant content even when page experience is poor. Speed helps most when your pages are as useful as a competitor's. It matters even more for whether visitors stay and book.

Do I need a developer to fix a slow site?

Not always. Resizing photos, removing unused widgets and replacing a slider with one good image are often within your team's reach. Changes to the template, hosting, caching or how scripts load usually need whoever built the site.

Which pages should I test first?

Your homepage, your busiest service or condition page, one location page and the page your Book button opens. Those are where new patients usually arrive and decide, so they are where speed costs you the most.

Sources

  1. Web Vitals, web.dev (Google)
  2. Understanding Google Page Experience, Google Search Central
  3. Interaction to Next Paint becomes a Core Web Vital on March 12, web.dev (Google)
Related series

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.