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 (358 ms on Cloudflare vs 471 ms from origin) and Largest Contentful Paint.

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices 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 96% of those sites have a good LCP, against 94% of all Wix sites.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy 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: 96%, against 94% of all Wix sites. Sites with CloudFront as CDN have it least often, at 89%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites5,33394%1.2s
Akamai 0.1%7100%1.2s
Netlify Edge <0.1%1100%920ms
Fastly 59.1%3,14696%1.1s
Cloudflare 5.0%26095%1.1s
Direct from origin (no CDN) 27.1%1,45292%1.3s
Amazon CloudFront 8.7%46689%1.3s
Vercel Edge <0.1%10%2.8s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy 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.

All Wix sites 5,621 sites
Direct from origin (no CDN) 27.1% An HTML edge CDN 72.9%
Sites with an HTML edge CDN 4,100 sites
Fastly 81.1% Amazon CloudFront 11.9%
Fastly 81.1% Amazon CloudFront 11.9% Cloudflare 6.8% Akamai 0.2% Netlify Edge <0.1% Vercel Edge <0.1%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy 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): 405 ms median for Fastly as against 471 ms for no. Overall median field LCP is 1.1s for Fastly as (TTFB 405 ms, load delay 450 ms, load duration 135 ms, render delay 152 ms) versus 1.3s for no.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All Wix sites 3,945419 ms455 ms137 ms151 ms455 mslab 455 ms1.2s
Fastly 2,338405 ms450 ms152 ms450 mslab 450 ms1.1s
Direct from origin (no CDN) 1,062471 ms453 ms150 ms453 mslab 453 ms1.3s
Cloudflare 193358 ms462 ms141 ms149 ms462 mslab 462 ms1.1s
Amazon CloudFront 347447 ms499 ms151 ms149 ms499 mslab 499 ms1.3s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy 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 94% of React sites have a good LCP, against 94% of all sites.

FrameworkAn HTML edge CDN on its sitesGood LCP
All Wix sites 5,621 sitesFastly 59%Direct from origin (no CDN) 27%94%
React 5,620 sitesFastly 59%Direct from origin (no CDN) 27%94%
Fastly Direct from origin (no CDN) Amazon CloudFront Cloudflare Akamai Netlify Edge Vercel Edge
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy 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, 96% of sites with Fastly as an HTML edge CDN have a good LCP, against 92% of React sites without an HTML edge CDN. Within React, sites with Fastly as an HTML edge CDN 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 358 ms and Fastly cuts it to 405 ms, compared with 471 ms for documents served directly from the origin.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy 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 (92% good LCP, 471 ms median TTFB), while sites on Cloudflare (95% good LCP, 358 ms TTFB) and Fastly (96% good LCP, 405 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 · 5,333 with all devices field dataBy 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 (5,333 with all devices Chrome field data, October 2026) · How we measured