When Core Web Vitals is worth the effort

The version of this that works is simpler than the version most people imagine. Core Web Vitals is not free, and pretending otherwise leads to bad decisions.

Performance work is mostly subtraction, which makes it unpopular and effective. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

When it is worth it

Google measures loading, interactivity, and visual stability. It is worth being explicit about, because assumptions differ quietly. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. The cost of getting this wrong is rarely visible on the day it happens.

How to decide

Field data from real visitors beats lab scores. None of that requires a large budget, only a decision and someone to own it. The version that survives contact with a real deadline is the simple one.

The short version

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

Worth checking on your own setup before it becomes someone else's problem to fix.