2026-06-30 — 6 min read
Three numbers decide whether Google thinks your site feels fast. Here’s what they mean in plain language, and which fixes are worth paying for.
Your developer mentions Core Web Vitals, your rankings are flat, and you’re being asked to fund work you can’t see. This is what you’re buying.
How long until the biggest thing on screen shows up. Usually a hero image or headline. This is the closest thing to "does the page feel fast," and it’s the one most often broken by a single oversized image.
When someone taps a button, how long before the page visibly responds. This replaced First Input Delay in 2024 and is stricter, because it measures every interaction rather than just the first.
How much the page jumps around while loading. If you’ve ever gone to tap a link and hit an ad because the page moved, that’s CLS. It’s the cheapest of the three to fix and the most irritating to users.
Less than SEO vendors imply, and more than nothing. Google has been explicit that these are a tiebreaker: they won’t lift a weak page above a better one, but between two comparable results, the faster one wins.
The stronger argument is commercial rather than algorithmic. Slow pages lose people before they ever see your offer, and that shows up in conversion rate regardless of where you rank.
In our experience the order of impact per dollar is remarkably consistent:
Notice that four of the five are about images and third-party code. Framework changes and rewrites, the expensive options, are rarely where the wins are.
Use PageSpeed Insights for a single page and Search Console’s Core Web Vitals report for the whole site. The distinction matters: PageSpeed runs a lab test on demand, while Search Console reports field data from real visitors. Field data is what Google uses, and it’s the one to trust when they disagree.
Most business sites can move from failing to passing in a few days of focused work, most of it on images. If someone quotes you a rebuild to fix Core Web Vitals, get a second opinion before you sign.