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.
The targets, measured on mobile
Google publishes a good threshold for each Core Web Vital. Use them as your targets, and measure them on mobile:
- Main content visible (LCP): 2.5 seconds or less
- Response to a tap (INP): 200 milliseconds or less
- Layout stability (CLS): 0.1 or less
Two supporting numbers help explain why a page misses:
- Server response (Time to First Byte): 0.8 seconds or less is Google's general guidance
- First content on screen (First Contentful Paint): 1.8 seconds or less
If your key pages meet the first three for real visitors, your site is fast by the standard Google itself uses. Beyond that point, you are paying for gains most patients will not notice.
Why the target is about your slowest patients
Google judges each metric at the 75th percentile of visits. In practical terms, the page has to be fast for three visits out of four, including patients on older phones, in a parking garage, or on a weak rural signal. An average hides those visits. The 75th percentile does not.
That fits a practice's patient mix better than any office test. Your front desk computer is new and on fast internet. Many of your patients are not. A retiree checking on an old phone whether you take their Medicare Advantage plan is exactly the visit the threshold protects.
It also means a site can feel fast to you and still fail. Test on a phone, on cellular data, before you accept that it is fine. Our guide to mobile versus desktop speed explains why the gap is so large.
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.
Which pages need to hit the target first
Not every page matters equally. Prioritize by where patients arrive and where they decide.
- Your homepage, where name searches and your Google Business Profile link usually land.
- Your top service and condition pages, the ones that bring new patients in from search.
- Location pages, if you have more than one office.
- The booking path, from the Book button to a confirmed time, including any scheduler from your EHR or booking vendor.
- Provider bios, which many patients check before choosing.
Old news posts, staff pages and archives can wait. Search Console's performance report shows which pages actually get visits from search, and how to test your website's speed shows how to check each one.
The booking widget is the page you do not control
Many practices embed a scheduler or intake form from their EHR, practice management system or a booking vendor. That widget usually loads from another company's servers, and its speed is outside your web vendor's hands.
Test it anyway. Tap your own Book button on a phone and time how long it takes until you can pick a real appointment slot. If that takes longer than everything before it, raise it with the vendor, ask whether a lighter embed exists, or open the scheduler on its own page instead of loading it inside every page.
A fast homepage that leads to a slow scheduler still loses the patient, and it loses them at the last step, after they had already decided to book.
Put the targets in writing
Speed is easy to promise and hard to check, so put numbers in your website agreement. A reasonable clause covers four points:
- The homepage, top service pages and location pages meet Google's good thresholds for LCP, INP and CLS on mobile, measured with real user data where available and lab tests where not
- The vendor reports those numbers monthly, not just a 0 to 100 score
- New features, widgets and tracking tags are tested for speed before they go live
- If a key page falls into the poor band, the vendor proposes a fix within an agreed time
This turns speed from a sales adjective into something you can verify. More on what to ask in questions to ask a marketing agency.
When fast enough is fast enough
Once your important pages pass, more speed work has diminishing returns. Google says plainly that it seeks to show the most relevant content even when page experience is sub par, and that good Core Web Vitals do not guarantee top rankings. A page that loads in 1.5 seconds instead of 2.2 is unlikely to outrank a competitor with a far better page about the condition the patient searched.
So treat speed as a floor, not a race. Get every key page into the good band, keep it there as the site grows, then spend the next dollar on what patients use to choose you: clear service pages, real provider bios and easy booking.
Checklist
- Your homepage passes LCP, INP and CLS on mobile
- Your top three service or condition pages pass on mobile
- Each location page passes on mobile
- On a phone over cellular data, a patient can see real appointment times soon after tapping Book
- Server response time on key pages is 0.8 seconds or less
- Your website agreement names the thresholds and requires a monthly report
Frequently asked
Is three seconds the rule for how fast a site should load?
It is not a Google standard. Google's published target is for the largest content element to appear within 2.5 seconds for at least three quarters of visits, plus fast responses to taps and a stable layout. A single load time figure mixes too many things to act on, so use the three Core Web Vitals instead.
Should desktop and mobile have the same targets?
Yes. The thresholds are the same, but Google measures phones and computers separately. Phones usually score worse because they have slower processors and connections, so fix mobile first and then confirm desktop.
How long until improvements show up in Google's data?
Real user data covers a rolling 28 day window, so a fix shows fully after about four weeks. Lab tests reflect the change right away. Use the lab test to confirm a fix worked, and the real user data to confirm patients feel it.
What if my practice gets too little traffic for real user data?
Aim for the same thresholds using the lab test on the mobile setting, which simulates a mid range phone on a slow connection. A page that does well in that test is usually in good shape for real patients. Check your own phone on cellular data as well.
Sources
- Web Vitals, web.dev (Google)
- Time to First Byte (TTFB), web.dev (Google)
- First Contentful Paint (FCP), web.dev (Google)
- Understanding Google Page Experience, Google Search Central
- About PageSpeed Insights, Google for Developers
- Lighthouse throttling documentation, GoogleChrome Lighthouse (GitHub)
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.