Some scripts and stylesheets are served without gzip or Brotli compression, increasing load times and bandwidth usage.
By Seoxpert Editorial · Published
Uncompressed HTML, CSS, and JS files are much larger, causing slower page loads and higher data usage for users. This negatively affects Core Web Vitals like LCP and TBT, potentially lowering search rankings and user satisfaction.
Leaving this unresolved results in slower site performance and possible SEO penalties due to poor Core Web Vitals.
Automated crawlers request text resources with 'Accept-Encoding: gzip, br' and check for the 'Content-Encoding' header in the response.
Nginx: Enable gzip compression for text resources
gzip on;
gzip_types text/css application/javascript application/json;Test compression with curl
curl -H "Accept-Encoding: gzip, br" -I https://example.com/script.js
# Look for 'Content-Encoding: gzip' or 'Content-Encoding: br' in the response headers.Use curl or browser dev tools to check for the 'Content-Encoding' header in resource responses.
A custom server config or misconfigured origin may override the CDN's default compression settings.
Yes, enable both. Brotli is preferred by modern browsers, but gzip ensures compatibility with older clients.
Compression is most effective for text-based files like HTML, CSS, and JS. Images and binaries are usually already compressed.
Run a scan to see if Text Resources Served Without Compression (gzip / br) affects your pages.
Scan my website →