Core Web Vitals: what actually moves your ranking
01Speed is a feature, not a metric
Chrome gives your pages a score for metrics it calls Core Web Vitals: how fast the biggest element paints, how quickly the page responds to input, and how stable the layout stays while loading. They matter for ranking, but treat them as detection, not the goal.
A fast page that sells nothing is still a waste. The vitals are worth chasing because they usually expose the real problems: too much JavaScript, oversized images, blocking third parties.
“You can't optimise your way into a good offer. But you can absolutely break one with a slow page.”
02Fix the cheap wins first
Three fixes cover most of the ground: serve images that match their display size and modern format, remove render-blocking scripts your users never interact with, and stop shipping a 3MB framework when a 30KB static render would do.
Then measure once daily, in the field — not in a lab. A page can score 100 in Lighthouse and still feel slow on a budget phone with slow network. Field data is the truth.
03Keep it fast after launch
Performance decays the way code does — silently. Every new dependency, banner and tracker pushes your budget over. Put a performance check into your merge pipeline and celebrate the regression test as loudly as the feature it protects.
