Core Web Vitals Explained for Business Website Owners

Three metrics, each measuring a different way a page can feel bad. Understanding what each one is actually timing tells you what to fix.

Largest Contentful Paint — "when does it look loaded?"

LCP times how long until the largest visible element renders. Usually a hero image, sometimes a heading block.

Typical causes of a bad LCP: an oversized hero image, render-blocking CSS or fonts, slow server response, or — very commonly — lazy-loading the hero image, which delays the exact element being measured.

How to improve Largest Contentful Paint covers the fixes.

Interaction to Next Paint — "does it respond when I tap?"

INP measures the delay between an interaction and the page visibly responding. It replaced First Input Delay in 2024 and is stricter, because it looks at interactions throughout the visit rather than only the first.

Cause is almost always JavaScript occupying the main thread. How to improve INP goes into what to do about it.

Cumulative Layout Shift — "does it jump around?"

CLS measures unexpected movement of content during load. The button you were about to tap moves, and you tap something else.

Caused by images without declared dimensions, ads and embeds inserted after load, web fonts swapping at a different size, and banners injected above existing content.

How to fix Cumulative Layout Shift covers each.

Field data versus lab data — the distinction that matters

This is the single most common confusion, and it wastes a lot of effort.

Field data is what real Chrome users experienced on your site over the last 28 days, on their actual devices and connections. Lab data is a simulation run on demand.

Google ranks on field data. You can have a lab score of 98 and fail Core Web Vitals, because your real visitors are on mid-range phones on mobile networks and the lab test was not.

Where to find field data:

• Search Console → Core Web Vitals. Grouped by URL pattern, which is the most actionable view.
• PageSpeed Insights. The top section, if your site has enough traffic to report.

Sites below a traffic threshold have no field data at all. In that case lab testing is all you have — but test on a mid-range mobile profile over a throttled connection, not on a desktop.

What to actually do about it

1. Check field data in Search Console first. That tells you which metric and which page group.
2. Fix that metric on those pages. Not everything at once.
3. Re-measure after four weeks, because field data is a 28-day rolling window and moves slowly.

Chasing a perfect lab score is the classic waste of effort here. The last few points routinely cost more than they return, and they are measured in a simulation nobody experiences.

If you would rather have it diagnosed properly, that work is part of the WordPress development service for builds and the maintenance service for keeping it that way. Speeding up a slow WordPress site shows the diagnostic order.