This guide explains each metric, what causes poor scores, and how to check your own site.
A Quick Definition
Core Web Vitals are a small set of measurements that Google uses to describe the real-world experience of loading and using a web page. They are part of what Google calls page experience signals, which it considers alongside many other factors, most importantly the relevance and quality of your content.
There are currently three Core Web Vitals:
| Metric | What it measures | "Good" threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading: how quickly the main content appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | Responsiveness: how quickly the page reacts to taps, clicks, and key presses | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability: how much content moves around unexpectedly | 0.1 or less |
Google evaluates these at the 75th percentile of visits. In plain terms, a page passes when at least three out of four visits meet the target. So your score reflects visitors on older phones and slower connections, not just the fast laptop in your office.
INP replaced an older metric, First Input Delay, in March 2024. If you see FID in an older report, know that it is no longer part of the set.
Largest Contentful Paint: "Is It Here Yet?"
LCP marks the moment the largest visible element, usually a hero image, a video poster, or a large block of headline text, finishes rendering. It is a good stand-in for when a visitor feels the page has arrived.
Common causes of a slow LCP include:
- Large, uncompressed hero images, especially photos uploaded straight from a camera
- Slow server response times, often from underpowered hosting or no caching
- Render-blocking CSS and JavaScript that must download before anything appears
- Web fonts that delay text from showing
- Main images loaded late because they are inserted by JavaScript or marked for lazy loading
Fixes usually start with the image itself: resize it to its displayed dimensions, convert it to a modern format such as WebP or AVIF, and tell the browser to prioritize it. Then look at hosting, caching, and a content delivery network (CDN).
Interaction to Next Paint: "Did It Hear Me?"
INP looks at the interactions a visitor makes during their time on a page and reports one of the slowest. If someone taps "Add to cart" and nothing visibly happens for half a second, they may tap again, give up, or lose trust.
Poor INP is almost always about JavaScript. When the browser's main thread is busy running scripts, it cannot respond to the visitor. Typical culprits are:
- Too many third-party scripts, such as chat widgets, ad tags, heatmaps, and social embeds
- Large JavaScript bundles from themes or page builders that load features you never use
- Heavy work triggered by a single click, such as re-rendering a whole page to update one number
Improving INP often means auditing scripts and asking of each one: is this earning its place? Removing or delaying non-essential tools and breaking long tasks into smaller pieces can make a site feel noticeably more responsive.
Cumulative Layout Shift: "Why Did That Move?"
You have probably tried to tap a link just as a banner loaded above it and pushed it away. CLS measures that kind of unexpected movement.
The usual causes are straightforward:
- Images and videos without set width and height, so the browser does not know how much space to reserve
- Ads, embeds, or cookie banners injected above existing content
- Web fonts that swap in and change the size of text after it first appears
- Content added dynamically, such as a "free shipping" bar that appears a moment after load
The fix is to reserve space in advance: give media explicit dimensions, place banners in fixed slots, and choose font settings that minimize reflow. CLS is often the easiest of the three to improve.
How to Check Your Own Scores
You do not need special software to get started. Two free tools from Google will tell you most of what you need to know.
- PageSpeed Insights (pagespeed.web.dev): Enter any URL to see field data from real Chrome users, when enough data exists, plus lab data from a simulated test with specific recommendations.
- Google Search Console: The Core Web Vitals report groups your pages into "Good," "Needs improvement," and "Poor," separately for mobile and desktop. It is the best way to see patterns across a whole site.
It helps to understand the difference between the two types of data. Field data comes from real visitors over the previous 28 days, so improvements take time to show up. Lab data comes from a single controlled test, which is useful for diagnosing problems and checking fixes immediately, but may not match what real visitors experience.
Where to Focus First
If your results show problems, resist the urge to chase a perfect score on every page. Instead:
- Start with your most important templates. Homepage, service pages, product pages, and contact page usually matter most.
- Fix by template, not by page. On most sites, pages share layouts, so one fix to a template can improve hundreds of URLs.
- Prioritize mobile. Mobile scores tend to be worse and mobile visitors are often your largest group.
- Measure before and after. Record your baseline so you can confirm each change actually helped.
- Watch for regressions. New plugins, tracking tags, and large images added later are the most common reasons good scores slip.
Remember that Core Web Vitals are a means to an end. The goal is not a green number in a report; it is a website that feels fast, responsive, and dependable to the people who use it.
Want a clear picture of your website's performance? Tenshi Systems Engineering offers speed and Core Web Vitals optimization for businesses everywhere. Request a consultation and we will review your results, explain what they mean, and outline a practical plan to improve them.