Why seconds cost patients
Patients open your site on a phone — often on mobile data, often on the move. Every second of waiting is a share of people who gave up and went back to the results, to a competitor. Google knows it, which is why speed (Core Web Vitals) is an official ranking factor: a slow site loses patients and positions at the same time.
What actually slows medical websites down
All-in-one template themes. A marketplace theme ships code for a thousand features you don't use — and every patient downloads all of it.
Carousels and sliders on the home page. Five large photos load at once when the patient will see one.
Third-party widgets. Chats, maps, counters, messenger buttons — each drags its own scripts. Three widgets easily double load time.
Photos straight off the camera. An 8MB shot where 200KB would do — the most common and cheapest-to-cure problem.
Test your site in 2 minutes
- Open pagespeed.web.dev and paste your address
- Read the mobile score, not desktop: patients arrive on phones
- Three numbers: Performance (aim for 90+), LCP (under 2.5s), CLS (under 0.1 — so the page doesn't "jump")
- Repeat for a service page, not just the home page
| Symptom | Likely cause | Treatment |
|---|---|---|
| A long white screen, then everything at once | a heavy font/theme blocks rendering | critical CSS optimisation |
| The main photo loads last | unoptimised images | compression + modern formats |
| The page "jumps" while reading | images without dimensions, banners | fixed sizes, a CLS audit |
| The score drops after adding a chat | third-party scripts in the critical path | deferred widget loading |
What to do about it
On custom code these are contained fixes: image optimisation, deferred widgets, a clean critical path. On a builder or a heavy template, speed has a ceiling no fix can break: the platform's code always loads. Our sites hold LCP under 1.5s and Lighthouse 90+ not by magic but by architecture: static code, optimised images, zero unnecessary scripts.
A working example: the Efedra clinic site holds Lighthouse Performance 98 after its rebuild — one of the reasons Google visits quadrupled in 6 months. Full breakdown — in the case study.