The State of Web Vitals

HTML document CDN on Wix sites

Direct from origin versus Cloudflare, Fastly, CloudFront, or Akamai: how serving the main HTML document through an edge CDN changes Time to First Byte (305 ms on Cloudflare vs 514 ms from origin) and Largest Contentful Paint.

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 →

One in four Wix sites, 27.1%, have no an HTML edge CDN. Of the 72.9% that do, 81% use Fastly as, and 95% 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 data · 5,619 sites with an HTML edge CDNBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with Fastly as an HTML edge CDN have a good LCP most often: 95%, against 92% of all Wix sites.

SitesGood, needs improvement, poor LCPMedian
All Wix sites72892%1.2s
Akamai 0.1%1100%863ms
Cloudflare 5.0%4696%1.2s
Fastly 59.2%39095%1.1s
Amazon CloudFront 8.7%8994%1.2s
Direct from origin (no CDN) 27.1%20285%1.3s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,619 sites with an HTML edge CDNBy Arjen Karel · corewebvitals.io/state-of-cwv
2

An HTML edge CDN usage

Three in four Wix sites uses an HTML edge CDN, and four in five of those use Fastly as.

Wix sites with an HTML edge CDN 5,619 sites
Direct from origin (no CDN) 27.1% An HTML edge CDN 72.9%
Sites with an HTML edge CDN 4,098 sites
Fastly 81.1% Amazon CloudFront 11.9%
Fastly 81.1% Amazon CloudFront 11.9% Cloudflare 6.8% Akamai 0.2%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,619 sites with an HTML edge CDNBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Where an HTML CDN saves time: TTFB and the four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between Fastly as and no sits in time to first byte (TTFB): 305 ms median for Fastly as against 514 ms for no. Overall median field LCP is 1.2s for Fastly as (TTFB 305 ms, load delay 469 ms, load duration 261 ms, render delay 132 ms) versus 1.3s for no.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Wix sites with an HTML edge CDN 376343 ms478 ms259 ms478 mslab 462 ms1.2s
Fastly 201305 ms469 ms261 ms469 mslab 446 ms1.2s
Direct from origin (no CDN) 107514 ms496 ms254 ms496 mslab 469 ms1.3s
Amazon CloudFront 45349 ms513 ms276 ms513 mslab 506 ms1.2s
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 data · 5,619 sites with an HTML edge CDNBy Arjen Karel · corewebvitals.io/state-of-cwv
4

An HTML edge CDN per framework

React sets the an HTML edge CDN to Fastly as on 59% of its sites, and 92% of React sites have a good LCP, against 92% of all sites.

FrameworkAn HTML edge CDN on its sitesGood LCP
Wix sites with an HTML edge CDN 5,619 sitesFastly 59%Direct from origin (no CDN) 27%92%
React 5,620 sitesFastly 59%Direct from origin (no CDN) 27%92%
Fastly Direct from origin (no CDN) Amazon CloudFront Cloudflare Akamai
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,619 sites with an HTML edge CDNBy Arjen Karel · corewebvitals.io/state-of-cwv
5

HTML edge CDN or the framework

Does the framework explain the an HTML edge CDN difference?

On React, 95% of sites with Fastly as an HTML edge CDN have a good LCP, against 85% of React sites with no. Within React, sites with Fastly as have a good LCP more often.

Why putting the HTML document on an edge CDN cuts TTFB

Static assets like images and scripts are easy to put on a CDN, but the browser cannot discover any of them until the main HTML document arrives. Routing the main domain through an edge network terminates DNS, TCP, and TLS at a point of presence near the visitor, and full-page HTML caching at the edge removes the origin server round trip entirely. In Chrome's field data, serving HTML through Cloudflare cuts median TTFB to 305 ms and Fastly cuts it to 305 ms, compared with 514 ms for documents served directly from the origin.

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

Understanding HTML document CDN delivery

Serve the main HTML document through an edge CDN and cache anonymous page views at the edge wherever possible. Across the dataset, 27.1% of sites still serve HTML directly from an origin server (85% good LCP, 514 ms median TTFB), while sites on Cloudflare (96% good LCP, 305 ms TTFB) and Fastly (95% good LCP, 305 ms TTFB) start rendering significantly earlier. Even when HTML cannot be cached publicly, edge TLS termination, HTTP/3 support, and tiered origin routing cut connection latency on every navigation.

Go fix it Configure Cloudflare for passing the Core Web Vitals → Time to First Byte → Free website cache warmer →
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field data · 5,619 sites with an HTML edge CDNBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals ETag present → Requests via CDN → HTTP protocol mix → HTTP protocol → By Arjen Karel · 5,621 crawled Wix sites (728 with desktop Chrome field data, 5,619 sites with an HTML edge CDN, October 2026) · How we measured