Core Web Vitals in plain language
Google measures how a page feels to use with three numbers. Here is what each one means, the target, and what usually fixes it on a small business site.
| Measure | What it means | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long until the main content, usually the hero image or headline, appears | 2.5 s or less | Over 4 s |
| INP (Interaction to Next Paint) | How long the page takes to react after a tap or click | 200 ms or less | Over 500 ms |
| CLS (Cumulative Layout Shift) | How much things jump around while the page loads | 0.1 or less | Over 0.25 |
Google judges these at the 75th percentile of real Chrome visits over 28 days, so three out of four visits need to hit the target. See Google's own write-up at web.dev/articles/vitals.
Fixing a slow LCP
- Resize the hero image. A 4,000-pixel photo shown 1,200 pixels wide wastes most of its bytes. Export at the size it is shown, as WebP.
- Don't lazy-load the hero. Lazy-loading is for images further down. The first image should load straight away.
- Cut render-blocking files. Sliders, font loaders and unused plugin CSS often hold up the first paint.
- Turn on caching. On WordPress, a caching plugin and your host's cache usually take a second or more off.
Fixing a poor INP
- Remove scripts you don't use: old chat widgets, unused tracking tags, heavy page builders' extras.
- Load third-party scripts after the page, not before.
Fixing layout shift
- Give images and video a width and height so the browser reserves space.
- Reserve space for banners and cookie notices instead of pushing the page down when they appear.
Check your own pages
The page speed check runs Google's test and lists the fixes that save the most time.