Hey there, Jason Koeppe here from SurePath Digital.
Here's a fun experiment. Go stand in your parking lot, turn off Wi-Fi on your phone and open your own website.
Go ahead. I'll wait.
...
Still loading? Is there a gray box where your hero image should be? Did the "Book Now" button jump down right as you went to tap it, so you accidentally tapped "Our Philosophy" instead?
Congratulations. You just experienced your website the way a lot of your patients do. On a phone, on cellular data, mildly annoyed and one thumb away from the back button.
Nobody calls to tell you your site is slow. They just leave.
The Big Three: Google's Core Web Vitals in plain English
Google boils page experience down to three measurements called Core Web Vitals. Here's what each one means and what "good" looks like, according to Google's own Web Vitals guide on web.dev (web.dev, by Philip Walton of the Chrome team, last updated October 31, 2024):
| Metric | What it measures | In plain English | Good |
|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading | How long until the biggest thing on screen shows up | Within 2.5 seconds |
| INP (Interaction to Next Paint) | Responsiveness | How fast the page reacts when someone taps | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | Visual stability | How much stuff jumps around while loading | 0.1 or less |
Two details from that guide worth knowing:
- Google suggests measuring at the 75th percentile of page loads, on mobile and desktop separately. In other words, the page should be good for most visits, including the slower ones.
- A page passes when it meets the target on all three.
That jumping "Book Now" button from the parking lot? That's CLS. And yes, it's as annoying in the data as it is in real life.
The 10-Minute Speed Check
Keep your homepage open on your phone while you run the tests below. You'll compare the report with what a patient actually sees, including that booking button you've been waiting to tap.
Minutes 0-3: Test your homepage on mobile
- Go to PageSpeed Insights (Google's free tool).
- Paste in your homepage address and hit Analyze.
- Click the Mobile tab first. Mobile is where a lot of your patients are, and it's usually the slower result.
You'll see two sections, and they're different things:
- Real-user data at the top. This comes from real Chrome users visiting your site. If your site doesn't have enough traffic, this section may say there's not enough data. That's normal for smaller clinic sites.
- Lab data below it, including the famous Performance score from 0 to 100. This is a simulated test run on the spot.
Minutes 3-5: Read the Big Three
Look at the real-user section first. Does it say your Core Web Vitals assessment passed or failed? Which of the three is red or orange?
No real-user data? Use the lab numbers instead. One catch: lab tests can't measure INP, because nobody's actually tapping anything. They show Total Blocking Time (TBT) instead, which the web.dev guide calls a lab proxy for INP. High TBT usually means too much JavaScript.
And please don't panic about the Performance score. It bounces around between runs. Run it three times, look at the range and focus on whether the Big Three pass.
Minutes 5-8: Find the heavy stuff with GTmetrix
- Go to GTmetrix and run the same page.
- Open the Waterfall tab. It's a list of every file your page loads, in order, with how long each took.
- Sort or scan for the biggest and slowest items.
This is where you'll usually find the culprit. A 4 MB photo of your lobby. A slider with six full-size images. A chat widget, two tracking pixels, a review widget and a font library, all loading before the page does.
Screenshot it. That's your fix list.
Minutes 8-10: Feel it on your own phone
Numbers are great. Your thumb is better.
Turn off Wi-Fi and open your homepage and your most popular service page. Ask:
- How long until I can see what this clinic does?
- Does anything jump while I'm trying to tap?
- Can I tap "Book" or "Call" without waiting?
If you catch yourself drumming your fingers, a patient is doing the same thing, right before they leave.
The usual suspects (and what to do about them)
On clinic sites, especially WordPress sites, slow pages usually come down to the same handful of things:
- Giant images. Photos uploaded straight from a camera or phone. Fix: resize them to the size they actually display at, convert to WebP and compress.
- Sliders and autoplay video on the homepage. They load a lot of heavy files before the patient sees anything useful. Fix: replace with one strong image, your headline and a booking button.
- Plugin pileup. Forty plugins, nine of which nobody remembers installing. Fix: remove anything you don't use, and replace overlapping ones.
- Third-party script stacks. Chat widgets, pop-ups, tracking tags, review feeds and social embeds. Each one adds weight and can hurt INP. Fix: keep the ones that earn their spot, and delay the rest until after the page loads.
- Layout jumpers (CLS). Images without set dimensions, banners that load late and push things down, fonts that swap after loading. Fix: set image width and height, reserve space for banners and preload your main font.
- Cheap hosting. If the server itself is slow to respond, nothing else fully fixes it. Fix: move to quality managed hosting with caching and a CDN (a network that serves your files from a location close to each visitor).
Start with images. They're usually the biggest win for the least effort.
Speed is one leak. Here are the others.
A fast site that confuses people is just a faster way to lose them. Once speed is handled, run the rest of the Six-Leak Audit on your clinic website: headline, booking button, form, proof and next step.
Speed also helps with the robots. Fast, crawlable pages are part of the "A" in the CLEAR plan for getting recommended by ChatGPT.
What happens when the site gets fast
Speed work is unglamorous. Nobody throws a party for a smaller image file. But it makes every visitor you've paid for more likely to stick around long enough to book.
If you'd rather never think about this again, that's what our Unlimited WordPress hosting and support is for: managed hosting, speed optimization, backups and site changes, handled.
The 125+ clients we've worked with average a 71% increase in ROI over their first three months. Our wider set of systems has been behind about $85M in collective client sales.
For the details of one campaign, see how the pain clinic reached a 1,010% ROI. That owner was three weeks away from closing his only clinic at the outset. In less than 60 days, he had moved on to planning how to open and fill a new clinic each quarter.
Frequently asked questions
How do I test my website's speed?
Go to Google PageSpeed Insights, paste in your homepage address and look at the mobile results first. Check whether your Core Web Vitals pass, then run the same page through GTmetrix to see which files load slowest. Finally, open the page on your own phone using cellular data and see how it feels.
What are Core Web Vitals?
They're three measurements Google uses to describe how a page feels to real visitors. Largest Contentful Paint (LCP) measures loading, Interaction to Next Paint (INP) measures how quickly the page responds when someone taps or clicks, and Cumulative Layout Shift (CLS) measures how much things jump around while the page loads.
What is a good Core Web Vitals score?
According to Google's web.dev guidance, a good experience means LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less. Google suggests measuring at the 75th percentile of page loads, on mobile and desktop separately, and a page passes when it meets all three.
Why is my PageSpeed score different every time I test?
The performance score comes from a simulated test, and results shift with server load, network conditions and what's running on the page at that moment. Run it a few times and look at the range. The real-user data section, when your site has enough traffic to show it, is the steadier number to watch.
What usually slows down a clinic website?
Oversized images are a very common culprit, along with homepage sliders and autoplay video, too many plugins, stacks of third-party scripts like chat widgets and tracking tags, heavy page builders and low-cost shared hosting. Fixing the images and removing what you don't need usually makes a noticeable difference before you touch anything technical.
What's your next move?
Go stand in the parking lot, turn off Wi-Fi and open your site. Then run the 10-Minute Speed Check and start with the images.
Want help? Book a call with me. We'll run the check on your site together, read the Big Three and tell you what to fix first.
Until next time, God bless and talk soon.
