WordPress uncompressed text responses and the Core Web Vitals

Sites with full text compression text compression coverage have a good LCP most often: 73%, against 70% of all WordPress sites. Sites with uncompressed text responses text compression have it least often, at 65%.

Full text compression is the most used: 67.1% of WordPress sites.

Across the four LCP sub-parts in Chrome's field data, the largest gap between full text compression and uncompressed text responses sits in time to first byte (TTFB): 1088 ms median for full text compression against 1211 ms for uncompressed text responses. Overall median field LCP is 1.9s for full text compression (TTFB 1088 ms, load delay 323 ms, load duration 168 ms, render delay 236 ms) versus 2.1s for uncompressed text responses.

jQuery sets the text compression coverage to full text compression on 67% of its sites, and 69% of jQuery sites have a good LCP, against 70% of all sites.

FrameworkText compression coverage on its sitesGood LCP

All WordPress sites 63,295 sitesAll text compressed 67%Has uncompressed text 33%70%

Alpine 380 sitesAll text compressed 55%Has uncompressed text 45%80%

jQuery 60,314 sitesAll text compressed 67%Has uncompressed text 33%69%

Vue 4,844 sitesAll text compressed 63%Has uncompressed text 37%68%

React 2,233 sitesAll text compressed 59%Has uncompressed text 41%61%

All text compressed Has uncompressed text

Does the framework explain the text compression coverage difference?

On jQuery, 72% of sites with full text compression text compression coverage have a good LCP, against 64% of jQuery sites with uncompressed text responses. Within jQuery, sites with full text compression have a good LCP more often. On Vue, 72% of sites with full text compression text compression coverage have a good LCP, against 60% of Vue sites with uncompressed text responses. Within Vue, sites with full text compression have a good LCP more often.

Where uncompressed text responses slip through on modern web stacks

Almost no server intentionally disables compression globally. Instead, uncompressed text responses slip through narrow MIME-type allowlists (forgetting image/svg+xml or application/json in nginx or Apache) or come from third-party API and widget endpoints that bypass the primary CDN. Across 42,465 sites (67.1%) that compress every text response, good LCP reaches 73% (1.9s median, 1088 ms TTFB), whereas the 20,830 sites (32.9%) shipping at least one uncompressed text payload drop to 65% good LCP (2.1s median, 1211 ms TTFB).