Core Web Vitals in 2026: The Numbers and the Real Fix Order

Vitals are pass-fail table stakes: green removes speed as an excuse, red spots competitors a head start everywhere. The fix order matters more than the tool list: measure on real mobile connections, kill the largest render-blockers first, right-size the LCP image, then chase interaction latency, because INP failures usually hide in third-party scripts nobody owns.

Crawl budget is a money metric

When bots spend their visit on parameter junk and duplicate paths, your revenue pages wait days for a recrawl. Prune, canonicalize, and block the waste; fresh content only matters if it gets fetched.

Core Web Vitals are table stakes

LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1. Miss them and you spot competitors a handicap on every query; hit them and speed disappears as an excuse.

Key takeaways

Migrations fail in the details

Redirect maps get the headlines, but schema parity, crawler access rules, and entity language drift are where visibility actually dies. Baseline everything before freeze and re-verify on launch day, not launch week.

In practice

The practical fix order matters more than the tool list, because chasing metrics in the wrong sequence wastes effort. We measure on real mobile field data rather than lab scores, kill the largest render-blocking resources first, right-size and preload the LCP image, reserve space for anything that loads late to stop layout shift, and only then chase interaction latency, which usually hides in third-party scripts nobody owns. The three thresholds, LCP under two and a half seconds, INP under two hundred milliseconds, CLS under a tenth, function as a floor rather than a nice-to-have, and there is a newer reason to care: a page that loads too slowly can be dropped during real-time AI retrieval before its content is read. Done in the right order, most sites reach green without a rebuild, which is the outcome we aim for rather than a theoretically perfect score.