The State of Web Vitals

Subresource CDN providers on Wix sites

Across audited sites, 100.0% (5,621) fetch requests from unfronted origin or custom hosts (92% good LCP), while 22.8% load assets via Cloudflare (88% good LCP), 99.9% via Amazon CloudFront (92% good LCP), and 99.9% via Fastly (92% good LCP, 1.2s median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · Desktop field outcomes · Wix sites only
Wix Scoped to 5,623 sites out of 203,892 analyzed (cms) Compare with all sites →

100.0% of Wix sites use origin/custom hosts subresource CDN distribution, and 92% of those sites have a good LCP, against 92% of all Wix sites.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with origin/custom hosts subresource CDN distribution have a good LCP most often: 92%, against 92% of all Wix sites. Sites with Cloudflare subresource CDNs have it least often, at 88%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites72892%1.2s
Direct origin / custom host 100.0%72892%1.2s
Fastly CDN 99.9%72892%1.2s
Amazon CloudFront 99.9%72892%1.2s
Cloudflare CDN 22.8%21288%1.3s
Vercel Edge Network 0.5%786%1.5s
Akamai CDN 0.7%1385%1.3s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Subresource CDN distribution usage

Origin/custom hosts is the most used: 100.0% of Wix sites.

Sites using each option (sites can use more than one) 5,621 sites
Direct origin / custom host 100.0% Fastly CDN 99.9% Amazon CloudFront 99.9%
Direct origin / custom host 100.0% Fastly CDN 99.9% Amazon CloudFront 99.9% Cloudflare CDN 22.8% Akamai CDN 0.7% Vercel Edge Network 0.5%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

LCP phase breakdown by CDN serving page subresources

Across the four LCP sub-parts in Chrome's field data, the largest gap between origin/custom hosts and Cloudflare sits in time to first byte (TTFB): 343 ms median for origin/custom hosts against 501 ms for Cloudflare. Overall median field LCP is 1.2s for origin/custom hosts (TTFB 343 ms, load delay 478 ms, load duration 259 ms, render delay 137 ms) versus 1.3s for Cloudflare.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All Wix sites 376343 ms478 ms259 ms478 mslab 462 ms1.2s
Amazon CloudFront 376343 ms478 ms259 ms478 mslab 462 ms1.2s
Fastly CDN 376343 ms478 ms259 ms478 mslab 462 ms1.2s
Direct origin / custom host 376343 ms478 ms259 ms478 mslab 462 ms1.2s
Cloudflare CDN 117501 ms496 ms257 ms496 mslab 485 ms1.3s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Subresource CDN distribution per framework

React sets the subresource CDN distribution to origin/custom hosts on 100% of its sites, and 92% of React sites have a good LCP, against 92% of all sites.

FrameworkSubresource CDN distribution on its sitesGood LCP
All Wix sites 5,621 sitesDirect origin / custom host 100%Fastly CDN 100%Amazon CloudFront 100%Cloudflare CDN 23%92%
React 5,620 sitesDirect origin / custom host 100%Fastly CDN 100%Amazon CloudFront 100%Cloudflare CDN 23%92%
Direct origin / custom host Fastly CDN Amazon CloudFront Cloudflare CDN Akamai CDN Vercel Edge Network
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Subresource CDN or the framework

Does the framework explain the subresource CDN distribution difference?

Almost every site with origin/custom hosts subresource CDN distribution is a React site, and almost every React site has origin/custom hosts subresource CDN distribution, so the data can't tell origin/custom hosts subresource CDN distribution and React apart.

Which CDN edges actually serve the images, scripts, and fonts on a page

Even when a site's main HTML document is served directly from an origin server, its subresources (images, scripts, fonts, third-party libraries) frequently traverse global CDNs. Across all audited sites, 22.8% (1,280) load subresources from Cloudflare (88% good LCP, 1.3s median), 99.9% (5,615) from Amazon CloudFront (92% good LCP), 99.9% (5,620) from Fastly (92% good LCP, 1.2s median), and 0.7% (37) from Akamai (85% good LCP).

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding subresource CDN providers

Serve static subresources (especially the LCP hero image, critical CSS, and web fonts) from the same edge CDN fronting your HTML document so requests coalesce over a single HTTP/2 or HTTP/3 connection. Across all audited sites, 22.8% fetch subresources from Cloudflare (88% good LCP) and 99.9% from Fastly (92% good LCP).

Go fix it Configure Cloudflare for passing the Core Web Vitals → Time to First Byte →
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Last-Modified present → Uncompressed text responses → Cacheable responses → HTML size (kB) → By Arjen Karel · 5,621 crawled Wix sites (728 with desktop Chrome field data, October 2026) · How we measured