Three myths about Core Web Vitals

This is one of those topics that looks small until it costs you something. A few things about Core Web Vitals that get repeated more often than they get checked.

Real-world numbers from actual visitors matter more than a score produced on a fast laptop. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

“It only matters for big sites”

Google measures loading, interactivity, and visual stability. Getting it slightly wrong is survivable. Ignoring it entirely is not. Budget a little time for it every quarter and it never becomes a project of its own.

“We can deal with it after launch”

Sometimes true, usually expensive. It is worth being explicit about, because assumptions differ quietly.

“Our platform handles it”

Field data from real visitors beats lab scores. It is worth being explicit about, because assumptions differ quietly. Check it against what you would want a competitor's site to get wrong.

What this looks like day to day

Speed is a feature people notice only in its absence, and then they leave rather than complain. 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 you want a second opinion on how yours is set up, ask.