Core Web Vitals: All About the Most Important Web Speed Metrics
Core Web Vitals is a fundamental set of metrics from Google designed to reflect website loading speed and user experience.
Let’s uncover which metrics it includes, why they are important, and how to measure them. Core Web Vitals represent the bare minimum you should understand about the speed of your websites.
Metrics of the Core Web Vitals Set
Core Web Vitals (CWV) consist of three perspectives on web speed – loading speed, interaction speed, and visual stability.
- Loading Speed (LCP) measures the time taken to load the largest visible element on the page. It answers the question, “How quickly does it load?” The threshold to meet is 2.5 seconds.
- Interaction Speed (INP) measures the time from an interaction to the rendering of the next frame for all interactions on the page. It answers the question, “How quickly does it respond?” A good response to new rendering is 200 ms.
- Visual Stability (CLS) examines the visual stability of the page during loading and browsing. It answers the question, “How much does the page jump?” Google considers a CLS score under 0.1 satisfactory.
A concise overview in a table:
| Metric | 🟢 Good | 🟠 Needs Improvement | 🔴 Poor |
|---|---|---|---|
| Loading Speed Largest Contentful Paint (LCP) | ≤ 2.5 s | 2.5 – 4 s | > 4 s |
| Interaction Speed Interaction to Next Paint (INP) | ≤ 200 ms | 200 – 500 ms | > 500 ms |
| Visual Stability Cumulative Layout Shift (CLS) | < 0.1 | 0.1 – 0.25 | > 0.25 |
How and Why Were Core Web Vitals Developed?
Google introduced the Web Vitals initiative in May 2020. The goal was to consolidate web speed into a small set of numbers that correspond to what users truly experience on a page, not just what a one-off lab test might suggest. Initially, the trio of Core Web Vitals included loading speed (LCP), visual stability (CLS), and interactivity measured by First Input Delay (FID).
Google based the selection of metrics on data from the Chrome UX Report and human interaction research, summarized in the article The Science Behind Web Vitals. Since June 2021, Core Web Vitals have influenced search rankings as part of the Page Experience signal. For website owners, this means speed is not just a technical optimization for developers but a component of visibility on Google.
Behind the initiative is Google's interest in not directing people from its ecosystem – from search, ads, or Chrome links – to slow or poorly usable pages. Rather, it wants to prioritize websites with a good user experience (UX). Core Web Vitals therefore monitor a fundamental part of UX, especially important for visitors coming from Google's ecosystem.
Another advantage of Core Web Vitals is their authoritative nature. They provide a common language between website owners, developers, and marketing teams. You know what to ask for in reports and can track the same numbers.
What Do “Good” Core Web Vitals Mean?
Google considers a website as "meeting CWV" when all three metrics are in the green band at the 75th percentile of data from the Chrome UX Report over the past 28 days, separately for mobile and desktop.
Google wants three-quarters of your users to see the site in the green metrics band on both device types.
This is a reasonable technical goal. However, it is not the definition of a "fast website". Google set thresholds to be achievable for decently made websites, not to represent top speed.
If you need to see not just the 75th percentile but the shape of user value distribution, use the histogram in the Chrome UX Report.
At PageSpeed.ONE, we say that fulfilling Core Web Vitals is the minimum from which to springboard further speed improvements.
For business decision-making (conversions, retention, cart abandonment), you need not only to meet the LCP, INP, and CLS thresholds but also our business analysis.
Can This Be Expressed as a Single Number?
It can – but be cautious about which number you choose. To know the state of your website among real users, you need to monitor the three Core Web Vitals metrics separately for mobile and desktop. That’s six values per domain, which can multiply across multiple domains.
A website owner, marketer, or project manager might not easily deduce success from these numbers. It’s tempting, then, to resort to a single synthetic score from Lighthouse – but that doesn’t relate to CrUX data and is misleading for making decisions about web speed.
At PageSpeed.ONE, we developed the PageSpeed.ONE Score (SPS). Born from consultancy practice: we first show clients CrUX and CWV in monitoring, but for a quick summary, domain comparison, or management reports, we need a single value derived from the same source – from Google users, not from a lab test.
Speed Score (SPS): unify six Core Web Vitals numbers per domain into one summary from CrUX data.
SPS unifies LCP, INP, and CLS for mobile and desktop into a single percentage. It considers the entire user distribution, not just the 75th percentile, and weighs metrics according to how they impact business and real traffic. It doesn’t replace CWV in optimization but gives you a quick overview of how you’re doing overall. Detailed calculation and interpretation can be found in the article on PageSpeed.ONE Score (SPS).
How to Measure Core Web Vitals from Users?
We must recognize that Core Web Vitals metrics represent data collected from real Google Chrome users in the Chrome UX Report dataset. However, you can also access this data through Google's API, and various providers offer it as well.
In practice, for a one-time state check, we recommend heading to the PageSpeed.ONE web speed test (Insights) as your first choice:
Measure your website speed
Enter a URL and see where you stand.
Another option is PageSpeed Insights from Google for a quick one-time check of another domain. However, this tool doesn’t show changes over time – you’ll get that from another Google tool, CrUX Vis.
Google Search Console as an Important Supplement
An essential tool is also Google Search Console for a summary of data by URL groups.
Be cautious with data interpretation! At PageSpeed.ONE, we often explain to clients the unintuitive reports showing URL counts in colour bands, not direct metric values.
Moving pages from orange to green might simply mean improving LCP from 2.51 s to 2.49 s, where the colour shifts, but the actual speed hardly changes. Search Console counts the number of URLs in each band. A shift of just a few URLs across a boundary threshold (e.g., LCP from 2.51 s to 2.49 s) can bump the domain from orange to green, even if the average metric value remains nearly the same.
Report in Google Search Console shows how many URLs fall into the “needs improvement” band, not the average value for the domain.
For a detailed breakdown of data collection, rules, and limitations, see the separate page on the Chrome UX Report. How to read speed step-by-step in Search Console is covered in the guide Google Search Console and Core Web Vitals.
How to Test Core Web Vitals in Synthetics?
Chrome UX Report tells you how your site performed for real users over the past 28 days. For checking a specific page, regression after deployment, or testing a page without Google user data, you need another source – synthetic (“lab”) measurements under controlled conditions.
For synthetic CWV testing, tools like Lighthouse are available, also included in the PageSpeed.ONE monitoring tool or our web speed test tool.
PageSpeed.ONE Monitoring also offers a Watchdog feature, which monitors potential speed degradation.
However, synthetics only tell part of the story, beware.
Meeting Core Web Vitals: User Data vs. Synthetic
When we say “a site meets CWV”, we mean user data, not synthetic data. Specifically: data from the Chrome UX Report over the last 28 days, 75th percentile, all three metrics in the green band, separately for mobile and desktop.
Lighthouse’s synthetic score won’t tell you this; it shows a standalone snapshot result and tends to be unnecessarily strict for CWV.
Reasons why synthetic doesn’t quite capture reality:
- INP isn’t captured by synth
Lab tests lack any user clicks, so INP is unavailable for “meeting CWV” in synthetic measurements. - CLS only for the first load
Real shifts after interaction (sorting products, opening a filter) usually don’t appear in lab measurements; they are collected throughout the page’s open time in CrUX. - One device at one moment
Synth measures a defined network and CPU profile. CrUX is a distribution of real people on different devices; aggregation “softens” against isolated spikes.
If you celebrate green status on lab measurements but CrUX remains orange, it doesn’t indicate tool errors. Synth measures a page’s technical potential; CrUX measures user reality. Optimize so that Core Web Vitals user data is in order.
For a complete picture, always combine synth and CrUX, possibly supplement with RUM. Differences are detailed in the article synth vs. CrUX vs. RUM.
The Significance of Core Web Vitals Metrics and Their Business Impact
Pages that meet these metrics typically offer a better user experience, which can lead to higher conversions, better search rankings, and cheaper PPC ads.
Google also didn’t choose metrics and limit values randomly but based on long-term work and analysis of numerous studies in human-computer interaction. For these reasons, we regard CWV as crucial limits for web speed optimization.
Beware, though, not all three metrics carry the same business weight. From our consultancy practice, we observe that LCP or INP can significantly shift an e-commerce conversion rate more than CLS.
In this sense, CLS is often the least business-oriented, and its impact is often overshadowed by page appearance in search results, brand campaigns, or navigation.
Meeting the thresholds is a starting line; for prioritizing optimizations, we recommend adding our business analysis (conversion flows, RUM, A/B tests).
The Impact of Core Web Vitals on SEO is Quite Evident
From long-term consultancy practice at PageSpeed.ONE, we see the most pronounced impact of Core Web Vitals on SEO in two types of projects: e-commerce sites and content websites.
The balanced technical level of competition also influences this. Where competitors haven’t kept an eye on speed, a well-made site can gain additional positions. Where everyone has, poor metrics deepen the disadvantage.
A concrete example from e-commerce:
After addressing slow INP, we saw gradual position improvement. In a modelled comparison, an additional 17.3% sessions from Google.
For Denatura, a natural cosmetics e-shop we monitor long-term, we combined CWV optimization with ongoing analysis in Google Search Console and an internal deployment log.
After optimizing the INP metric on the product detail page (particularly third-party code unnecessarily blocking the main thread), we saw stabilization of positions and gradual user speed improvement. This roughly corresponds to what we see elsewhere: the effect doesn’t immediately manifest as a traffic surge but gradually through positions and impressions on long-tail queries targeted by problematic pages.
From another anonymized PageSpeed.ONE e-commerce case study, after fixing INP in February 2026, there was almost immediate stabilization of average position (from ~5.2 to ~4.3) and cessation of large search oscillations. Impressions and clicks didn’t shoot up immediately; the influence went through improving the quality of long-tail queries. This aligns with historical experience from September 2025, where the conjunction of “green” CWV with a Google Core Update created growth that mere technique likely wouldn’t have triggered. Conversely, poor CWV acts as a handbrake. A site may grow in season due to marketing, but the technique constantly holds it back.
Do Core Web Vitals Still Make Sense?
Yes, for multiple reasons simultaneously. Core Web Vitals remain the minimum a website owner should understand, and from our consultancy practice, we see three recurring arguments:
- Impact on SEO and PPC
Core Web Vitals metrics remain a signal for search and factor into Google Ads quality score. Poor status regularly impacts accounts and CPC. - Basic UX and Conversion Benchmark
The three metrics describe three real experience dimensions to which human psychology responds: how quickly it appears, how quickly it reacts, how much it jumps. These three questions are in your visitor's mind, whether you like it or not. - Proxy Metrics for Other Technical Indicators
During a Core Update, many things shift simultaneously. From observing numerous projects, we see that websites in good technical condition tend to have fewer drops or even gains during updates. Loading speed (LCP) also acts as a proxy for backend speed (TTFB), which can positively affect Google's crawl budget and availability for AI bots (we address AI bots Strategy).
What don’t Core Web Vitals metrics do? They don’t tell you if your site is fast for business. For that, you need other numbers, typically business analysis on your own conversion flows, or RUM data collection. Taking CWV as the sole measure would be the same mistake as taking the Lighthouse score as the web speed.
How to Improve Core Web Vitals
Optimizing each metric has its own rules and dedicated article. Here’s a brief guide combined with experience from our own projects:
- Loading Speed (LCP) Optimization:
There’s a lot to it. From backend improvements (TTFB), critical path optimization (CSS, fonts), correct formats and image sizes,fetchpriorityandpreloadfor LCP element, lazy loading outside the viewport. Detailed steps in LCP optimization. - Interaction Speed (INP) Optimization:
Split long tasks (setTimeout,scheduler.yield()), defer non-critical JS post-interaction, limit third-party code in critical moments, provide immediate visual feedback to users. A long-term approach on a real application is described in the Innogy case study (INP improvement by 38%). Recipe in INP optimization. - Visual Stability (CLS) Optimization:
Address image and iframe dimensions (CLS dimensions), proper font space settings, asynchronous banners with fixed reserves, beware of shifts post-click. Comprehensive view in CLS optimization.
From PageSpeed.ONE’s consultancy practice, we add a few advanced notes:
- Cloudflare
For many websites, we recommend considering CDN installation – if correctly set (Cloudflare setup), it can aid all Core Web Vitals metrics. - Platform Limits
Shoptet as a platform requires a different approach, see Shoptet optimization (asynchronous GTM, shifts in cookie bar, JS modernization).
Changes in Core Web Vitals will reflect in Google’s data (CrUX) with a delay (typically visible movement starts appearing 1–2 weeks post-deployment). To prevent regression from sneaking onto production unnoticed, we recommend implementing long-term web speed monitoring with alerting for degradation.
Core Web Vitals Dashboard in PageSpeed.ONE Monitoring
A summary of Core Web Vitals metrics for mobile and desktop can be found in our web speed test tool, but also in the PLUS monitoring – in the Summary Report and others. Additionally, our tool allows tracking metric development at the domain or URL level over months.
Regular PLUS monitoring then supplements synthetic tests and regression alerts, ensuring you don’t stumble into a poor state blindly.