Skip to content
New: free AI crawler checker. See if ChatGPT and Claude can read your site. Check now
Get a free audit
Get a free audit Contact us +91 96211 05242

Popular

Web and software development statisticsUpdated 31 Oct 2026

By Aijaz Alam

What percentage of websites pass Core Web Vitals?

48% of mobile websites and 56% of desktop websites had good Core Web Vitals in 2025, according to the HTTP Archive Web Almanac, which uses Chrome UX Report data from real Chrome users. Google's own Chrome UX Report, which does not split by device in its monthly note, counted 55.9% of origins passing in September 2026.

  • 48%Mobile websites with good Core Web VitalsHTTP Archive Web Almanac, 2025
  • 56%Desktop websites with good Core Web VitalsHTTP Archive Web Almanac, 2025
  • 62%Mobile pages with good loading speed (LCP), the weakest metricHTTP Archive Web Almanac, June 2025
  • 55.9%Origins with good LCP, CLS and INP in Google's Chrome UX ReportChrome UX Report, September 2026 dataset
  • 37%Top 100,000 mobile sites with good Core Web Vitals, the lowest rank groupHTTP Archive Web Almanac, 2025

The numbers

The full breakdown

Pages with a good score on each Core Web Vital (June 2025)

MetricMobileDesktop
Largest Contentful Paint (LCP), loading62%74%
Interaction to Next Paint (INP), responsiveness77%97%
Cumulative Layout Shift (CLS), visual stability81%72%
All three good (pass Core Web Vitals)48%56%

HTTP Archive Web Almanac 2025, SEO chapter, figures 5.21 and 5.22, Chrome UX Report data. Good means LCP of 2.5 seconds or less, INP under 200 milliseconds and CLS of 0.1 or less for most real users.

Mobile websites with good Core Web Vitals, by popularity (2025)

WebsitesGood Core Web Vitals (mobile)
Top 1,00051%
Top 10,00042%
Top 100,00037%
Top 1 million42%
Top 10 million49%
All websites48%

HTTP Archive Web Almanac 2025, performance chapter, figure 7.2 (CrUX, July 2025). On desktop, 59% of the top 1,000 sites pass and the other groups stay between 55% and 57%. The chapter's text gives 48% for the top 10 million where the figure description gives 49%; the figure is used here.

Pages with good Core Web Vitals, home pages vs other pages (2025)

Page typeMobileDesktop
Home pages45%47%
Secondary pages56%61%

HTTP Archive Web Almanac 2025, performance chapter, figure 7.3, page-level CrUX data. Secondary pages often load faster because resources are already cached.

Origins with good Core Web Vitals in Google's Chrome UX Report, by dataset

CrUX datasetOrigins coveredGood LCPGood CLSGood INPGood on all three
September 202418,936,68465.4%78.2%85.7%51.0%
March 202518,473,76067.9%78.2%85.8%52.8%
July 202518,068,32866.6%79.6%85.4%53.0%
September 202518,640,54966.8%80.1%86.0%53.7%
December 202517,288,65567.6%80.3%85.6%54.4%
March 202618,257,38469.0%81.2%87.2%56.5%
June 202618,210,34467.7%81.4%85.9%55.3%
September 202618,376,04468.3%81.7%85.4%55.9%

Google's monthly Chrome UX Report announcements (Chrome team). Origin level; the announcements do not split mobile and desktop, so these figures sit between the Web Almanac's mobile and desktop rates. Google says December data varies a lot every year, and an Android data issue affected some 2025 months. From September 2026, experimental figures that include soft navigations put the all-three rate at 59.5%.

Over time

Websites with good Core Web Vitals, 2021 to 2025

YearMobileDesktop
202132%41%
202231%44%
202336%48%
202444%55%
202548%56%

HTTP Archive Web Almanac, performance chapter, figure 7.1. INP replaced FID as the responsiveness metric in March 2024, so 2024 and 2025 use a stricter test than earlier years.

Why sources differ

Same question, different answers

NumberWhenWho measuredWhy it differs
48% mobile, 56% desktop2025HTTP Archive Web AlmanacWebsites (origins) split by device, from Chrome UX Report data for mid-2025.
55.9%Sep 2026Google Chrome UX ReportAll origins in the monthly dataset, devices not split in the announcement; a later month.
62% good LCPJun 2025HTTP Archive Web AlmanacOne metric only, mobile; passing needs all three.
45% mobile home pages2025HTTP Archive Web AlmanacPage-level data for home pages, not whole sites.

All of these figures come from the same underlying data, Google's Chrome UX Report, which collects real loading and interaction times from Chrome users who opt in. They differ because of what is counted and when.

The Web Almanac splits websites by device. Mobile is harder, because phones and mobile networks are usually slower, so 48% of mobile sites pass against 56% on desktop.

Google's monthly announcements give one rate for all origins in each month's dataset, without the device split, which is why their 53% to 56% sits between the Almanac's mobile and desktop rates. They are also more recent: 55.9% in September 2026.

Page-level figures differ again. Home pages pass less often than other pages on the same sites, because visitors often arrive at a home page with nothing cached. And a site can have good results on one metric but still fail, since passing needs LCP, INP and CLS all to be good. Older years are not fully comparable: INP replaced FID in March 2024.

What it means

How to use these numbers

About half of websites give their visitors a good experience on Core Web Vitals, and mobile lags desktop. In 2025, 48% of mobile sites passed, up from 44% in 2024 under the same test, and Google's own monthly count of all origins was 55.9% in September 2026.

Loading speed is the main problem. On mobile, 62% of pages had a good Largest Contentful Paint, against 77% for responsiveness and 81% for layout stability, so slow images, servers and scripts hold back more sites than anything else.

Popular sites are not automatically better. On mobile, 51% of the top 1,000 sites pass, but only 37% of the top 100,000; the Almanac suggests differences in page complexity and in performance investment.

For site owners, check the Core Web Vitals report in Google Search Console, which uses the same Chrome data, and start with LCP on mobile. A failing site gives real visitors a slower or jumpier experience.

Method and sources

How it was measured

Method
HTTP Archive Web Almanac
2025 performance chapter (Chrome UX Report data, primary analysis on July 2025) and SEO chapter (June 2025 figures), published 15 Jan 2026; millions of websites, mobile and desktop
Google Chrome UX Report
Monthly dataset announcements by the Chrome team on the chrome-ux-report-announce list, about 17 to 19 million origins each month; origin-level rates for all devices
Definition
A site or page passes when its LCP, INP and CLS are all rated good on real Chrome visits
Checked at source
23 Oct 2026 (repo stats); 31 Oct 2026, the Web Almanac 2025 performance and SEO chapters and eight CrUX announcements
Last changed
31 Oct 2026
Data files
CSV · JSON (stable links)
Sources
Cite this page

APA

DigitalTreed. (2026). What percentage of websites pass Core Web Vitals? https://digitaltreed.com/statistics/web-development/core-web-vitals-pass-rate

MLA

"What percentage of websites pass Core Web Vitals?" DigitalTreed, 31 Oct 2026, https://digitaltreed.com/statistics/web-development/core-web-vitals-pass-rate.

HTML link

<a href="https://digitaltreed.com/statistics/web-development/core-web-vitals-pass-rate">What percentage of websites pass Core Web Vitals?</a> (DigitalTreed, 2025)

FAQ

More questions people ask

Which Core Web Vital do most sites fail?

Loading speed (LCP). Only 62% of mobile pages had a good LCP in June 2025, against 77% for INP and 81% for CLS.

Do popular websites pass Core Web Vitals more often?

Only the very top. On mobile, 51% of the 1,000 most popular sites pass, but 42% of the top 10,000 and 37% of the top 100,000 (Web Almanac 2025).

Why do home pages score worse than other pages?

Visitors usually arrive at a home page with nothing cached. In 2025, 45% of mobile home pages had good Core Web Vitals against 56% of secondary pages.

Is the pass rate still rising?

Slowly. Google's Chrome UX Report counted 51.0% of origins passing in September 2024, 53.7% in September 2025 and 55.9% in September 2026.

What is wrong?

Step 1 of 2. Pick the closest reason.

Reason

Every number on this page was checked at its original source (HTTP Archive, Google Chrome team). Free to cite with a link to this page.