WordPress HTML compression (Brotli vs Gzip) and the Core Web Vitals

Brotli (br), Gzip, Zstandard (zstd), or uncompressed HTML: how document compression affects Time to First Byte (892 ms on Brotli vs 1071 ms on Gzip) and Largest Contentful Paint.

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

One in ten WordPress sites, 12.3%, have no HTML compression. Of the 87.7% that do, 36% use Brotli, and 80% of those sites have a good LCP, against 76% of all WordPress sites.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field data · 63,291 sites with HTML compressionBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with Brotli HTML compression have a good LCP most often: 80%, against 76% of all WordPress sites. Sites with Zstandard HTML compression have it least often, at 72%.

SitesGood, needs improvement, poor LCPMedian
All WordPress sites17,00576%1.7s
Brotli (br) 31.4%5,45180%1.7s
Gzip 50.2%8,13975%1.8s
Uncompressed (none) 12.3%1,91274%1.8s
Zstandard (zstd) 6.1%1,50372%1.9s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field data · 63,291 sites with HTML compressionBy Arjen Karel · corewebvitals.io/state-of-cwv
2

HTML compression usage

Nine in ten WordPress sites uses HTML compression, and 57% of those use Gzip. Brotli is 36% of the sites with HTML compression, 31.4% of all WordPress sites.

WordPress sites with HTML compression 63,291 sites
Uncompressed (none) 12.3% HTML compression 87.7%
Sites with HTML compression 55,499 sites
Gzip 57.2% Brotli (br) 35.8%
Gzip 57.2% Brotli (br) 35.8% Zstandard (zstd) 6.9%
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field data · 63,291 sites with HTML compressionBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Where HTML compression shows up in the four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between Brotli and no sits in time to first byte (TTFB): 892 ms median for Brotli against 992 ms for no. Overall median field LCP is 1.7s for Brotli (TTFB 892 ms, load delay 294 ms, load duration 136 ms, render delay 219 ms) versus 1.8s for no.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
WordPress sites with HTML compression 11,805999 ms289 ms219 ms289 mslab 330 ms1.8s
Gzip 5,5651071 ms271 ms219 ms271 mslab 317 ms1.8s
Zstandard (zstd) 1,0961082 ms290 ms242 ms290 mslab 311 ms1.9s
Brotli (br) 3,805892 ms294 ms219 ms294 mslab 328 ms1.7s
Uncompressed (none) 1,339992 ms356 ms199 ms356 mslab 426 ms1.8s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field data · 63,291 sites with HTML compressionBy Arjen Karel · corewebvitals.io/state-of-cwv
4

HTML compression per framework

On jQuery, 51% of sites use Gzip HTML compression, and 75% of jQuery sites have a good LCP, against 76% of all sites. On Vue, 56% of sites use Gzip, and 75% of Vue sites have a good LCP.

FrameworkHTML compression on its sitesGood LCP
WordPress sites with HTML compression 63,291 sitesGzip 50%Brotli (br) 31%Uncompressed (none) 12%76%
Alpine 380 sitesBrotli (br) 40%Gzip 38%Zstandard (zstd) 13%82%
jQuery 60,314 sitesGzip 51%Brotli (br) 31%Uncompressed (none) 12%75%
Vue 4,844 sitesGzip 56%Brotli (br) 28%Uncompressed (none) 13%75%
React 2,233 sitesGzip 48%Brotli (br) 35%66%
Gzip Brotli (br) Uncompressed (none) Zstandard (zstd)
The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field data · 63,291 sites with HTML compressionBy Arjen Karel · corewebvitals.io/state-of-cwv
5

HTML compression or the framework

Does the framework explain the HTML compression difference?

On jQuery, 74% of sites with Gzip HTML compression have a good LCP, against 73% of jQuery sites without HTML compression. Within jQuery, sites with and without HTML compression have a good LCP about equally often.

Why Brotli HTML compression speeds up resource discovery

Brotli uses a built-in dictionary of common HTML, CSS, and JavaScript tokens, shrinking HTML documents 15 to 20 percent more than Gzip at comparable CPU cost. Because the browser's preload scanner parses the HTML stream chunk by chunk as it arrives, a smaller compressed document delivers the <head> and hero <img> markup in fewer TCP or QUIC packets. Sites serving Brotli HTML record a 892 ms median TTFB and 1.7s median LCP, compared with 1071 ms TTFB and 1.8s LCP on Gzip.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field data · 63,291 sites with HTML compressionBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding HTML document compression

Enable Brotli (br) compression at your web server (Nginx, LiteSpeed, Caddy) or edge CDN. 50.2% of WordPress sites still compress HTML with legacy Gzip (75% good LCP, 1.8s median LCP) and 12.3% send uncompressed HTML (74% good LCP). WordPress sites serving Brotli HTML reach 80% good LCP and a 1.7s median LCP.

The State of Web Vitals · October 2026 · WordPress: 63,295 crawled sites · 17,005 with desktop field data · 63,291 sites with HTML compressionBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals HTTP protocol mix → Connection hints → Cache strategy mix → Uncompressed text responses → By Arjen Karel · 63,295 crawled WordPress sites (17,005 with desktop Chrome field data, 63,291 sites with HTML compression, October 2026) · How we measured