The short answer
- The three measurements: LCP within 2.5 seconds, INP under 200 ms and CLS under 0.1. Those are Google’s own thresholds.
- INP raised the bar: not just loading fast, but staying fast to respond to every interaction.
- The largest gain almost always sits in less JavaScript, well-loaded imagery and reserved space.
- The same light build also makes your site more readable for AI crawlers. Speed is double return.
The three measurements that count
Google’s own thresholds for a good experience. Hit all three, on mobile, in the field.
Largest Contentful Paint: how fast the largest element is on screen. Feels like: the page is here.
Interaction to Next Paint: how fast the page responds to every click or tap. Feels like: it is listening.
Cumulative Layout Shift: how much the page jumps while loading. Feels like: it stays still where you click.
What the three measurements really say
LCP measures whether the page is there fast, INP whether it keeps responding to every tap, and CLS whether it stays still while you click. Together they form the measurable part of what visitors call trust.
INP is the strictest of the three, because it measures the whole session: that filter button halfway too, and that menu at the bottom. A site that opens fast but responds slowly goes through the ice here.
Measure in the field, not only in the lab. Google judges on real visitor data, and your test computer on fibre is not your customer on a phone on the train.
Visitors measure nothing. They feel everything. The Vitals put that feeling into numbers.
Where the gain sits
Almost always in the same three places. One: JavaScript. Every kilobyte of script has to be loaded, parsed and executed, and that last part blocks the response time. Cutting wins more here than optimising.
Two: imagery. The largest element on your page is usually an image; give it the right size, a modern file type and priority on loading. Three: calm. Reserve space for everything that loads later, so the page does not jump under your visitor’s finger.
Our own site is the proof: built static, per page only the style and script that page needs. Speed is not an afterburner but a build choice, from the first line.
Speed as a findability strategy
The Vitals weigh in your ranking, but the story has grown larger. AI crawlers prefer light, server-rendered pages; what is slow and script-heavy gets read half or not at all, and what is not read never gets cited.
Speed also touches your revenue side directly: every second of waiting costs attention, and attention is the first step of every request.
So treat the thresholds not as an exam but as a floor. Whoever sits well below them has room for the busy days, the slower phones and the campaign spikes that come one day.
Frequently asked questions
Where do I see my own Core Web Vitals?
In Google Search Console under page experience, measured on real visitors. For a snapshot per page PageSpeed Insights works; the field report is leading.
My score varies per measurement. Is that normal?
Lab measurements fluctuate with network and device; that is why the field average over real visitors counts. Steer on the trend, not on one measurement.
Can a slow site become fast without a rebuild?
Often considerably: imagery, load order and superfluous script deliver the first gain. If the slowness sits in the foundation, we say so honestly, with the sum attached.
Does your site hit the thresholds?
Request the speed check. You get your field score per measurement, the cause and the shortest route to green.