Guides › WordPress › Site down or error screens

ERR_CONTENT_DECODING_FAILED on a WordPress Site

The browser received compressed content it could not read, usually due to double compression or a PHP output problem.

Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
Site down or error page

ERR_CONTENT_DECODING_FAILED means the browser got a compressed page it could not unpack. The page is usually compressed twice, or compressed and then altered.

1Check compression layers2Disable plugin compression3Check PHP4Check .htaccess5Check the CDN6Look for output before headers7TestFixed? Test the site. If not, get help.
The steps in order. Work down the list and stop when the problem is solved.

Step 1: Check compression layers

Illustration for Step 1: Check compression layers

Compression can be applied by the server, a caching plugin, PHP and a CDN. Two at once is the typical cause.

Step 2: Disable plugin compression

Illustration for Step 2: Disable plugin compression

In your cache plugin switch off GZIP compression, then clear caches.

Step 3: Check PHP

Illustration for Step 3: Check PHP

If zlib.output_compression is on in PHP settings and your server also compresses, turn one off.

Step 4: Check .htaccess

Illustration for Step 4: Check .htaccess

Remove duplicate mod_deflate blocks.

Step 5: Check the CDN

Illustration for Step 5: Check the CDN

In Cloudflare or another CDN purge the cache and review compression settings.

Step 6: Look for output before headers

Illustration for Step 6: Look for output before headers

Blank lines or spaces before <?php in wp-config.php or a plugin can corrupt output.

Step 7: Test

Illustration for Step 7: Test

Use a private window and see if the error is gone.

Still stuck?

If these steps do not solve it, we fix it for you for a flat $99. Full refund if we do not solve it within 7 days.

Related guides

Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.

Last updated 2026-11-22.