theweb.report

We crawled 14,764,966 websites to find out what the web actually looks like. Platform market share, real performance data, security risks, and which technology choices make a measurable difference.

14.8M
domains crawled
12.3M
live and analysed
1,059
platforms detected

We crawled the homepage of every primary domain from Google Chrome's User Experience Report dataset. The list of domains comes from real Google Chrome users, and reflects sites that are actually receiving visits. This is what a slice of the active web looks like.

# What 14.8 million domains turned out to be

Not every domain in the dataset runs an established website. Some are domains that are for sale, others are default pages waiting for a real site, spam, or just broken. 7.3% of sites blocked us from loading a page at all.

Filtering out the noise and errors leaves us 13.5 million real websites.

14,764,966

Served us a page

83.4% · 12,324,984

Blocked

7.3% · 1,080,408

Error

5.4% · 789,988

Not a real site

3.9% · 569,586

# Every third site is WordPress

WordPress comes in two forms. The open source software from wordpress.org is downloaded and run on hosting of your own choosing, and it accounts for 4,654,967 of the sites we crawled. WordPress.com is the hosted service Automattic sells and it accounts for 75,869. The open source version is 61.4 times the size of the paid one.

WooCommerce is a plugin that can run on either version and is installed on 22.1% of every WordPress site we found.

35.01%

of the 13,513,049 websites we crawled run WordPress: 4,730,836 sites.

WordPress.org Every other site
34.45%
Self-hosted WordPress.org
4,654,967 sites
0.56%
WordPress.com
75,869 sites
7.72%
WooCommerce
1,043,221 sites, running on both wordpress.org and wordpress.com

# Platform Market Share

Each square denotes one in every hundred websites we crawled. The ten market leaders are shown; another 1,049 platforms we can identify run the remaining 1,967,330 sites between them.

WordPress.org
34.45%
Shopify
5.65%
Wix
3.57%
Squarespace
2.02%
Joomla
0.96%
Webflow
0.81%
Lovable
0.62%
Drupal
0.62%
Tilda
0.61%
Duda
0.6%
1,049 other platforms
14.57%
No CMS identified
35.52%

# The busier a website is, the less likely it is to run off-the-shelf software

As website traffic increases the most popular CMS platform (WordPress.org) decreases in market share and custom website builds dominate. WordPress is most popular on sites that people visit less frequently.

Download chart

Traffic rank comes from Google's Chrome User Experience Report, which sorts the sites it observes into popularity bands.

Top 100k
Top 1M
Top 10M

# 64.1% of the platforms we identified are self-hosted

Self-hosted software runs on a server the site's owner controls or pays for directly: they choose the host, the configuration, and when any of it changes. On a hosted platform the company runs both the software and the server.

Download chart

Shares of the 8,712,650 sites where we identified the platform.

8,712,650

# 60.4% of the platforms we identified are open source

Open source content management systems mean the code is open and public and often written and maintained by a community. Source available is similar, but comes with more restrictions. Closed source is private and you are not allowed to edit, view or republish the code.

Download chart

We map a system to its licence when their code is available on services like npm and GitHub. When a licence can't be identified we assume closed source.

8,712,650

3,049,964 sites have ecommerce functionality

# We identified 339 ecommerce platforms

We detect ecommerce on 339 platforms. For multi-purpose CMSs like WordPress.org we detect installations of 6 ecommerce plugins (including WooCommerce and Easy Digital Downloads). For platforms like Wix and Squarespace we also detect the activation of their commerce features.

WooCommerce

34.2% of stores · 1,043,221

Self-hosted SaaS

# Domestic platforms lead in South Korea, Argentina, Russia, Czechia and Saudi Arabia

WooCommerce leads in most countries including Britain, Germany, France, Spain and Italy. Shopify leads in Australia, India and Canada. Everywhere else the market-leader is usually domestic: Cafe24 87.6% in South Korea, Tiendanube 56.8% in Argentina, Bitrix 49% in Russia, Shoptet 37.9% in Czechia, Salla 37% in Saudi Arabia and Prom.ua 35.5% in Ukraine.

Map metric
—
—
—
Geographic location comes from the site's location schema (where defined) and the domain's TLD, excluding .com and some country domains like .co that have become trendy.

# Shopify stores clear all three Core Web Vitals twice as often as WooCommerce stores

Google's Core Web Vitals measure a webpage's user experience. They assess loading speed, interactivity, and visual stability. We mapped a site's pass rate back to the platform it runs on. Of the two most popular platforms, stores running on Shopify pass Core Web Vitals on 86.9% of sites, nearly double the rate of 44.4% for WooCommerce stores.

Tiendanube 89.0% · 45,272 stores Shopify 86.9% · 761,477 stores Wix 85.8% · 318,641 stores OpenCart 83.0% · 54,201 stores Squarespace 82.8% · 107,015 stores Bitrix 75.2% · 53,996 stores Cafe24 73.3% · 26,319 stores PrestaShop 71.4% · 69,703 stores Magento 59.6% · 30,653 stores WooCommerce 44.4% · 1,043,221 stores
The 10 largest platforms, each with at least 1,000 live stores.

# 192,701 ecommerce sites (10%) send no HTTP security headers

HTTP security headers enforce specific rules for what a site can load and do and help mitigate security vulnerabilities.

On average SaaS / hosted ecommerce sites do a better job of setting security headers on requests, setting 3.03 of these 5 headers on average, versus 1.28 on self-hosted stores. 48.8% of self-hosted stores send none of them at all, against 3.9% of SaaS ones.

Shopify is the most secure platform, sending four of the five headers to nearly every store it runs, and no platform sends all five.

SaaS platforms Strict-Transport-Security (HSTS) Content-Security-Policy X-Frame-Options X-Content-Type-Options Referrer-Policy
Shopify 99.8%100% 99.6%100% 99%99% 99.7%100% 0.1%0%
Wix 99.9%100% 0%0% 0%0% 99.9%100% 0%0%
Squarespace 60.1%60% 0.1%0% 54.1%54% 99.8%100% 0%0%
Tiendanube 97.2%97% 97.1%97% 0%0% 97.1%97% 0%0%
Cafe24 96.1%96% 0.2%0% 0%0% 96.2%96% 96.2%96%
Odoo 50.3%50% 4.6%5% 8%8% 88%88% 40.3%40%
Tilda 0.1%0% 0.1%0% 94.7%95% 4.2%4% 0%0%
Square Online 99.9%100% 0%0% 0%0% 0%0% 0%0%
BigCommerce 35.8%36% 2.2%2% 43.8%44% 99.4%99% 0.3%0%

Self-hosted platforms

PrestaShop 18.7%19% 8.1%8% 13.9%14% 16%16% 9.8%10%
OpenCart 17.5%18% 6.1%6% 11.8%12% 14.6%15% 9.3%9%
Bitrix 22.4%22% 17%17% 35.5%36% 28.7%29% 3.6%4%
Magento 36.6%37% 29.6%30% 91.6%92% 87.2%87% 11.2%11%
Shopware 78.7%79% 4.8%5% 88.3%88% 77.4%77% 76.2%76%

No stores → Every store

Share of each platform's stores whose homepage arrived carrying the header, for platforms running at least 15,000 stores. Where a hosted platform is not at 100%, it is usually a store running a custom frontend the platform never rendered, or a domain served from somewhere other than the platform's own edge. Presence is not quality: we record that a header arrived, not whether its value was strict enough to stop anything.

4,654,967 sites run on WordPress.org

# WordPress.org is a very flexible open source CMS running 34.5% of sites

Developers can edit the code and site owners can install and change site themes and plugins. That same flexibility means the user experience, quality and speed of a WordPress site can vary a lot depending on how it's set up, where it is hosted, and what theme and plugins are installed.

61.5%

Running a cache · 2,863,055 sites

53.4%

Built with a page builder · 2,487,369 sites

33.1%

Publishing no meta description · 1,541,936 sites

8.8%

Running a version with a known security hole · 409,981 sites

# Three themes run a quarter of WordPress, and all three sit in the bottom half on Google's Largest Contentful Paint (LCP) metric

Hello Elementor, Astra and Divi run 1,157,496 sites between them. GeneratePress leads on LCP at 66.7%.

Caching matters more than the theme. We count a site as cached when a caching plugin, a cache on its server, or a CDN is storing a finished copy of the page. Cached, every theme here responds in 267 to 355ms. Uncached, the same themes take 964 to 1,890ms, so the difference between them only shows on a site that does not cache.

ThemeSitesCached (TTFB)Uncached (TTFB)LCP (loading)
558,968295ms1.4s
50.6%
300,382274ms1.5s
54.8%
Astra298,146305ms1.4s
49.4%
109,804274ms1.2s
58%
90,685294ms964ms
66.7%
89,440355ms1.3s
62.6%
81,718278ms1.9s
35.3%
66,628294ms1.1s
63.8%
56,737295ms1.4s
49.8%
49,124267ms1.1s
62.2%

# WordPress editors and page builders, by speed and Core Web Vitals

53.4% of WordPress sites run a page builder plugin we detect.

We looked at WordPress sites from version 5.0 onwards, and measured their median TTFB when the site is cached (server, CDN and/or plugin) versus uncached. The Classic Editor plugin leaves no trace in the page, so we infer it when no block markup and no other page builder is found.

EditorSitesCached (TTFB)Uncached (TTFB)LCP (loading)
1,212,156305ms1.4s
44.5%
853,828317ms881ms
68.8%
538,855302ms980ms
64.7%
326,742293ms1.2s
49.1%
137,936289ms876ms
72%
71,051262ms1.4s
51.8%
Beaver Builder43,082236ms1.3s
64.1%
Spectra27,206290ms1.1s
61.6%
14,826246ms1.1s
66.2%
Oxygen14,026258ms1.1s
67.4%

# WordPress sites with a caching plugin respond in good time 77.9% of the time, against 36.6% with no caching

38.3% of WordPress sites run no caching we can identify. Where a CDN serves the page from its own cache, 99.5% respond in good time.

CDN edge

CMS plugin

Origin

No cache

  1. ≤800ms
  2. ≤1800ms
  3. >1800ms

# Some cache plugins perform wildly differently depending on the server they're optimised for

We compared self-hosted WordPress sites running the latest major version, split by web server and by caching plugin. Each panel shows the 10 most-installed plugins with at least 500 sites on that server.

LiteSpeed Cache is built for the LiteSpeed server. On nginx and Apache the same plugin is slower than running no cache plugin at all. WP Rocket holds up wherever it lands.

Web server
TTFB Passing CWV
WP Rocket TTFB 153–432ms CWV
56.6%
WP-Optimize TTFB 153–437ms CWV
54.5%
TTFB 146–486ms CWV
56.6%
TTFB 164–371ms CWV
64.5%
SG Optimizer TTFB 186–893ms CWV
62.1%
TTFB 172–1101ms CWV
50.2%
TTFB 211–1261ms CWV
51.9%
TTFB 205–1178ms CWV
55.8%
TTFB 485–1751ms CWV
53.8%
LiteSpeed Cache TTFB 417–2334ms CWV
37.8%
  • 25th percentile
  • Median
  • 75th percentile

04 Infrastructure

Next · 05 Performance

4,098,928 sites sit behind one provider, Cloudflare

# Cloudflare serves 70.5% of the sites that use a CDN

A CDN sits between a visitor and a website and serves the site's pages and files from a server near the visitor. We detected a CDN on 43.1% of sites, and 70.5% of those are served by Cloudflare.

70.5% of CDN-served sites · 4,098,928 · Standalone

# Cloudflare answers DNS for more sites than the next 3 operators combined

Which nameservers a domain points at is a separate choice from who hosts the site, and most sites inherit it from whoever sold them the domain. Cloudflare's grip here is far looser than the 70.5% of CDN-served sites it delivers, but this is still the first answer every browser waits on.

Download chart

A site counts as self-hosted when every nameserver it delegates to sits on the site's own domain, such as example.com answered by ns1.example.com.

Cloudflare 16.6% · 1,594,176 GoDaddy 9.9% · 947,332 Wix 3.3% · 316,436 AWS 3% · 286,196 Google Cloud 2.2% · 216,061 OVHcloud 2.1% · 203,009 IONOS 2.1% · 197,254 Hostinger 1.8% · 177,504 GMO Internet 1.7% · 161,522 Xserver 1.5% · 144,548 Self-hosted 0.93% · 88,966

# Hostinger hosts more sites than any other provider we identified

We identify 555 hosting providers from 455 signals: the network a site's server sits on, the headers the server sends back, and the names its DNS points at. Hostinger is the largest, with 685,708 sites, 6.87% of every site whose host we could name.

Hostinger 6.87% · 685,708 AWS 4.16% · 414,754 OVHcloud 3.59% · 358,528 Hetzner 3.34% · 333,719 Vercel 3.27% · 326,179

# 50.9% of sites tell you what server software answered

Every HTTP response can carry a server header that names the underlying webserver that handled the request. 99% of sites behind Cloudflare hide their origin server.

42.8% of sites disclosing a server · 2,764,229

# Infrastructure concentration

The Herfindahl-Hirschman Index squares every supplier’s share and adds them up, so one dominant player counts far more than many small ones. A pure monopoly scores 10,000. Regulators read below 1,500 as competitive and above 2,500 as highly concentrated.

Layer Largest supplier Concentration · HHI of 10,000 Verdict
CDN 29 suppliers 70.5% share 5,072 Highly concentrated
Platform 1,059 suppliers WordPress.org 53.4% share 2,985 Highly concentrated
DNS 143 suppliers 16.6% share 428 Competitive
Hosting 205 suppliers Hostinger 6.87% share 155 Competitive
  • The 2,500 highly-concentrated threshold
A market split between more suppliers scores lower, so the four layers are not perfectly like for like. The suppliers column shows how many each index covers. Each layer counts only the sites whose supplier we could identify.

# Seven companies, and how much of the web each one sits inside

Counted by company rather than by product, across every layer above: the nameserver, the CDN, the hosting, the firewall, and the scripts, fonts and embeds a page loads. A site counts once for a company however many of its products it carries, so the parts under a row add up to more than the row.

Company % of live sites
Google 67.23%
  • Analytics 43.66%
  • Google Fonts 36.83%
  • Tag Manager 19.84%
  • Ads 16.64%
  • Embeds 11.64%
  • reCAPTCHA 8.7%
  • Libraries 5.72%
  • Cloud and Firebase 3.16%
  • Translate, Sign-In 1.97%
Cloudflare 39.76%
  • Firewall 30.55%
  • CDN 30.36%
  • DNS 13.69%
  • cdnjs 8.62%
  • Turnstile 0.82%
  • Web Analytics 0.3%
  • Hosting 0.03%
Meta 15.63%
  • Pixel and SDK 14.87%
  • Facebook embeds 0.71%
  • Instagram embeds 0.31%
Automattic 13.23%
  • Jetpack 7.97%
  • WooCommerce 7.72%
  • Akismet 5.07%
  • Gravatar 0.63%
  • WordPress.com 0.59%
  • WP Cloud 0.11%
  • WordPress VIP 0.04%
Microsoft 7.75%
  • Clarity 4.79%
  • LinkedIn Insight 1.41%
  • Azure 1.21%
  • Bing Ads 1.2%
  • GitHub Pages 0.24%
  • SharePoint 0.01%
Amazon 5.84%
  • AWS 3.4%
  • Route 53 2.5%
  • CloudFront 1.93%
  • Ads 0.12%
  • AWS WAF 0.1%
Adobe 3.79%
  • Adobe Fonts 3.33%
  • Commerce 0.26%
  • Analytics 0.13%
  • Experience Manager 0.1%
  • Marketo 0.03%

05 Performance

Next · 06 Front end

5,576,934 sites pass Core Web Vitals

# 78.6% of sites on SaaS platforms pass Core Web Vitals, against 55.6% on WordPress.org

When one company controls the whole stack, sites tend to be fast by default. The options sold on speed are no better than average: headless CMS sites pass at 58.8% and enterprise CMS sites at 57.1%, level with the 60.5% of sites whose platform we could not identify. AI site builders pass at 30.7%.

Sites Passing Core Web Vitals
SaaS platforms Sites 3,005,310 Passing Core Web Vitals
78.6%
Other self-hosted CMS Sites 710,246 Passing Core Web Vitals
75.2%
No platform identified Sites 4,789,556 Passing Core Web Vitals
60.5%
Headless CMS Sites 118,975 Passing Core Web Vitals
58.8%
Enterprise CMS Sites 59,113 Passing Core Web Vitals
57.1%
WordPress.org Sites 4,634,583 Passing Core Web Vitals
55.6%
AI site builders Sites 126,546 Passing Core Web Vitals
30.7%

# Core Web Vitals pass rate by time to first byte

Core Web Vitals are Google's measure of what real visitors experienced: how quickly the main content appeared, how fast the page responded, and how much it moved while loading.

% sites passing all 3 Core Web Vitals

Under 200ms 67.9% · 2,750,788 200 to 800ms 68% · 4,220,091 800 to 1800ms 55.4% · 1,228,040 Over 1800ms 26.3% · 593,854

# Where caching sits, and how common each layer is

Caching keeps a finished page ready so the server does not rebuild it for every visitor. It can be generated by a plugin or the CMS on the site, on the server itself, or at a CDN in front of both, and 58.8% of sites have at least one of the three in place.

CMS plugin 16.1% · 2,172,549 Origin cache 13.2% · 1,778,989 Behind a CDN 43.1% · 5,817,813

# Only 17.5% of homepages behind a CDN were served from its cache

Where the CDN edge was not caching the HTML at all, the largest group here by some distance, the median page arrived slower than the median site with no CDN at all. That is not the CDN failing; it is a CDN doing nothing except adding a hop.

Where the page is cached, the CDN vendors are within 71ms of each other. Where it is not, they span 884ms.

Served from the edge cache, a median TTFB of 140ms
1,015,496

# Response compression

Compressing a response is the oldest speed win there is, and 6.8% of sites still skip it. Brotli packs the same page smaller than gzip; Zstandard packs and unpacks it faster, and browsers only began accepting it in 2024.

Brotli
4,714,072

# Page-level performance

Image optimisation reduces the number of bytes sent on page load, whilst hints tell the browser which order to fetch assets in. Charts show adoption only, how common a technique is, not its effectiveness.

Images

<img loading="lazy"> 62.4% <img fetchpriority="high"> 36.9% WebP 23.7% AVIF 1.8%

Scripts and resource hints

<script async> 65.3% <script defer> 52.7% <link rel="preconnect"> 36% <link rel="preload"> 34.8%

6,611,511 sites still load jQuery

# jQuery runs on 53.7% of the homepages we read

jQuery was released in 2006 to paper over the differences between browsers of that era. Those differences are gone, the browsers that caused them are gone, and 6,611,511 sites still load it.

React is the largest of the modern libraries, on 10.6% of the live sites we visit.

jQuery 53.67% · 6,611,511 React 10.59% · 1,304,267 Vue 1.47% · 180,857 Alpine.js 0.34% · 41,646 Angular 0.27% · 33,573 Turbo (Hotwire) 0.16% · 19,100 Svelte 0.13% · 16,248 HTMX 0.06% · 7,511 Stimulus (Hotwire) 0.04% · 5,116 Expo (React Native Web) 0.01% · 1,408 Solid 0.00% · 547 Ember 0.00%

# Webflow includes jQuery on 97.6% of the sites it builds. Wix includes it on 0.2%.

WordPress bundles jQuery with the software, which explains a large part of its reach: 84.9% of WordPress sites carry it. It does not explain Webflow, a visual builder launched in 2013 that puts jQuery on almost everything it makes. Wix is the same kind of product and has all but removed it, so this is a decision each platform takes rather than something the web is stuck with.

Webflow 97.6% of 111,707 WordPress.org 84.9% of 4,682,203 Joomla 80.3% of 134,359 Shopify 17.1% of 755,081 Squarespace 11.2% of 272,723 Wix 0.2% of 480,150

# Every modern meta-framework combined reaches 6.3% of the homepages we read

A meta-framework builds a site out of components and renders it on the server, the browser, or both. They are what the last decade of frontend writing has mostly been about. Next.js is the category: 544,513 sites, more than the other nine put together.

Next.js 4.42% · 544,513 Nuxt 0.90% · 111,257 Astro 0.63% · 77,552 SvelteKit 0.11% · 13,239 Gatsby 0.09% · 11,613 React Router 0.08% · 10,127 Remix 0.03% · 4,043 Hydrogen 0.02% · 1,961 Vue Storefront 0.00% · 143

# 94,159 sites run a headless CMS

Headless sites have a separate system from the rendered page you view. They account for 0.76% of the live sites we visit.

When we detect a site looks like a headless install we take a closer look at the site's JavaScript. We map environment variables, function names, API endpoints and script namespaces to headless CMS providers. Even this is imperfect as code can be abstracted or pre-rendered, so these market share numbers are a minimum.

Sanity 23% · 21,681 21.2% · 19,975 Strapi 11.2% · 10,511 Contentful 9.9% · 9,289 Storyblok 5.9% · 5,551 Prismic 4.8% · 4,530 Payload 3.4% · 3,245 Directus 3.3% · 3,079 DatoCMS 2.8% · 2,618 Drupal 2.2% · 2,114

# Hugo builds 60.9% of the static sites we can identify

A static site generator turns folders of content into finished HTML before anyone visits. There is no database and no application serving the page, so the output is indistinguishable from any other HTML file. We identified 17,871 sites built this way, which is 0.14% of everything we crawled.

Hugo 60.9% · 10,881 Jekyll 19.4% · 3,468 Docusaurus 6.9% · 1,228 VitePress 4.3% · 763 Eleventy 2.7% · 483 Quarto 2.1% · 378 VuePress 1.3% · 238 Gridsome 1.3% · 226 Scully 0.6% · 101 Pelican 0.3% · 54 React Static 0.3% · 51

# 117,961 sites keep their data in Supabase and 59,171 in Firebase

A backend service supplies the database, the sign-in and the file storage behind a site, so the code that runs in the browser is the whole application. Firebase has sold that since 2011 and Google has owned it since 2014. Supabase, built on Postgres and launched in 2020, has caught it up in five years.

Download chart

We find a backend service in the page for every site, and in the JavaScript only for the sites whose code we read. A site whose platform we had already identified rarely has its JavaScript read, so these counts are a minimum market share.

0.96% · 117,961 Firebase 0.48% · 59,171 0.06% · 7,276 0.04% · 5,271 0.02% · 2,797 0.02% · 2,569 0.01% · 1,241 0.01% · 698 0.00% · 261 0.00% · 32

# Laravel runs 264,354 sites, more than any other backend framework

A backend framework is the code a developer builds a site on when no platform does the work for them. We find one on 668,594 sites, 4.95% of everything we crawled, from the session cookie, the form token or the header it sets for itself. A platform built on a framework counts here too, so Statamic sites count towards Laravel and Discourse forums towards Rails.

1.96% · 264,354 1.38% · 186,562 0.52% · 70,001 0.41% · 55,176 0.30% · 40,656 0.14% · 19,161 0.11% · 14,803 0.08% · 11,400 0.04% · 5,162 0.01% · 1,029

# 13.0% of sites still include markup for a browser that was retired in 2022

HTML5 became a W3C recommendation on 28 October 2014, and 96.1% of sites now declare it. The rest are XHTML, HTML 4, or the 134,615 pages that declare no doctype at all.

The second chart counts markup written for software that has since been withdrawn. Microsoft retired Internet Explorer on 15 June 2022, and 1,595,195 sites still carry a conditional comment addressed to it. Adobe ended Flash on 31 December 2020, and 21,922 sites still embed it.

Doctype served

HTML5
96.08% · 11,836,157

Legacy markup features

IE Conditional 12.95% · 1,595,195 Deprecated HTML 6.00% · 739,359 XHTML doctype 2.12% · 261,617 Adobe Flash object/embed 0.18% · 21,922

5,156,506 sites have a security issue we detected

# 33.8% of sites set no security header at all

A security header is one line in a server's response telling the browser what to refuse: which scripts may run, whether the page can be framed, whether to insist on encryption. Adding one is a single line of configuration. Keeping a strict one working as a site changes is the harder part, which is where most sites stop.

X-Content-Type-Options 37.1% · 5,006,777 Strict-Transport-Security (HSTS) 35.1% · 4,745,048 X-Frame-Options 28.2% · 3,805,490 Content-Security-Policy 22.9% · 3,090,431 Referrer-Policy 19.7% · 2,655,512 Permissions-Policy 12.4% · 1,680,768

# 196,914 sites cannot serve a working HTTPS connection

We request every site over HTTPS first and fall back to plain HTTP only when the handshake fails, 1.46% of sites.

Most of those failed sites already have a certificate. Only 31,203 of them have no HTTPS at all. The rest serve one the browser refuses: issued for a different domain, signed by an authority the browser doesn't trust, or long expired. A visitor gets a full page warning before they get the site.

Certificate hostname mismatch 0.56% · 75,453 Handshake failed 0.28% · 37,161 No HTTPS 0.23% · 31,203 Self-signed certificate 0.23% · 30,554 Untrusted certificate chain 0.06% · 8,293 Certificate expired 0.06% · 8,259 Obsolete TLS version 0.01% · 1,806

# 48.1% of sites that reveal their PHP version run a version that is no longer getting security patches

We detect PHP is running on 3,080,957 sites. Of those sites 1,838,448 leak or expose the version of PHP the site is running on.

Leaving the PHP version declared in HTTP headers isn't the best idea from a security perspective and updating the version of PHP on your hosting is normally a simple task.

  • PHP 8.4+ (active support) · 13.4% · 247,226
  • PHP 8.2 to 8.3 (security fixes only) · 38.4% · 706,517
  • PHP 8.0 to 8.1 (end of life) · 13.7% · 252,524
  • PHP 7.x (end of life) · 26.9% · 495,069
  • PHP 5.x and older (end of life) · 7.5% · 137,107

# 8.8% of WordPress sites run a version with a known security hole

WordPress leaks its version number in asset paths by default; we detect the version on 62.8% of installs.

WordPress has shipped 959 releases; the latest when we crawled was 7.1.2. Most sites trail it by a version or two. The rest sit on an end-of-life release that will never be patched again.

  • Up to date · 85% · 2,477,703
  • Maintenance update only · 0.9% · 26,652
  • Security patch pending · 4.1% · 120,902
  • A major version behind · 6.2% · 181,858
  • End-of-life, unsupported · 3.7% · 106,514

# Where a WordPress site is hosted changes its odds of being updated

We charted the median TTFB of WordPress sites hosted on one platform against the share of those installs on an out-of-date release. Bottom left are hosting providers that have faster sites that are up to date. Top right are hosts with slower sites and outdated WordPress installs.

Hostinger

2.7% on an old release · 189,465 · 359ms TTFB

0% 5% 10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75% 80% 85%
0 200 400 600 800 1000 1200 1400 1600 1800 2000 2200 2400
↑ Share on an out-of-date release Median time to first byte, ms →
Chart only includes hosts with at least 2,000 WordPress installs.

# 19,986 sites print a server error into their own homepage

When something breaks on the server a site can show a plain error page, or it can print the failure into the page it serves. The second kind names the software, the file paths and sometimes the database behind the site, which is the reconnaissance an attacker would otherwise have to do themselves.

Nearly all of it is one setting. PHP, Laravel, Django, Rails and ASP.NET all ship a debug mode that prints the failure to the browser, and all of them expect it to be off before the site goes live.

Download chart

A site can leak more than one kind of error, so the bars add up to more than the number of sites leaking.

PHP error output (display_errors on) 0.15% · 19,707 Database error (MySQL, PDO, Oracle, SQL Server) 0.00% · 227 Laravel Whoops/Ignition or Symfony debug page 0.00% · 40 ASP.NET / IIS server error page 0.00% · 22 WordPress "Error establishing a database connection" 0.00% · 12 Java / Spring / Tomcat exception page 0.00% · 5 Node / Express error or default 404 0.00% · 5 Perl / CGI "Software error" 0.00% · 3 ColdFusion error page 0.00% · 2 Python traceback or Django DEBUG page 0.00% · 1 Ruby on Rails exception page 0.00% · 1

# We detected a WAF on 40.1% of live sites

A web application firewall inspects requests before they reach the site and blocks the ones that look like attacks. Most of what we can see sits at the network edge, in front of the host, and the rest runs on the server itself as a plugin or a module.

Download chart

We don't tend to detect firewalls as our crawler tries to be polite and not break rules or make intrusive probes. The numbers here are an undercount of the true market share for this reason. Some vendors name themselves on normal requests and are shown here.

30.6% of live sites · 4,523,078

Edge / network Application / origin

08 SEO & Accessibility

Next · 09 Privacy

4,213,824 sites are accessible and include a skip link

# The least adopted SEO signal reaches 52.4% of sites. The least adopted accessibility signal reaches 34.2%.

Both groups are measured on the same sites and drawn on one scale, so a bar in either can be read against a bar in the other. The SEO signals are what a page declares about itself for a search engine. The accessibility signals are what it declares for assistive software.

SEO

Title tag 98.7% XML sitemap 80.3% Meta description 73.9% Schema.org 56.2% og:image 52.4%

Accessibility

HTML lang 92.8% Semantic HTML 90.1% Image alt text 73.9% Form labels 71.1% Skip nav link 34.2%

# A site running a CMS is up to 6.5 times more likely to include a skip link

Accessibility falls as traffic rises: the busiest sites score worse than the long tail. That is not effort, it is composition. Most of the head of the web is hand-built and most of the tail runs a CMS, and a skip link is something a theme provides rather than something an author writes.

On a CMS No CMS identified
Top 10k 29.3% 2.5× 11.7%
Top 100k 37.3% 4.4× 8.5%
Top 1M 43.8% 6.5× 6.7%
Top 10M 45.2% 5.7× 7.9%
A site counts as running a CMS where we identified one. Everything else, from a bespoke build to a platform we could not name, sits on the other side.

# Platforms are optimised for SEO and inconsistent about accessibility

We score every site we crawl across several quality metrics. Here those sites are mapped to the platform they run on, and accessibility and SEO are each scored out of 100.

For SEO we score meta description, canonical URL, robots.txt, XML sitemap, open graph tags and structured data markup. The accessibility score checks for an <h1> tag, a language attribute, pinch to zoom being enabled, a skip link and the use of semantic HTML.

Download chart

Platforms with at least 10,000 sites. The lines are the medians of the platforms plotted, top right is better than average.

WordPress.org

SEO 84 · accessibility 80 · 4,654,967

30 40 50 60 70 80 90 100
50 60 70 80 90 100
↑ Accessibility score SEO score →

7,144,858 sites run a tracker

# We were asked to accept cookies 3,139,028 times

A consent platform is the banner that asks whether a site may set cookies, and the record of what you answered. We detect 107 of them by name, from the plugins that dominate WordPress to the enterprise suites, plus the banners Wix, Squarespace and Shopify build into their own platforms.

CookieYes is the largest at 11.9% of the sites that show a banner, and everything below the top three is under 6%. 29.6% is a banner we detect by markup or styling, but is either custom coded, or unattributed to a vendor.

29.6% of sites with a banner · 929,719

Named platform Banner we could not attribute

# Two companies collect almost all of the web's advertising data

An advertising pixel is a few lines of code a site adds so an ad platform can watch what visitors do after they arrive. It reports the purchase, the sign-up, the page viewed, and ties it back to the ad that sent them. The site gets attribution and an audience it can advertise to again. The platform gets the behaviour of everyone who visits, on a site it does not own.

Meta's pixel is on 16.3% of sites and Google's conversion tag on 14.8%. Nothing else is close, and the two are rarely a choice between one or the other: 83% of the sites carrying Meta's pixel carry a Google tag as well.

16.3% · 2,009,113 14.8% · 1,821,180 1.6% · 191,558 1.6% · 190,954 1.3% · 162,665 0.5% · 63,539 0.4% · 52,178 0.3% · 36,768 0.2% · 30,124 0.2% · 25,882 0.2% · 18,517 0.1% · 16,632 0.1% · 13,671 0.1% · 6,542 0.0% · 270

# 58% of sites carry a tracking script (analytics, advertising, CRM or lead generation), and 47.9% carry Google Analytics

Analytics scripts tell site owners what pages are being viewed and where visitors have come from. Sometimes these can be privacy conscious and anonymise the data that is recorded or shared.

Analytics and tracking scripts can be loaded by tag managers like Google Tag Manager. 21.5% of sites use it, and when they do we take a look inside to see what scripts are loaded.

Analytics

Google Analytics 47.9% · 5,899,077 Microsoft Clarity 5.2% · 646,582 Yandex Metrica 3% · 364,946 Hotjar 1.9% · 234,647 Matomo 1.4% · 170,691 Cloudflare Web Analytics 0.3% · 40,554 Plausible Analytics 0.3% · 37,328 LiveInternet 0.3% · 36,641 VWO 0.1% · 18,342 Adobe Analytics 0.1% · 18,130

Tracking scripts on a site

No scripts 40.7% · 5,012,310 1 script 26.2% · 3,222,388 2 scripts 14.5% · 1,783,346 3 scripts 8.9% · 1,098,887 4 scripts 5.2% · 636,837 5 or more scripts 4.6% · 565,406

# Consent banners lead in Europe. Ad trackers do not follow the same pattern.

The 27 highest banner rates are all European countries. Italy is highest at 65.8%. Israel is 28th, the first country outside Europe. The bottom of the list is under 4%.

Germany, Austria, Switzerland and France are among the lowest on the ad tracker layer. Bulgaria, Hungary and Romania are among the highest, alongside Vietnam and Ukraine. EU countries range from 9.7% to 38.3% under the same law.

Map metric
—
—
—
Geographic location comes from the site's location schema (where defined) and the domain's TLD, excluding .com and some country domains like .co that have become trendy.

# 71.5% of sites load files or a service from Google

A site is counted as loading a Google service when its HTML asks the browser to fetch something from a Google host: a script, a stylesheet, a font file, an embedded frame.

Each request sends the visitor's IP address along with other data, but Google states it doesn't always use this data for advertising profiles, like with Google Fonts. Regardless, its reach across the corpus is impressive: 71.5% of sites touch Google in some form.

Google Analytics 46.1% · 5,683,037 Google Fonts 40.4% · 4,975,905 Google Tag Manager 21.5% · 2,646,246 Google Ads 14.6% · 1,803,925 reCAPTCHA 9.1% · 1,120,415 Maps (embed or API) 7.1% · 871,277 Hosted Libraries (jQuery etc) 6.3% · 770,605 YouTube embeds 5% · 621,798 AdSense 3.4% · 412,984 Google Cloud hosting 1.5% · 184,890 Translate widget 1.1% · 140,967 Sign-In 1% · 120,897 Ad Manager 0.4% · 43,635 Docs / Forms / Calendar embeds 0.4% · 46,535

2,499,925 sites publish an llms.txt

# 18.5% of sites publish an llms.txt file

An llms.txt file sits at the root of a site and lists the pages it wants an AI assistant to read. It was proposed in 2024 and has never been ratified by anyone. No major model provider has committed to acting on it, Google has confirmed that no Search system reads it, and crawlers do not request it in any meaningful volume.

55.2% of the files we found sit on platforms that switched one on for every customer, and Shopify alone accounts for 743,970. Where someone has to add it themselves, adoption collapses.

Auto-injected by the platform

Wix 99.8% Duda 99.8% Shopify 99.2%

Written by developers

Webflow 13.5% WordPress.org 13.1%

# 3.3% of sites block at least one AI crawler

Blocking rises with traffic. The two kinds of crawler are not blocked equally: bots that collect text to train models are disallowed around three times as often as bots that fetch a page in response to a question.

AI training crawlers Top 10k Top 100k Top 1M Top 10M
GPTBot 14.2%14% 9.1%9% 5.2%5% 2.1%2%
Bytespider 13.1%13% 8.6%9% 5.2%5% 2.1%2%
CCBot 13.7%14% 8.9%9% 5.1%5% 2%2%
Amazonbot 9.2%9% 7.3%7% 4.7%5% 1.9%2%
ClaudeBot 12%12% 8.1%8% 4.6%5% 1.7%2%
meta-externalagent 9.6%10% 7%7% 4.1%4% 1.7%2%
Google-Extended 9.9%10% 6.8%7% 3.9%4% 1.5%2%
Applebot-Extended 8.9%9% 6.4%6% 3.6%4% 1.4%1%
DeepSeekBot 4.7%5% 3.4%3% 2.3%2% 0.9%1%

On-demand search fetchers

ChatGPT-User 8%8% 5.6%6% 3.3%3% 1.1%1%
PerplexityBot 8.5%9% 5.6%6% 3.1%3% 1.1%1%
YouBot 7.8%8% 4.8%5% 2.7%3% 1%1%
OAI-SearchBot 6.1%6% 4.4%4% 2.6%3% 0.9%1%
DuckAssistBot 5.8%6% 3.8%4% 2.4%2% 0.9%1%
Claude-User 4.9%5% 3.6%4% 2.4%2% 0.9%1%
Claude-SearchBot 5%5% 3.8%4% 2.5%3% 0.9%1%

Rarely blocked → Often blocked

Percentages of that tier's sites disallowing that bot in robots.txt

# AI builders load slowest of any category we identify

You trade the speed of building the site for a heavy front end that takes longer to load. An AI builder sends a near-empty document and assembles the page in the browser afterwards: the median Lovable site sends 12KB of HTML, against 161KB for WordPress. Nothing appears until the JavaScript has run, and that wait is what Google's field data records. The two builders that hold up, Hostinger Horizons and v0 by Vercel, are the two that send a real page.

BuilderSitesLCP (loading)INP (interaction)CLS (stability)
Lovable84,098
36.3%
72%
86.4%
Base449,514
22.1%
72.4%
83.3%
Replit7,642
47.8%
72.6%
84.4%
v0 by Vercel4,884
67.1%
80.5%
92%
Manus3,911
24.3%
74.8%
86.2%
Emergent2,999
15.2%
66.8%
77%
Claude Design2,378
71.3%
88.5%
94.8%
GoDaddy Airo2,235
65.9%
93.1%
96.7%
ChatGPT Sites2,145
43.4%
89.1%
95.4%
Bubble1,898
28.3%
89%
69.8%
Bolt1,537
43.1%
79.2%
83.1%
Readdy1,094
33%
84.4%
89.5%
Durable560
65.8%
94.4%
93.8%

# A standard for refusing text and data mining exists, and 1,113 sites use it

The W3C's TDM Reservation Protocol lets a server say, in one header, that its content is reserved from text and data mining. 1,113 sites send it. Another 135 send the same header set to allow mining. Almost all of both are academic journals and university research portals.

11 The Invisible Web

1,868,802 sites failed to load or blocked us

# Higher-traffic domains are more likely to block our crawler

Top 10k 26.1% Top 100k 23.3% Top 1M 16.8% Top 10M 12.4%

# Cloudflare issued 44.0% of the blocks we hit

1,080,408 domains blocked our crawler from loading a page. Some blocks come from WAFs, some from hosting providers and some are a plain 403 Forbidden error which we can't attribute.

44.0% · 475,548 domains 27.3% · 295,081 domains 17.6% · 190,137 domains 20i 3.1% · 33,066 domains 1.3% · 14,165 domains 1.3% · 14,103 domains 1.3% · 13,828 domains Sucuri 0.8% · 8,952 domains 0.7% · 7,721 domains Cafe24 bot challenge 0.7% · 7,687 domains

# We can still identify who serves a blocked domain, usually not what CMS platform it runs on

We can still detect the CDN from the response headers, the nameserver from the DNS records, and the host from who owns the IP address. None of those needs the page. Detecting the platform usually does.

CDN detected 81.5% · 880,337 domains Hosting detected 55.7% · 602,173 domains Platform detected 12.9% · 139,419 domains

# 1.71% of the sites we visit are spam, and 0.17% declare themselves as adult content

The spam sites we detect share a common build signature: the same HTML, tracking scripts or asset hosts. They're custom builds and rarely run on a CMS platform we detect, but are on thousands of domains.

We detect adult sites when they declare an RTA label or a rating tag. CMS detection rates for them are also lower than on an average site.

Category Sites No platform detected
Any spam build Sites 214,029 No platform detected
97.2%
Gambling Sites 188,691 No platform detected
98.2%
Labels itself adult Sites 21,936 No platform detected
77.4%
AI content farm Sites 4,012 No platform detected
100%
Scam or cloaked payload Sites 714 No platform detected
100%