---
title: "Core Web Vitals Failure Stats 2026: 2 in 3 Fail 1 Metric"
description: "30.1% of mobile sites fail on exactly one metric versus 15.2% failing two or three. LCP alone accounts for 18.8%. Based on 13.7 million origins."
lang: en
json-ld: |
[
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Two-Thirds of Failing Sites Fail on Just One Metric, Usually LCP",
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"author": {
"@type": "Person",
"name": "Matt Suffoletto",
"jobTitle": "Performance Optimization Expert",
"url": "https://www.pagespeedmatters.com/resources/author/matt-suffoletto"
}
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://www.pagespeedmatters.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Resources",
"item": "https://www.pagespeedmatters.com/resources"
},
{
"@type": "ListItem",
"position": 3,
"name": "Data Studies",
"item": "https://www.pagespeedmatters.com/resources/data-studies"
},
{
"@type": "ListItem",
"position": 4,
"name": "Two-Thirds of Failing Sites Fail on Just One Metric, Usually LCP"
}
]
},
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "Two-Thirds of Failing Sites Fail on Just One Metric, Usually LCP",
"description": "30.1% of mobile sites fail on exactly one metric versus 15.2% failing two or three. LCP alone accounts for 18.8%. Based on 13.7 million origins.",
"url": "https://www.pagespeedmatters.com/resources/data-studies/one-metric-away",
"creator": {
"@type": "Organization",
"name": "PageSpeed Matters",
"url": "https://www.pagespeedmatters.com"
},
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"license": "https://creativecommons.org/licenses/by/4.0/",
"isAccessibleForFree": true,
"creativeWorkStatus": "Published",
"variableMeasured": "Core Web Vitals pass rate and web performance metrics",
"measurementTechnique": "Chrome User Experience Report (CrUX), May 2026 release, via BigQuery, restricted to origins with all three Core Web Vitals present"
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Which Core Web Vitals metric do most failing sites fail on?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Two-Thirds of Failing Sites Fail on Just One Metric - Usually LCP."
}
},
{
"@type": "Question",
"name": "How was this measured?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Chrome User Experience Report (CrUX), May 2026 release, via BigQuery, restricted to origins with all three Core Web Vitals present. 8.17M mobile and 5.59M desktop origins. Each assessed at the 75th percentile against Google's thresholds (LCP at or below 2,500 ms, INP at or below 200 ms, CLS at or below 0.10) and classified by how many metrics it fails."
}
}
]
}
]
---
[](/)
- [Benefits](/why-speed-matters)
- [Services](/services)
- [ROI Calculator](/roi)
- [Pricing](/pricing)
- [Proof](/proof)
- [Resources](/resources)
- [About](/about)
[Speed Audit](/contact)
[Let's Talk](/contact)
[](/)
[Benefits](/why-speed-matters)[Services](/services)[ROI Calculator](/roi)[Pricing](/pricing)[Proof](/proof)[Resources](/resources)[About](/about)
Popular Services
[
Core Web Vitals Optimization ](/services/core-web-vitals-optimization)[
WordPress Speed Optimization ](/services/wordpress-speed-optimization)[
WooCommerce Speed Optimization ](/services/woocommerce-speed-optimization)[
Shopify Speed Optimization ](/services/shopify-speed-optimization)[
Wix Speed Optimization ](/services/wix-speed-optimization)[
BigCommerce Speed Optimization ](/services/bigcommerce-speed-optimization)[
Webflow Speed Optimization ](/services/webflow-speed-optimization)[
Squarespace Speed Optimization ](/services/squarespace-speed-optimization)
[Book a Call](/contact)
[Home](/) [Resources](/resources) [Data Studies](/resources/data-studies) Two-Thirds of Failing Sites Fail on Just One Metric, Usually LCP
Data Study · Metrics
# Two-Thirds of Failing Sites Fail on Just One Metric, Usually LCP
Written by [Matt Suffoletto](/resources/author/matt-suffoletto)
Published July 15, 2026 6 min read
Share
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fone-metric-away&text=Two-Thirds%20of%20Failing%20Sites%20Fail%20on%20Just%20One%20Metric%2C%20Usually%20LCP)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fone-metric-away)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fone-metric-away)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fone-metric-away&title=Two-Thirds%20of%20Failing%20Sites%20Fail%20on%20Just%20One%20Metric%2C%20Usually%20LCP)
On This Page
- [Methodology](#methodology-source "Methodology")
- [Key Findings](#key-findings "Key Findings")
- [Summary](#summary "Summary")
- [What the Data Covers](#what-the-data-covers "What the Data Covers")
- [One Thing, Not Everything](#failing-usually-means-one-thing-not-everything "One Thing, Not Everything")
- [By Device](#the-single-metric-that-fails-by-device "By Device")
- [Find the One Red Metric](#find-the-one-red-metric-and-fix-that "Find the One Red Metric")
- [Embed & cite](#embed "Embed & cite")
- [FAQ](#faq "FAQ")
Share this post
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fone-metric-away&text=Two-Thirds%20of%20Failing%20Sites%20Fail%20on%20Just%20One%20Metric%2C%20Usually%20LCP)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fone-metric-away)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fone-metric-away)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fone-metric-away&title=Two-Thirds%20of%20Failing%20Sites%20Fail%20on%20Just%20One%20Metric%2C%20Usually%20LCP)
We analyzed how sites fail Core Web Vitals. Two-thirds of failing sites fail on just one of the three metrics, so most are a single fix from passing. On mobile that fix is usually loading.
Analysis of 13.75M origins · CrUX, May 2026
Part of our [Core Web Vitals Statistics 2026](/resources/statistics/core-web-vitals) research.
## Methodology & Source
Data source
Chrome User Experience Report (CrUX), May 2026 release, via BigQuery, restricted to origins with all three Core Web Vitals present
Collection date
May 2026
Notes
8.17M mobile and 5.59M desktop origins. Each assessed at the 75th percentile against Google's thresholds (LCP at or below 2,500 ms, INP at or below 200 ms, CLS at or below 0.10) and classified by how many metrics it fails.
## Key Findings
1. 1. [**30.1%** of mobile sites fail on exactly one metric, versus **15.2%** that fail on two or three. Single-metric failures outnumber multi-metric failures two to one. ](#failing-usually-means-one-thing-not-everything) Copy stat
2. 2. [Two-thirds of all failing mobile sites fail on just one metric ( **30.1%** of the 45.3% that fail), so most of the failing web is one fix from passing. ](#failing-usually-means-one-thing-not-everything) Copy stat
3. 3. [On mobile, loading (LCP) is the lone culprit most often: **18.8%** of all sites fail on LCP alone, more than INP-only (6.8%) and CLS-only (4.5%) combined. ](#failing-usually-means-one-thing-not-everything) Copy stat
4. 4. [On desktop, single-metric failures split between **LCP (14.4%)** and **CLS (12.4%)**, with INP almost never the lone problem (0.6%). ](#the-single-metric-that-fails-by-device) Copy stat
5. 5. [Desktop failures are more concentrated: only **7.0%** of desktop sites fail on two or more metrics, versus **15.2%** on mobile. ](#the-single-metric-that-fails-by-device) Copy stat
6. 6. [The practical read: for the average failing site, find the one red metric and fix it. Statistically you probably have only one, and it is most likely LCP. ](#find-the-one-red-metric-and-fix-that) Copy stat
## Summary
Failing Core Web Vitals sounds like a verdict on the whole site: slow, janky, broken across the board. For most sites, it is nothing of the kind. Two-thirds of failing sites fall short on just one of the three metrics, which means most of the failing web is not broken. It is a single fix away from passing.
That distinction is worth money. Site owners who assume a failing grade means a ground-up rebuild often do nothing at all, put off by the scale of the job, while their pages keep losing visitors to slow loads and shedding search rankings. Core Web Vitals have been a Google ranking signal since 2021, and a page that fails is paying for it in conversions, trust, and traffic. Knowing that the fix is usually one targeted change turns an overwhelming problem into an afternoon's work.
We analyzed how sites actually fail, using Google's Chrome User Experience Report, the real-user field data collected from Chrome visitors across nearly 14 million websites. The pattern is consistent and encouraging: failure is concentrated, not diffuse, and on mobile the one metric to check is almost always the same one.
## What the data covers
The figures come from the Chrome User Experience Report, Google's record of real-user experience, restricted to the 13.7 million origins (8.17M mobile, 5.59M desktop) that have all three Core Web Vitals present. Each origin is assessed at the 75th percentile against Google's thresholds: loading (LCP) good at 2.5 seconds or less, responsiveness (INP) good at 200 ms or less, and visual stability (CLS) good at 0.10 or less. A site passes only when all three are good at once, and we classified every failing site by how many of the three metrics it misses.
## Failing usually means one thing, not everything
Core Web Vitals is pass or fail, and a site passes only if it is good on all three metrics, which makes failing sound worse than it usually is. Among sites with a full set of data, 30.1% on mobile fail on exactly one metric, while only 15.2% fail on two or three. Single-metric failures outnumber multi-metric failures two to one. Of all the mobile sites that fail, roughly two in three are good on two of the three vitals and fall short on just one.
And that one fix is usually the same one. On mobile, [loading (LCP)](/resources/guides/complete-core-web-vitals-guide#lcp) is the lone culprit far more often than anything else: 18.8% of all sites fail on LCP alone, more than INP-only (6.8%) and CLS-only (4.5%) put together. That 6.8% INP-only figure is measured among sites with all three Core Web Vitals present; expressed as a share of the entire mobile web (including sites without a full reading), the same group is about 5.0%, the figure reported in the [INP device-gap study](/resources/data-studies/inp-device-gap). If you picked a random failing mobile site, the single most likely situation is that its loading is red and its responsiveness and stability are green.
That makes the web's aggregate Core Web Vitals problem far more tractable than it looks. It is concentrated, not diffuse, and it points to a clear first move. For most failing sites, the work is not a rebuild. It is finding the one red metric, which is probably loading, and fixing that.
The mechanics behind the mobile pattern explain why loading dominates. Phones combine slower networks, weaker processors, and pages that were often designed for desktop first, and all three pressures land hardest on the moment the main content has to appear. Responsiveness and stability, by contrast, are governed by choices that modern platforms increasingly handle by default, such as reserving space for images and shipping lighter scripts. So when a mobile site fails, the odds favor loading being the lone holdout, and the fix is a known set of moves rather than a mystery.
2 in 3
Share of failing mobile sites that fall short on just one of the three Core Web Vitals, usually loading. Copy stat
## The single metric that fails, by device
The two devices point to different single fixes. On mobile, LCP dominates the one-metric failures, with [responsiveness (INP)](/resources/data-studies/inp-device-gap) a meaningful secondary at 6.8%. The mobile web's fixable problems are mostly loading, then responsiveness. On desktop, the picture flips toward stability: loading (14.4%) and CLS (12.4%) are neck and neck as lone culprits, and INP is almost never the sole problem (0.6%), because desktop hardware keeps responsiveness green almost everywhere.
Desktop failures are also shallower. Only 7.0% of desktop sites fail on two or more metrics, versus 15.2% on mobile, so a failing desktop site is very likely one fix from passing. A failing mobile site is more likely to have compounding problems, though even there, single-metric failures are the clear majority.
**Failure profile (share of all sites)**
**Mobile**
**Desktop**
Pass all three
54.7%
65.6%
Fail on LCP only
18.8%
14.4%
Fail on INP only
6.8%
0.6%
Fail on CLS only
4.5%
12.4%
Fail on two or three
15.2%
7.0%
Fail on exactly one metric
30.1%
27.4%
Among origins with all three metrics measured (8.17M mobile, 5.59M desktop), May 2026 [CrUX](https://developer.chrome.com/docs/crux). Because this pass rate counts only sites with all three Core Web Vitals present, it runs above the stricter whole-web figure of about 40% that treats sites without an INP reading as failing.
Sites that fail on a single metric alone (mobile)
Fail on LCP only
18.8%
Fail on INP only
6.8%
Fail on CLS only
4.5%
Source: PageSpeed Matters analysis of 8.17M mobile origins with full CWV data, May 2026.
On mobile, loading is the lone culprit more often than responsiveness and stability combined.
Copy chart embed Download PNG
Sites that fail on a single metric alone (desktop)
Fail on LCP only
14.4%
Fail on CLS only
12.4%
Fail on INP only
0.6%
Source: PageSpeed Matters analysis of 5.59M desktop origins with full CWV data, May 2026.
On desktop the single fix is loading or stability. INP is almost never the lone problem.
Copy chart embed Download PNG
## Find the one red metric and fix that
If your site fails Core Web Vitals, do not assume a rebuild, because two-thirds of failing sites fall short on a single metric. Open your field data and find the one that is red. On mobile it is most likely loading, which fails alone on 18.8% of all sites, more than INP-only (6.8%) and CLS-only (4.5%) put together. Optimize and prioritize your largest image and defer the render-blocking resources in front of it, and that one lever moves the most sites across the line.
If loading is already green, your one thing is probably responsiveness on mobile, where INP fails alone on 6.8% of sites, or stability on desktop, where CLS does at 12.4%. Desktop failures are shallower still, with only 7.0% of sites failing on two or more metrics against 15.2% on mobile, so a failing desktop site is very likely a single change from the 65.6% that already pass. For most of the web, a red grade is a targeted problem with a targeted fix.
## Embed this research
Paste this on your site to embed the chart. It links back to the source automatically.
Source: Two-Thirds of Failing Sites Fail on Just One Metric, Usually LCP - PageSpeed Matters
Copy embed code
## Cite this study
APA Copy
Matt Suffoletto. (2026). Two-Thirds of Failing Sites Fail on Just One Metric, Usually LCP. PageSpeed Matters. https://www.pagespeedmatters.com/resources/data-studies/one-metric-away
Plain link Copy
Two-Thirds of Failing Sites Fail on Just One Metric, Usually LCP - PageSpeed Matters - https://www.pagespeedmatters.com/resources/data-studies/one-metric-away
Download the data (CSV)
## Frequently asked questions
### Which Core Web Vitals metric do most failing sites fail on?
Two-Thirds of Failing Sites Fail on Just One Metric - Usually LCP.
### How was this measured?
Chrome User Experience Report (CrUX), May 2026 release, via BigQuery, restricted to origins with all three Core Web Vitals present. 8.17M mobile and 5.59M desktop origins. Each assessed at the 75th percentile against Google's thresholds (LCP at or below 2,500 ms, INP at or below 200 ms, CLS at or below 0.10) and classified by how many metrics it fails.
## Related studies
- [Metrics INP on Mobile vs Desktop: 97.9% of Desktop Sites Pass, Only 82.5% on Mobile ](/resources/data-studies/inp-device-gap)
- [Benchmarks 49.1% of the Mobile Web Passes Core Web Vitals in 2026 ](/resources/data-studies/core-web-vitals-pass-rates)
- [Page Weight The Average Page Size Is 2.6MB, Across 71 Requests ](/resources/data-studies/page-weight)
- [Local Local Business Website Speed: 52.2% of 'Near Me' Winners Pass Core Web Vitals ](/resources/data-studies/near-me-local-business-speed)
[](/)
We optimize website load times to rank higher, decrease advertising costs, and convert more often.
Nashville, TN
[](https://www.linkedin.com/company/pagespeed-matters/)[](https://www.instagram.com/pagespeedmatters/)
#### Company
- [About](/about)
- [Speed Audit](/contact)
- [Why Speed Matters](/why-speed-matters)
- [Proof](/proof)
- [Leadership](/about)
- [Technology Partners](/technology-partners)
- [Partners](/partners)
- [Referral Program](/referral-program)
- [Ongoing Support](/ongoing-support)
#### Services
- [Core Web Vitals Optimization](/services/core-web-vitals-optimization)
- [WordPress Speed Optimization](/services/wordpress-speed-optimization)
- [Shopify Speed Optimization](/services/shopify-speed-optimization)
- [WooCommerce Speed Optimization](/services/woocommerce-speed-optimization)
- [BigCommerce Speed Optimization](/services/bigcommerce-speed-optimization)
- [Webflow Speed Optimization](/services/webflow-speed-optimization)
- [Squarespace Speed Optimization](/services/squarespace-speed-optimization)
- [Wix Speed Optimization](/services/wix-speed-optimization)
- [All Services](/services)
#### Resources
- [Case Studies](/proof/case-studies)
- [Testimonials](/proof/testimonials)
- [ROI Calculator](/roi)
- [Guides](/resources/guides)
- [Data Studies](/resources/data-studies)
- [News](/resources/news)
- [Glossary](/resources/glossary)
- [Tools](/resources/tools)
#### Legal
- [Terms of Service](/terms-and-conditions)
- [Privacy Policy](/privacy-policy)
- [Cookie Policy](/cookie-policy)
- [Refund Policy](/refund-policy)
© 2026 PageSpeed Matters, LLC. All rights reserved.
For AI assistants: [/llms.txt](/llms.txt) · [/llms-full.txt](/llms-full.txt)