Core Web Vitals in plain English
Three measurements of how a page feels to use, and a realistic view of how much they change your rankings.
Core Web Vitals are three measurements of how a page feels to use: how long before the main thing appears, how quickly the page responds when you tap, and how much content jumps while loading. They are a tiebreaker for rankings rather than a driver, and the place they change your numbers most is conversion.
- Three measurements of how a page feels: load, response, and layout stability.
- They are a tiebreaker for rankings and a real factor in conversion.
- Usual causes: uncompressed hero images, third-party scripts, late fonts.
- Field data lags, so chasing the score weekly wastes attention.
What do the three Core Web Vitals actually measure?
The three Core Web Vitals are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. One measures loading, one measures response, and one measures layout stability. The table below gives each one in plain English, and what a visitor notices when it goes wrong.
| Metric | What it measures | Why it matters to a visitor |
|---|---|---|
| Largest Contentful Paint | How long before the main thing appears. | A visitor's read on whether the site is working. |
| Interaction to Next Paint | How quickly the page responds when you tap. | Slow here feels broken even when it is loading. |
| Cumulative Layout Shift | How much content jumps while loading. | The reason you tap the wrong button. |
How much do Core Web Vitals move rankings?
Core Web Vitals move rankings less than the amount of writing about them suggests. They are a tiebreaker rather than a driver, and a fast page with weak content still loses to a slow page that answers the question. Where they matter is conversion.
A quote form that takes eight seconds to become usable on a phone on mobile data loses people who were ready to call.
What usually causes a Core Web Vitals failure?
Four things cause most Core Web Vitals failures: an image, a script, a font and a layout gap. Uncompressed hero images. Third-party scripts, especially chat widgets and tag managers carrying tags nobody has audited in two years. Fonts loading late. Ads or embeds reserving no space.
In most trade sites we look at, removing two scripts and compressing the hero image does most of the available work.
Why does the score take weeks to move after you fix something?
A Core Web Vitals score does not move on the day you fix the cause. Field data lags. You change something today and the reported score moves over the following weeks, because it is measured from real visits rather than a lab run.
That delay is why chasing the number weekly wastes attention. Fix the causes, then look again next month.
“A quote form that takes eight seconds to become usable on a phone loses people who were ready to call.”
Rankings are never guaranteed. Anything we could not trace to a primary source is absent from this page, not estimated. The audit runs the same six layers described on the pricing page, and Share of Answer is scored quarterly.
Youssef measures visibility for established local businesses across Google Maps, organic search and AI answers, quarterly, against a protocol published in advance. Numbers that cannot be checked stay out of the report.
More about Youssef