Google measures how your website feels to real visitors with three numbers called Core Web Vitals. They sound technical, but each one answers a simple question your customers ask without realizing it: did the page show up quickly, did it respond when I tapped, and did it stay still while I was reading?
This guide explains what each metric means, how to check your own site in a few minutes, and what usually fixes a poor score.
Why these three numbers matter
Core Web Vitals are part of how Google thinks about page experience. They are not the only thing that decides rankings, and a perfect score will not rescue a page with thin content. But they are a fair stand-in for frustration. A slow, jumpy page loses people before they ever read your offer.
Google recommends judging each metric at the 75th percentile of real page visits, measured separately on mobile and desktop. In plain terms, at least three out of four visits should hit the good mark. Your fastest visitors on office Wi-Fi are not the ones to worry about. The customer on a phone in a parking lot is.
LCP, INP and CLS in plain language
- Largest Contentful Paint (LCP) measures loading. It records when the biggest thing in view, usually a hero image or main heading, finishes appearing. Google's good threshold is 2.5 seconds or less.
- Interaction to Next Paint (INP) measures responsiveness. When someone taps a button, opens a menu or types in a form, how long until the screen visibly reacts? Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS) measures visual stability. It scores how much content jumps around while the page loads. Good is 0.1 or less.
If you read older articles, you may see First Input Delay (FID). INP replaced FID as a Core Web Vital in March 2024 because it looks at every interaction during a visit, not just the first one.
How to check your own site
You do not need a developer to get a first read. Three free Google tools cover most needs.
- PageSpeed Insights (pagespeed.web.dev): paste a URL and you get two views. The top section shows field data from real Chrome users, if your site has enough traffic. The lower section is a lab test, a simulated page load that is useful for diagnosing problems.
- Google Search Console: the Core Web Vitals report groups your URLs into good, needs improvement and poor, based on real visits. It is the best place to spot patterns across the whole site.
- Chrome DevTools and Lighthouse: built into the Chrome browser, these are what a developer will use to trace the cause of a specific issue.
Field data beats lab data
Lab scores shift every time you run a test and depend on a simulated device. Field data reflects what your real visitors experienced over recent weeks. If the two disagree, trust the field data and use the lab test to work out why.
A small business site may not have enough traffic for field data to appear. In that case the lab test is still a helpful guide. Just treat the score as directional rather than final.
What usually fixes slow loading
Poor LCP almost always comes down to a heavy main image, a slow server or too much waiting before the page can draw anything.
- Resize and compress the hero image, and serve a modern format like WebP or AVIF. A photo straight from a camera is often far larger than it needs to be.
- Do not lazy-load the main image at the top of the page. Lazy loading is great for images further down, but it delays the one image that matters most.
- Cut back render-blocking scripts and stylesheets, especially chat tools, widgets and tracking tags that load before your content.
- Use decent hosting and a content delivery network (CDN) so the first response arrives quickly, wherever your visitor is.
What usually fixes sluggish taps and jumping pages
INP problems usually mean the browser is busy running JavaScript when someone tries to interact. Common culprits are page builders that ship a lot of code, stacks of marketing scripts, and heavy sliders or pop-ups. The fix is often subtraction: remove plugins and tags you no longer use, delay non-essential scripts until the page is usable, and break up long-running tasks in custom code.
CLS is usually the easiest of the three to fix. Content jumps when the browser does not know how much space something needs until it arrives.
- Set width and height, or an aspect ratio, on images and videos so space is reserved before they load.
- Reserve space for ads, embeds and cookie banners instead of letting them push content down.
- Load web fonts carefully so text does not reflow when the custom font swaps in.
Our recommendation
Run your homepage and your most important service page through PageSpeed Insights this week, on mobile. If all three metrics are green, move on and spend your energy on content. If one is red, read the specific suggestions the tool gives before you consider a rebuild. Many problems are solved by compressing images, trimming scripts and setting image dimensions.
If the issues trace back to your theme, page builder or hosting, that is when a developer earns their fee. Ask them to show you field data from before and after the work, not just a lab score, so you know the change helped real visitors.
Written by Vishal Singh
Founder of Byte Harbor and a senior frontend and web platform engineer. He builds websites, custom software and AI automation for businesses across Canada and the US.
About Byte HarborRelated service
Website development for Canadian businesses
A fast, responsive site that explains what you do, is easy for your team to update, and makes contacting you simple.
Explore Website Development
