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.
The first seconds of a visit, step by step
Picture a hypothetical patient with a painful tooth, searching on her phone during a lunch break. She taps a dental practice's listing.
- For the first moment she sees a blank white screen, and she is already deciding whether this is worth the wait.
- The logo and menu appear, but the main area stays empty while a large photo loads. She scrolls, finds nothing, and scrolls back up.
- The photo arrives and pushes the text down. She taps where the Book button was and opens the patient portal login instead.
- She goes back, taps Book, and nothing happens for a second because a chat widget is still starting. She taps again.
Every one of those moments is a chance to leave, and the back button is always one tap away. Nothing in the practice management system records her. She simply becomes someone else's new patient.
What the published evidence shows, and what it does not
Google's web.dev site collects case studies from companies that measured the business effect of speed. One of the clearest comes from Vodafone, which ran an A/B test on a landing page: the version with a 31 percent better Largest Contentful Paint produced 8 percent more sales, with no other functional or visual differences.
Two cautions before you apply that to a practice. First, these are retailers, publishers and telecom companies, not clinics. A patient in pain may wait longer than a shopper comparing phone plans, and a patient browsing elective procedures may wait less. Second, published case studies tend to be the successes. The speed project that changed nothing rarely gets written up.
What the evidence supports is the direction: when a page gets meaningfully faster for real users, more of them finish what they came to do. How much is something you measure, not something you borrow.
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.
Three ways speed loses bookings
Each Core Web Vital maps to a specific way patients drop off.
- Slow main content (LCP). The patient sees a blank or half built page and goes back to the search results. This is the most visible loss.
- Unresponsive taps (INP). The patient taps Book or Call and nothing happens, so they tap again, open the wrong thing or give up. On a booking or intake form, a laggy page makes every field feel like work.
- A jumping layout (CLS). The patient taps the wrong link because the page moved. Calling the billing line instead of scheduling, or landing on the portal instead of new patient booking, is a quiet way to lose a visit.
When you read a speed report, translate each red number into which of these is happening to your patients. See what Core Web Vitals measure if the terms are new.
The booking step is where speed costs the most
A patient who has tapped Book has made a decision. Losing them at that point is the most expensive loss on your site, and it is often the slowest step, because the scheduler usually loads from your EHR or booking vendor rather than your own site.
Time it yourself on a phone over cellular data, from tapping Book to seeing real appointment times. Then count the steps to a confirmed visit. If the scheduler takes several seconds to appear, opens in a window that looks like a different website, or asks for details the patient does not have handy, that is where to focus first. Speed and simplicity work together here. See online scheduling that writes into your EHR.
Measure the effect on your own site
You do not need a lab to see whether speed matters for your practice. You need a before and an after.
- Pick one change with a clear date, such as compressing the homepage hero, removing unused widgets or moving to better hosting.
- Record the four weeks before: visits to the page, clicks on Book and Call, booking starts and completed bookings.
- Make the change and confirm it with a lab test the same day.
- Record the four weeks after, and compare with the same weeks last year if your practice is seasonal.
- Note anything else that changed in the same period, such as an ad campaign or a review push.
It will not be a perfect experiment, but it is your data from your patients. Set up click and call tracking first, covered in measuring button clicks and calls.
Speed matters most when you pay for the visit
If you run Google Ads or other paid campaigns, every visitor who leaves during a slow load is a click you paid for and lost. A slow landing page wastes budget in a way you can see on an invoice, and raising the budget only buys more of the same losses.
Check Core Web Vitals and the booking path on every ad landing page before increasing spend, and recheck after any change to the page. See why ads fail on websites that do not convert.
Checklist
- You have timed the path from Book to real appointment times on a phone
- Clicks on Book and Call are tracked as events
- Each speed fix has a date, so you can compare before and after
- You compare four weeks before and after, and the same period last year if seasonal
- Ad landing pages pass Core Web Vitals on mobile before budgets go up
Frequently asked
How much will a faster site increase my bookings?
Nobody can honestly tell you in advance. Published experiments show gains in other industries, but your patients, specialty and booking setup are different. Measure a before and after on your own site; that number is worth more than any borrowed benchmark.
Is there a load time where patients give up?
No reliable source has published a single cutoff for healthcare, and patients with urgent needs behave differently from patients comparing elective options. Use Google's thresholds as your target: main content within 2.5 seconds, taps that respond within 200 milliseconds and a stable layout.
Do patients really leave a doctor's website because it is slow?
Some will, and you will never hear from them. When several practices appear in the results, going back and trying the next one costs the patient nothing. A slow page makes that the easiest choice.
Should I speed up the site or the booking widget first?
Whichever is slower for a patient on a phone. If the homepage is fine but the scheduler takes several seconds to appear, the scheduler is costing you more, because those patients had already decided to book.
Sources
- Why does speed matter?, web.dev (Google)
- Vodafone: A 31% improvement in LCP increased sales by 8%, web.dev (Google)
- Web Vitals, web.dev (Google)
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.