Web & Performance

Gzip Compression Disabled

When gzip or brotli compression is disabled, the server sends uncompressed HTML, CSS, JavaScript, and other text-based resources to browsers. This wastes bandwidth and increases load times, especially for users on slower connections. Compression typically reduces file sizes by 60–80% with negligible CPU overhead on modern servers.

Symptoms

  • PageSpeed tools flagging "Enable text compression"
  • Large Content-Length values for text resources in network tab
  • Missing Content-Encoding: gzip header in server responses
  • Slow page loads despite fast TTFB

Common Causes

  • Compression not configured in the web server (Apache, nginx)
  • CDN or reverse proxy not compressing responses
  • Compression module not loaded/enabled
  • Compression excluded for certain content types
  • Backend application not setting proper Content-Type for compression

Step-by-Step Troubleshooting

  1. 1

    Check gzip status

    Test if gzip compression is enabled for your website.

    Use HTTP Headers →
  2. 2

    Check HTTP headers

    Look for Content-Encoding header in the server response.

    Use HTTP Headers →
  3. 3

    Run speed test

    Measure the impact on page load performance.

    Use Website Speed Test →
  4. 4

    Enable compression on server

    Configure gzip/brotli in your web server: mod_deflate for Apache, gzip on for nginx.

  5. 5

    Verify compression works

    Re-test to confirm Content-Encoding: gzip is present in responses.

    Use HTTP Headers →

Recommended Diagnostic Tools

HTTP HeadersHTTP HeadersWebsite Speed Test

Monitor Compression

Track server compression configuration and performance.

Related Problems

Frequently Asked Questions