Refract Group2026
Glossary
Core Web Vitals
Core Web Vitals are Google’s three measures of how a page feels to use, taken from real visits: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness and Cumulative Layout Shift for visual stability.
- LCP: main content shown2.5 s or less
- INP: reply to a tap200 ms or less
- CLS: layout movement0.1 or less
Core Web Vitals in detail
- Also called
- CWV, Web Vitals, LCP, INP and CLS
- Topic
- Website
- Updated
What it is
Each metric times something a visitor notices. LCP is how long the largest image or block of text in the first view takes to appear. INP watches the clicks, taps and key presses during a visit and reports one of the slowest, measured until the screen changes in reply. CLS adds up how far things jump while the page is open. INP replaced First Input Delay, which timed only the first interaction, on 12 March 2024.
Google judges a page at the 75th percentile of real visits, with phones and desktops counted apart, so three visits in four have to meet the threshold. Good is an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less. The figures come from real Chrome visits, so a new site with little traffic may have none yet.
Why it matters
Google says good Core Web Vitals align with what its core ranking systems reward. The larger cost is on the page itself. A heading that appears after five seconds on a phone, or a form that jumps as an image loads above it, loses some of the people who came. The thresholds are a floor for the pages buyers land on, and they should be checked on a phone.
How we do it
We measured our own site in November 2026. Lab runs on the live site, simulating a slow phone, put the largest element at 6.3 seconds on the home page and 5.6 to 6.1 on a service page, against 1.1 on a case study. In each slow case it was hero text, in the HTML from the first paint and held back by the entrance animation.
On 14 November the entrance moved to a CSS clock that starts at first paint. On a throttled phone the first text went from about 4.6 seconds to between 2.4 and 2.7, and it now shows with JavaScript off. Lighthouse’s default figure did not move, because it times a fast load in which the entrance still plays. We have no figures from real visits yet.
An example
Say a landing page’s hero image weighs 1.8 MB and starts loading only after the stylesheet and two scripts. Field data puts its LCP at 4.3 seconds on phones, which is poor. Serving the image at the size it is shown, in a modern format, and telling the browser to fetch it first brings LCP to 2.3 seconds. A cookie banner that pushes the page down as it arrives still adds 0.15 of layout shift, until it is given a reserved space.
Common mistakes
- Reading a Lighthouse score as the vitals. Lighthouse times one simulated load, leaves INP out of its score, and Google judges a page on what real visitors experienced.
- Measuring only the homepage. A fast homepage says nothing about the pricing or service page a buyer reaches from search, so measure the templates people arrive on.
- Hiding text behind an entrance. Text that is in the HTML but faded in by a script still counts as late for LCP, as our own home page showed.
- Leaving space unreserved. Images, embeds and banners without set dimensions push content down as they arrive, and that movement is what CLS counts.
Core Web Vitals vs a Lighthouse score
Core Web Vitals are three measures taken from real visits, while a Lighthouse score is a grade out of 100 from one simulated load, weighted across five lab metrics.
| Core Web Vitals | A Lighthouse score | |
|---|---|---|
| Data | Real visits, in Chrome | One simulated page load |
| Metrics | LCP, INP and CLS | TBT, LCP, CLS, FCP and Speed Index |
| Responsiveness | INP, from real interactions | Total Blocking Time as a stand-in |
| Between checks | Moves as visits accumulate | Can change from run to run |
Questions
What people ask about core Web Vitals.
Google’s good thresholds for Core Web Vitals are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less, met by at least 75 per cent of visits, with phones and desktops counted apart. Poor begins above 4 seconds for LCP, 500 milliseconds for INP and 0.25 for CLS.
Google says good Core Web Vitals align with what its core ranking systems seek to reward, and recommends that site owners achieve them. They are part of how Google weighs page experience. Speed does not make a page relevant, though: a fast page still has to answer the search to rank for it.
Interaction to Next Paint, or INP, replaced First Input Delay in the Core Web Vitals on 12 March 2024. FID timed only the delay before the first interaction was handled. INP looks at clicks, taps and key presses across the whole visit and how long the screen takes to change after each, with good at 200 milliseconds or less.
Where this shows up in our work
Related terms
Working on this now?
Tell us what you’re building and where it’s stuck. We reply within 12 hours.
Most teams start with a call, then a sprint or an audit.
The people you’d work with, from the first call to launch