Core Web Vitals in 2026: INP, LCP and field measurement
INP is now the reference responsiveness metric, and since late 2025 every major browser can measure it. In 2026, tracking real performance has never been more reliable.
A foundation that's finally stable
Core Web Vitals measure the real experience: loading (LCP), responsiveness (INP) and visual stability (CLS). Since March 2024, INP has replaced the old FID as the responsiveness metric — a major change, because it captures all interaction latency, not just the first delay.
What changed more recently is subtle but important for anyone measuring seriously: with Safari 26.2 (December 12, 2025), LCP and INP became "Baseline Newly available" — in other words, the latest version of every major browser finally ships the APIs needed to measure them. In 2026, you can therefore track these metrics across your entire audience, not just on Chrome.
The targets to aim for
Nothing wild, but you have to hit them:
- LCP — the main element visible in under 2.5s.
- INP — a visible reaction to a click in under 200ms.
- CLS — less than 0.1 of layout shift.
The real lesson: measure in the field
The lesson of 2026 isn't a new threshold, it's a method. A lab score (Lighthouse) isn't enough: it reflects a powerful machine and a perfect connection. What counts is field data — real users, via the Chrome UX Report and now-universal APIs. And Google increasingly aggregates these signals at the site level, not just page by page: a handful of slow pages can weigh on the whole.
What I do on my projects
- I measure continuously (Speed Insights, CrUX) rather than once before delivery.
- I treat INP as a real subject: split up the JavaScript, lighten event handlers, avoid the long tasks that block the main thread.
- I reserve space for images and fonts to hold the CLS.
In 2026, the question is no longer "what's the lab score?" but "what do my real visitors experience, on their real phone?". That's the only measure that counts.