Shopify uncompressed text responses and the Core Web Vitals
68.7% of audited sites (5,666) ship at least one uncompressed text resource (95% good LCP, 1.4s median), trailing sites that compress every text response (31.3%, 98% good LCP, 1.2s median).
31.3% of Shopify sites use full text compression text compression coverage, and 98% of those sites have a good LCP, against 96% of all Shopify sites.
LCP pass rate
Sites with full text compression text compression coverage have a good LCP most often: 98%, against 96% of all Shopify sites. Sites with uncompressed text responses text compression have it least often, at 95%.
Text compression coverage usage
Uncompressed text responses is the most used: 68.7% of Shopify sites. Full text compression is 31.3% of Shopify 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: 536 ms median for full text compression against 609 ms for uncompressed text responses. Overall median field LCP is 1.2s for full text compression (TTFB 365 ms, load delay 536 ms, load duration 214 ms, render delay 254 ms) versus 1.4s for uncompressed text responses.
Text compression coverage per framework
On jQuery, 74% of sites use uncompressed text responses text compression coverage, and 94% of jQuery sites have a good LCP, against 96% of all sites. On Vue, 76% of sites use uncompressed text responses, and 95% of Vue sites have a good LCP.
Uncompressed text responses or the framework
Does the framework explain the text compression coverage difference?
On jQuery, 96% of sites with full text compression text compression coverage have a good LCP, against 93% of jQuery sites with uncompressed text responses. Within jQuery, sites with full text compression have a good LCP more often. On Vue, 98% of sites with full text compression text compression coverage have a good LCP, against 94% of Vue sites with uncompressed text responses. Within Vue, sites with full text compression and uncompressed text responses have a good LCP about equally 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,580 sites (31.3%) that compress every text response, good LCP reaches 98% (1.2s median, 365 ms TTFB), whereas the 5,666 sites (68.7%) shipping at least one uncompressed text payload drop to 95% good LCP (1.4s median, 400 ms TTFB).
Understanding uncompressed text responses
Audit third-party storefront apps and custom endpoints for missing Content-Encoding headers. While Shopify's Cloudflare edge compresses all first-party Liquid HTML, CSS, and JS with Brotli, 68.7% of Shopify stores load at least one uncompressed text response from an external app or secondary endpoint (95% good LCP, 1.4s median vs 98% and 1.2s on fully compressed stores).
By Arjen Karel · 8,246 crawled Shopify sites (8,062 with all devices Chrome field data, October 2026). How we measured.