Performance
Site speed for practice websites: Core Web Vitals in plain terms
The three numbers Google uses to judge how a page feels to a real visitor, what counts as good, and where practice websites usually lose time.
By Mariya Di Luzio, Founder and Creative Strategist ·Published · 6 min read
The short answer
Google measures how a page feels with three Core Web Vitals: the main content should appear within 2.5 seconds, taps should get a response within 200 milliseconds, and the layout should barely jump (a shift score of 0.1 or less).1 Google uses these in ranking, but relevance comes first.2 Speed matters most because patients leave slow pages.
Key takeaways
- The three Core Web Vitals are LCP (loading), INP (responsiveness) and CLS (visual stability).1
- Google counts a page as passing when 75 percent of real visits meet all three thresholds.3
- Many small practice sites have too little traffic for real-visitor data, so the lab test is what you work from.4
- The usual culprits are oversized hero images and video, sliders, page-builder code and third-party widgets.
What are Core Web Vitals?
Core Web Vitals are three measurements Google publishes to describe how a page feels to the person using it. Each one answers a question a patient would ask without knowing the term.1
| Metric | Good | What it measures |
|---|---|---|
| LCP, Largest Contentful Paint | 2.5 s or less | How long until the main content shows |
| INP, Interaction to Next Paint | 200 ms or less | How fast the page reacts to a tap or click |
| CLS, Cumulative Layout Shift | 0.1 or less | How much the page jumps while loading |
Thresholds as published by Google on web.dev.1 Anything above 4 seconds for LCP, 500 milliseconds for INP or 0.25 for CLS is rated poor.3 INP is the newest of the three: it became a stable Core Web Vital in 2024, replacing an older measure of first input delay.1
The CLS number is the one patients feel most. It is the page that moves just as someone goes to tap "Book now", so they tap a banner instead.
How much does speed affect Google ranking?
Less than most agencies imply. Google says plainly that Core Web Vitals are used by its ranking systems, and just as plainly that good scores do not guarantee a page will rank at the top. Its documentation states that Google Search always seeks to show the most relevant content, even if the page experience is sub-par.2
Where speed does count in search is the tie-break. Google notes that where many pages are similarly helpful, a great page experience can contribute to success.2 For a chiropractor competing with six others in the same town, that is exactly the situation.
The bigger reason to care is not Google. A patient on a phone in a car park, on a weak signal, deciding between three practices, will not wait for a slow page to finish loading. Nobody reports that loss to you. It just never becomes an appointment.
Field data or lab data: which number is real?
PageSpeed Insights, Google’s free testing tool, shows two kinds of results, and mixing them up causes most of the confusion.3
- Field data is from real visitors in Chrome over the previous 28 days, on their own phones and connections. It comes from the Chrome User Experience Report (CrUX).3
- Lab data is one simulated page load on a single device with fixed network settings.3 It is useful for finding problems, and it will differ from what real visitors get.
A page passes the Core Web Vitals assessment when the 75th percentile of all three metrics is good. In other words, three visits in four have to meet every threshold.3
Source: Google, PageSpeed Insights.3
Why your practice may have no field data
CrUX only includes sites that are publicly discoverable and have enough visitors to produce a statistically significant dataset.4 Many practice websites do not. When a page has too little data, PageSpeed Insights falls back to the whole site, and when the whole site has too little, it shows no real-visitor data at all.3 That is not a fault. It means the lab result is your working number, and you should test the pages patients actually use, on the mobile setting.
Why are practice websites slow?
These are patterns seen repeatedly when auditing practice sites, not measured industry figures:
- A full-width hero video or an uncompressed photo straight from the camera. Google notes that the resource behind LCP, when there is one, is an image or a web font, and its advice is to compress images, use modern formats and never lazy-load the main image.5
- Homepage sliders that load five large images to show one, and push content around as they cycle.
- Page-builder themes that ship code for every feature the builder offers, whether the page uses it or not.
- Chat widgets, review carousels, booking pop-ups and tracking scripts, each loading its own code from another server.
- Images, embeds and iframes without set dimensions, plus late-loading web fonts. Google lists these as the most common causes of poor CLS.6
Third-party tools deserve the hardest look. Each one arrived with a reason, and nobody removed it when the reason ended. A dental practice with a chat widget nobody answers is paying for that widget in load time on every visit.
How to check your own site in ten minutes
- Open PageSpeed Insights and enter your home page. Choose the mobile result, since that is how most patients arrive.
- Look first for the field data panel. If it shows a result, that is the real-world verdict. If it says there is not enough data, use the lab numbers below it.3
- Repeat for the booking or contact page, and for your most visited service page.
- Read the "Diagnostics" list and note anything that names an image, a video or a third-party script.
- Write down the three numbers per page. Re-test after every change, not once a year.
Speed sits alongside accessibility, claim language and structured data in the technical and compliance rebuild. If you want to see how it fits with being cited by AI assistants, the pillar guide covers the order to do the work in.
When speed work is not the priority
If the site loads in under three seconds on a phone, the booking form works and nothing jumps, stop there. Chasing a perfect 100 in the lab score rarely changes a patient’s decision. In our experience, wrong opening hours, a weak Google Business Profile or unclear pricing cost more appointments than the last half-second does.
Questions practice owners ask
What is a good Core Web Vitals score for a practice website?
Google defines good as a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of real visits. A page passes only when all three are good.
Do Core Web Vitals affect Google ranking?
Yes, but modestly. Google says Core Web Vitals are used by its ranking systems, that good scores do not guarantee top positions, and that it will still show the most relevant content even when page experience is poor. Speed helps most when several pages are similarly helpful.
Why does PageSpeed Insights say there is not enough data for my site?
Real-visitor data comes from the Chrome User Experience Report, which only includes sites with enough traffic to form a statistically significant sample. Many small practice sites do not reach that. Use the lab results instead, test on the mobile setting, and check the pages patients use most.
Will a faster website bring in more patients?
Speed removes a reason to leave; it does not create a reason to book. A fast site with wrong hours, no prices and a thin Google Business Profile still loses patients. Fix speed when it is clearly poor, then put the effort into the facts and trust signals patients check.
Sources, and how much weight each one carries
- Google, web.dev, "Web Vitals", Core Web Vitals definitions and thresholds.Official documentation from the company that defines the metrics.
- Google Search Central, "Understanding page experience in Google Search results".Official documentation. Google describing its own ranking systems, at the level of detail it chooses to share.
- Google for Developers, "About PageSpeed Insights", field and lab data, thresholds and the 75th percentile rule.Official tool documentation. Primary source for how the tool scores a page.
- Chrome for Developers, "Overview of CrUX", Chrome User Experience Report eligibility.Official documentation of the dataset.
- Google, web.dev, "Optimize Largest Contentful Paint".Official technical guidance.
- Google, web.dev, "Optimize Cumulative Layout Shift".Official technical guidance.
This article is about marketing, website and compliance practice. It is not medical or legal advice, and nothing in it is intended to diagnose, treat, cure or prevent any disease. For a decision about your own practice, speak with a qualified attorney or the relevant regulator.
Written by
Founder and Creative Strategist, The Healthy Digital. We help health and wellness practices get found by patients and recommended by AI, with every claim sourced.
