Uncompressed text responses on Wix sites
60.1% of audited sites (3,378) ship at least one uncompressed text resource (93% good LCP, 1.2s median), trailing sites that compress every text response (39.9%, 96% good LCP, 1.1s median).
39.9% of Wix sites use full text compression text compression coverage, and 96% of those sites have a good LCP, against 94% of all Wix sites.
LCP pass rate
Sites with full text compression text compression coverage have a good LCP most often: 96%, against 94% of all Wix sites. Sites with uncompressed text responses text compression have it least often, at 93%.
Text compression coverage usage
Uncompressed text responses is the most used: 60.1% of Wix sites. Full text compression is 39.9% of Wix sites.
How leaking uncompressed text responses affects the four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between full text compression and uncompressed text responses sits in resource load delay: 408 ms median for full text compression against 475 ms for uncompressed text responses. Overall median field LCP is 1.1s for full text compression (TTFB 390 ms, load delay 408 ms, load duration 107 ms, render delay 150 ms) versus 1.2s for uncompressed text responses.
Text compression coverage per framework
On React, 60% of sites use uncompressed text responses text compression coverage, and 94% of React sites have a good LCP, against 94% of all sites.
React 5,620 sitesHas uncompressed text 60%All text compressed 40%94%Uncompressed text responses or the framework
Does the framework explain the text compression coverage difference?
On React, 96% of sites with full text compression text compression coverage have a good LCP, against 93% of React sites with uncompressed text responses. Within React, 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 2,243 sites (39.9%) that compress every text response, good LCP reaches 96% (1.1s median, 390 ms TTFB), whereas the 3,378 sites (60.1%) shipping at least one uncompressed text payload drop to 93% good LCP (1.2s median, 413 ms TTFB).
Understanding uncompressed text responses
Enable Brotli or gzip across every compressible MIME type on both your origin server and CDN edge: text/html, text/css, application/javascript, application/json, image/svg+xml, and font/ttf. Text resources shrink by 70% to 85% when compressed; leaving a render-blocking stylesheet, SVG hero, or hydration JSON payload uncompressed multiplies wire transfer time on mobile networks. Across the dataset, 39.9% of sites compress all text responses (96% good LCP, 1.1s median) while 60.1% ship at least one uncompressed text file (93% good LCP, 1.2s median).
By Arjen Karel · 5,621 crawled Wix sites (3,077 with phone Chrome field data, October 2026). How we measured.