Core Web Vitals are Google's three measurements of how a page feels to a real visitor: how fast the main content appears, how quickly the page responds to a tap, and whether things jump around while it loads. Developer documentation explains the math. This page explains what each one means on a practice website, where to find your scores, and the culprits that show up on medical sites again and again.
In short: Core Web Vitals are three scores from real Chrome visitors: Largest Contentful Paint (good at 2.5 seconds or less), Interaction to Next Paint (200 milliseconds or less) and Cumulative Layout Shift (0.1 or less). On practice sites, oversized photos, sliders, chat widgets and late-loading badges cause most failures. Fix phones first.
People look this up a lot: "core web vitals" draws 2,400 searches a month in the US and 390 in Canada, "largest contentful paint" 720, "cumulative layout shift" 390 and "interaction to next paint" 140 (Google Ads Keyword Planner data via DataForSEO, US and Canada, 12-month average to Sep 2026).
Core Web Vitals in one paragraph
Google's web.dev (opens in a new tab) defines three metrics and a "good" threshold for each, measured at the 75th percentile of page loads and split between phones and desktops. That means a page passes only if at least three in four real visits meet the mark. They are "first and foremost, field metrics", gathered from real Chrome users, not from a test in a lab. Interaction to Next Paint replaced First Input Delay (opens in a new tab) on March 12, 2024. All thresholds below were checked on October 22, 2026.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | 2.5 s or less | 2.5–4 s | Over 4 s |
| Interaction to Next Paint (INP) | 200 ms or less | 200–500 ms | Over 500 ms |
| Cumulative Layout Shift (CLS) | 0.1 or less | 0.1–0.25 | Over 0.25 |
Largest Contentful Paint: how fast the main content appears
LCP is the time until the largest image, text block or video (opens in a new tab) in the visible screen has rendered. On a practice home page that's usually the hero photo, a provider photo or the main headline.
Illustrative example: A fictional orthodontic practice's home page opens with a five-image slider of smiling patients. The phone downloads several full-size photos before showing the first one, and LCP lands well past four seconds. Replacing the slider with one compressed image and a text headline brings the main content up first.
What helps, per web.dev's LCP guide (opens in a new tab): right-sized, compressed images in modern formats; no lazy-loading on the main image ("never lazy-load your LCP image"); fewer render-blocking scripts in the page header; and a fast server response.
Interaction to Next Paint: how fast the page responds
INP measures the delay between a tap, click or key press and the screen updating. It covers every interaction during the visit (opens in a new tab), not just the first. Scrolling and hovering don't count.
Illustrative example: A fictional family practice loads a chat widget, a review carousel and two ad tags as soon as the page opens. A patient taps "Request appointment" while those scripts are still running, and nothing happens for most of a second. They tap again, and the form opens twice.
The fix is usually to do less on load. A facade (opens in a new tab) shows a lightweight placeholder that loads the real chat widget only when someone taps it. Remove scripts nobody uses.
Where to see your scores: Search Console and PageSpeed Insights
Search Console's Core Web Vitals report groups similar pages and labels each group Good, Need improvement or Poor, using its slowest metric. The report (opens in a new tab) is built from Chrome UX Report (CrUX) data. Our guide to using Google Search Console shows where to find it.
PageSpeed Insights shows two kinds of results for any URL:
- Field data at the top: real visits over the previous 28 days (opens in a new tab). This is what the Core Web Vitals assessment uses.
- Lab data below: a Lighthouse test run once, in a simulated environment. Useful for diagnosing causes; it can't measure INP directly, so it shows Total Blocking Time instead. Our guide to Lighthouse scores explains how to read it.
Small practice sites often have no field data. CrUX only includes pages and sites that are "sufficiently popular" (opens in a new tab), and Google doesn't publish the threshold. When field data is missing, use lab results and your own phone. Our website grader (free tool) gives a quick check, and our free audit of your site scores website speed on phones along with five other areas.
The usual culprits on practice websites
| Culprit | Metric it hurts | What to ask your web person |
|---|---|---|
| Oversized provider and hero photos | LCP | Resize and compress; serve modern formats; don't lazy-load the top image |
| Image sliders on the home page | LCP, CLS | Replace with one static image and a clear headline |
| Chat widgets loading immediately | INP | Load on tap with a facade, or delay until the page is idle |
| Review badges and carousels | CLS, INP | Reserve fixed space; load after main content |
| Embedded maps and videos | LCP | Lazy-load anything below the fold; use a static map image with a link |
| Cookie banners inserted at the top | CLS | Use a bottom overlay that doesn't push content |
| Ad tags and unused scripts | INP | Remove what nobody uses; keep pixels off patient forms |
| Booking buttons from third-party scripts | CLS | Reserve the button's space in the layout |
If the list is long, a rebuild may beat patching. Our website redesign checklist covers how to switch without losing what works. Medfy sites are built to be fast, and that's part of the free preview you see before subscribing.
Do Core Web Vitals affect rankings?
Yes, modestly. Google's documentation says Core Web Vitals are used by its ranking systems (opens in a new tab), and that other page-experience aspects don't directly help ranking. The same page says Google "always seeks to show the most relevant content, even if the page experience is sub-par". Search Central's Core Web Vitals page (opens in a new tab) describes good scores as aligning with what its core ranking systems reward, not as a standalone factor.
In practice: a fast page about the wrong thing won't rank, and a slow page about exactly the right thing can. Speed matters most after the click. Technical basics such as structured data and clear service pages work alongside it. For the full picture, see our guide to website speed optimization.
Frequently asked questions
What are good Core Web Vitals scores?
Google's 'good' thresholds are 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. A page passes when at least 75 percent of real visits meet each one, judged separately for phones and desktops. 'Poor' starts above 4 seconds, 500 milliseconds and 0.25.
Why does my site fail Core Web Vitals on mobile but pass on desktop?
Phones have less processing power and often slower connections, so the same page takes longer to show its main image and to respond to taps. Heavy hero photos, sliders, chat widgets and third-party scripts hurt far more on a phone. Google reports the two separately, and many patients look for a practice on their phone, so fix the mobile results first.
Do Core Web Vitals matter for small websites?
The experience matters for every site, because patients on phones leave slow pages. The measurement is another matter: Google's real-visitor data only covers pages and sites with enough Chrome traffic, and the threshold isn't published. If Search Console shows no data for your site, use PageSpeed Insights lab results and your own phone to find and fix problems.
How long do Core Web Vitals take to update after a fix?
Real-visitor data in PageSpeed Insights covers the previous 28 days, so a fix shows up gradually as new visits replace old ones. In Search Console, clicking Start Tracking on a fixed issue starts a 28-day monitoring session. Lab tests in PageSpeed Insights or Lighthouse reflect a fix immediately, which makes them the quickest way to confirm the change worked.