Core Web Vitals in Plain English

Core Web Vitals are three measurements of how a page feels to a real visitor: how fast the main content appears, how quickly the page reacts when someone taps, and whether things jump around while it loads. Google says its ranking systems use them, and also says it will show the most relevant content even when page experience is weak, and that good scores do not guarantee a top position. Treat them as a way to find real annoyances, not a score to chase. Start by looking at your real numbers, then fix the biggest cause on your slowest page.

The three measurements

These thresholds come from Google's web.dev documentation and the Search Console help. INP replaced the older First Input Delay measure as the responsiveness metric. "75th percentile" means three out of four visits had that experience or better, which keeps the number honest about slower phones and connections.

Look at real data first

Two kinds of numbers exist, and they answer different questions.

• Field data comes from real Chrome users over about the last 28 days. It is what Google's Core Web Vitals report in Search Console uses, and it is what shows at the top of PageSpeed Insights when your site has enough traffic.
• Lab data is a simulated test on one device at one moment (Lighthouse). It is useful for debugging and varies from run to run. A 95 lab score does not guarantee good field results.

A small site with little traffic may have no field data at all. In that case Search Console shows nothing for the page, and PageSpeed Insights may fall back to whole-site numbers or show only lab results. Then use the lab test for guidance and keep your expectations modest.

In Search Console, open Core Web Vitals. Mobile and desktop are separate reports, and a group of pages takes the status of its worst metric. Find the groups marked Poor or Needs improvement and look at the example URLs.

Fix LCP first: the top of the page

Google's guidance splits LCP into four parts: the time to receive the first byte of HTML, the delay before the main image starts loading, the time to download it, and the delay before it paints. For most small business sites the culprit is the hero image.

1. 1Find the LCP element. PageSpeed Insights names it. It is usually the hero photo or a big heading.
2. 2Do not lazy-load it. web.dev is explicit: never lazy-load your LCP image, because it adds delay.
3. 3Give it priority. Marking the one important image with fetchpriority high helps. Do it for one or two images only, or the hint stops being useful.
4. 4Resize and compress it. A 4,000 pixel wide photograph served to a phone is a common cause. Use a modern format and a size that matches the display.
5. 5Reduce redirects. Visitors who land through several redirects start slower. Link directly to the final address.
6. 6Check hosting response time. A very slow server makes a good LCP hard to reach, however well the page is built.

Fix CLS next: stop the jumping

Layout shift is the easiest to find and fix.

• Add width and height (or an aspect ratio) to every image and video so space is reserved.
• Reserve space for embeds, maps, ads and cookie banners that load late.
• Avoid inserting banners above content that is already visible.
• Load web fonts sensibly and pick a fallback font close in size, which web.dev recommends.

Then INP: make taps respond

Poor INP usually means the browser's main thread is busy with scripts when someone tries to use the page. Typical causes on small business sites:

• Chat widgets, popups, review badges and tracking tags from many providers.
• Heavy sliders, animation libraries and autoplay video backgrounds.
• A large page with thousands of elements.

The first fix is to remove what you do not need. Open your tag manager and delete tags nobody can explain. Then delay what remains until after the page is usable. If a menu button takes half a second to open, a script is the cause, not your phone.

What not to do

• Do not buy a speed plugin as the first move. Cleaning images and removing scripts does more.
• Do not chase a perfect Lighthouse number. Fix the pages that real visitors use.
• Do not test only on your office Wi-Fi. Check on a mid-range phone on mobile data.
• Do not compress images so far that product or portfolio photos look soft. Quality is why people are on your site.

What platform you are on changes your options

On Squarespace, Wix and Shopify, you control images, apps and embeds but not the platform's own code. On WordPress, plugins and themes are often the cause and can be removed. On a custom build, you control everything and the result is only as good as the plan. See Squarespace or custom for that tradeoff and the redesign checklist if speed is part of a rebuild.

Want a person to look at it?

Our team checks speed as part of every build, and we can look at an existing site and tell you what to fix first. Start with the website check or start a quote if you want a person to take it from there.