Core Web Vitals are the three metrics Google uses to measure a page’s user experience: LCP, INP, and CLS. All three are measured in the browser, on real users — which means a site that looks good in a lab test can perform poorly in the field.
What do the three metrics measure?
LCP — Largest Contentful Paint
How long it takes for the largest visual element on the page to be drawn on screen. This is the moment the user would say “the page has loaded.” Google’s threshold for a good score is 2.5 seconds. It’s usually dragged down by uncompressed hero images, render-blocking CSS, and slow server responses.
INP — Interaction to Next Paint
How long the interface takes to respond when the user clicks something. It replaced FID in 2024 and is a much more demanding metric. The good threshold is 200 milliseconds. The main culprit is almost always third-party JavaScript tying up the main thread: chat widgets, heatmaps, analytics tags stacked on top of each other.
CLS — Cumulative Layout Shift
How much the content shifts around while the page loads. It’s the text you’ve just started reading suddenly jumping down, or a button moving just as you’re about to click it. The good threshold is 0.1. The cause is usually images without declared dimensions, late-loading fonts, and dynamically injected banners.
Why is this a marketing issue?
Core Web Vitals are a ranking signal, but their real impact isn’t on rankings. Visitors abandon a slow page before they even see the content. If you’re buying traffic with Google Ads, that’s a loss you can measure directly in money: you pay for every click and then lose the user on the loading screen.
That’s why we treat performance as an architectural decision, not an “optimization phase.” A caching plugin bolted on afterward won’t rescue a heavy theme choice.
Where should you start?
- Open the Core Web Vitals report in Google Search Console — this is real-user data, not lab data.
- Convert your images to WebP and always set their width and height attributes. That alone fixes LCP and CLS together.
- Justify every third-party script you load, one by one. Remove anything that can’t be justified.
- Preload your fonts and choose their
font-displaybehavior deliberately. - Use server-side page caching; time to first byte sets the ceiling for everything else.
Frequently asked questions
Will my rankings drop if my Core Web Vitals scores are poor?
Don’t expect a direct, sharp drop. Core Web Vitals aren’t a signal strong enough to compete with content quality; they act as a tiebreaker between two pages of similar quality. Your real loss isn’t in rankings — it’s in holding on to the users who do reach your site.
Do I need to score 100 on PageSpeed Insights?
No. A score of 100 is a lab simulation. What matters is passing all three thresholds in the field, on your real users’ devices. The field data in Search Console is the only true measure.
When will I see the effect of my changes?
The field data in Search Console uses a rolling 28-day window, so it takes weeks for a fix to be fully reflected in the report. For instant feedback, measure in the browser.