Core Web Vitals: what to get right first

It comes up on almost every project, usually later than it should. If you only fix one thing about Core Web Vitals this quarter, make it the first item below.

Performance work is mostly subtraction, which makes it unpopular and effective. The version that survives contact with a real deadline is the simple one.

Start here

Google measures loading, interactivity, and visual stability. Where this goes wrong is almost never a lack of knowledge. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

Then this

Largest contentful paint under 2.5 seconds is the bar. None of that requires a large budget, only a decision and someone to own it. If two people in the business would answer this differently, that gap is the actual problem.

Eventually

Field data from real visitors beats lab scores. That sounds obvious written down. It is still the thing most often skipped. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

How to tell if yours is fine

Real-world numbers from actual visitors matter more than a score produced on a fast laptop. Three things worth confirming about Core Web Vitals before you move on:

• Someone can say what the current setup is without going to look
• Field data from real visitors beats lab scores — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If any of that sounds like a description of your current setup, it is fixable.