How fast does your clinic website need to be?

Think about who's actually loading your site. They're in pain. They've just tapped your ad or your Google listing from a phone, often in a car park, on the train, in bed at 11pm. They are deciding right now whether to book with you or ring the next clinic. They have three other tabs open with three of your competitors. You don't get a second chance and you don't get patience.

When the page makes them wait, they don't sit there admiring your loading spinner. They leave. They tap back to Google and pick the clinic whose site loaded first. The booking you paid for, or earned, never happens. And you never see it, because a patient who bounced off a slow page doesn't fill in a form to tell you why.

I was guilty of this with my own clinics. The site looked beautiful on my screen. I was proud of it. It took six seconds to load on a phone and I had no idea, because I never once loaded it like a patient would. The fancy hero video I loved was the exact thing costing me bookings.

Forget the jargon for a second. The number that matters is how long until a patient can read your headline and tap the book button. Not when the page technically finishes, when it's usable. On a phone, on mobile data, that should be under 2 seconds. Under 1 is excellent. Past 3 you're into the danger zone, and past 4 you're losing about half of them before they've read a word.

Test on a phone, not your laptop. Test on mobile data, not the clinic wifi. Your desktop on a fast connection is the most flattering possible view of your site, and it's the one almost none of your patients will ever see. Roughly two thirds of people finding a clinic are on a phone, often on a patchy connection. That's the reality you're being judged against.

Slow hits you twice, and the second hit is the one most owners never connect. The first cost is obvious once you see it: people arrive, the page is slow, they leave, you lose the booking. The second is quieter. Google measures how fast your site loads and how people behave on it, and it uses that to decide where you sit in the results.

Google's whole business for thirty years has been sending people to the right thing the first time. A slow site that people bounce off is, in Google's eyes, a bad answer. So it shows you to fewer people. Someone lands, waits, leaves, taps back to the results, that back tap is a downvote. A long engaged read is an upvote. Speed feeds straight into that. You end up paying twice for the same problem: fewer visitors arriving, and more of the ones who do arrive leaving.

In almost every slow clinic site I open, it's the same short list of culprits. None of them are exotic. Most are an afternoon to fix once you know what you're looking at. You don't need to become a developer. You just need to know what's weighing the page down so you can get the right person to lighten it.

You don't need a developer to find out where you stand. Two free checks, five minutes, and you'll know more about your site than most clinic owners ever bother to learn. Do the phone test first because it's the honest one, then the tool test to see why.

Start with the phone in your pocket. Turn off wifi, load your homepage on mobile data, and count the seconds until you can read and tap. That's the number your patients live with. Then run your address through Google's free PageSpeed Insights and read the Core Web Vitals. It'll give you a mobile score and, more usefully, tell you exactly what's slowing you down, usually pointing straight at the heavy images and the scripts.

Don't get lost chasing a perfect 100 out of 100, that way lies madness and it isn't the goal. The goal is honest: under 2 seconds on a phone, and the obvious heavy stuff cleared off. It's the worst your site is ever going to be, so the only direction from here is faster.