Name: WordPress HTML CDN delivery and the Core Web Vitals (October 2026) - The State of Web Vitals
Creator: Arjen Karel

WOWordPress Scoped to 63,295 sites out of 203,892 analyzed (cms) Compare with all sites →

86.1% of WordPress sites have no an HTML edge CDN. Of the 13.9% that do, 60% use Cloudflare as, and 72% of those sites have a good LCP, against 70% of all WordPress sites.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv

LCP pass rate

Sites with Cloudflare as an HTML edge CDN have a good LCP most often: 72%, against 70% of all WordPress sites. Sites with CloudFront as CDN have it least often, at 66%.

SitesGood, needs improvement, poor LCPMedian

All WordPress sites60,85570%1.9s

Netlify Edge <0.1%1080%1.8s

Cloudflare 8.4%5,16172%1.9s

Akamai 2.1%1,31372%1.9s

Direct from origin (no CDN) 86.1%52,28070%1.9s

Fastly 1.4%85267%2.1s

Amazon CloudFront 1.9%1,20166%2.1s

Vercel Edge 0.1%3866%2.3s

GoodNeeds improvementPoorSites: with Chrome field data

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv

An HTML edge CDN usage

13.9% of WordPress sites use an HTML edge CDN, and three in five of those use Cloudflare as.

All WordPress sites 63,295 sites

Direct from origin (no CDN) 86.1% An HTML edge CDN 13.9%

Sites with an HTML edge CDN 8,824 sites

Cloudflare 60.3% Akamai 15.3% Amazon CloudFront 13.9%

Cloudflare 60.3% Akamai 15.3% Amazon CloudFront 13.9% Fastly 9.9% Vercel Edge 0.4% Netlify Edge 0.1%

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv

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 Cloudflare as and no sits in time to first byte (TTFB): 1066 ms median for Cloudflare as against 1133 ms for no. Overall median field LCP is 1.9s for Cloudflare as (TTFB 1066 ms, load delay 336 ms, load duration 173 ms, render delay 249 ms) versus 1.9s for no.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP

All WordPress sites 43,6221127 ms340 ms235 ms340 mslab 340 ms1.9s

Fastly 6231251 ms321 ms266 ms321 mslab 321 ms2.1s

Akamai 9401062 ms321 ms254 ms321 mslab 321 ms1.9s

Cloudflare 3,7341066 ms336 ms249 ms336 mslab 336 ms1.9s

Direct from origin (no CDN) 37,3761133 ms341 ms233 ms341 mslab 341 ms1.9s

Amazon CloudFront 9111168 ms356 ms249 ms356 mslab 356 ms2.1s

Vercel Edge 301086 ms391 ms391 mslab 391 ms2.3s

TTFB Resource load delay Resource load time Element render delay

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv

An HTML edge CDN per framework

On jQuery, 86% of sites use no an HTML edge CDN, and 69% of jQuery sites have a good LCP, against 70% of all sites. On Vue, 87% of sites use no, and 68% of Vue sites have a good LCP.

FrameworkAn HTML edge CDN on its sitesGood LCP

All WordPress sites 63,295 sitesDirect from origin (no CDN) 86%70%

Alpine 380 sitesDirect from origin (no CDN) 78%Cloudflare 14%80%

jQuery 60,314 sitesDirect from origin (no CDN) 86%69%

Vue 4,844 sitesDirect from origin (no CDN) 87%68%

React 2,233 sitesDirect from origin (no CDN) 82%61%

Direct from origin (no CDN) Cloudflare Akamai Amazon CloudFront Fastly Vercel Edge Netlify Edge

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv

HTML edge CDN or the framework

Does the framework explain the an HTML edge CDN difference?

On jQuery, 71% of sites with Cloudflare as an HTML edge CDN have a good LCP, against 69% of jQuery sites with no. Within jQuery, sites with Cloudflare as have a good LCP more often. On Vue, 65% of sites with Cloudflare as an HTML edge CDN have a good LCP, against 67% of Vue sites with no. Within Vue, sites with Cloudflare as and no have a good LCP about equally 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 1066 ms and Fastly cuts it to 1251 ms, compared with 1133 ms for documents served directly from the origin.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 60,855 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv

Understanding HTML document CDN delivery

Put your WordPress domain behind an edge CDN and enable full-page HTML caching for anonymous visitors. Right now 86.1% of WordPress sites serve their HTML directly from the origin server (70% good LCP, 1133 ms median TTFB). Proxying HTML without caching only saves TLS handshake time; combining Cloudflare APO or Cache Rules with proper cache-bypass rules for logged-in users and WooCommerce carts serves the document straight from the edge.

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 · WordPress: 63,295 crawled sites · 60,855 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 · 63,295 crawled WordPress sites (60,855 with all devices Chrome field data, October 2026) · How we measured