Skip to main content
Optimize Website is a single-page tool that flips Apache’s mod_deflate compression on or off for your account. When on, Apache gzips text-based responses (HTML, CSS, JS, JSON) before sending them, which usually shaves 60–70% off transfer size.
Think twice before changing this. Every modern web stack expects compression to be on, and most Noxity sites already have it on by default. Turning it off makes pages slower for visitors. Turning it on for content types that don’t benefit (already-compressed images, video) wastes CPU. The wrong toggle here can also conflict with caching layers, AccelerateWP, or your CDN’s own compression, leaving you with double-compressed broken responses.
Optimize Website with compression toggle

cPanel home → Software → Optimize Website

​
The three options

​
When the default is correct

If you’re a typical WordPress, Joomla, Laravel, or static-site account: Compress all content is what you want, and it’s likely already set. Don’t toggle.

​
When to consider changing it

  • You’re running AccelerateWP. AccelerateWP handles compression itself. Leaving Apache compression on is fine but redundant. Don’t disable Apache compression to “let AccelerateWP do it” without testing. Many AccelerateWP setups still rely on Apache as a fallback.
  • Your CDN compresses upstream. Cloudflare, BunnyCDN, etc., compress on their edge. Some hosts disable origin compression to reduce CPU. Test before changing. If a connection bypasses the CDN, the visitor gets the uncompressed origin response.
  • You’re serving large pre-compressed assets. If your build pipeline outputs .js.gz files alongside .js, double-compression by Apache wastes CPU. The “compress specified MIME types” option lets you exclude application/octet-stream etc.

​
When to leave it alone

  • You don’t know what gzip is. The default is right for you.
  • The site works. Don’t tinker.
  • Your last performance test came back fine.
Compression is largely commodity now. The bigger speed wins for most sites are caching, CDN, and image optimization, not toggling this setting.

​
Common issues

Either compression is being applied to a content type that doesn’t survive it, or two layers are double-compressing. Set Optimize Website to Disabled as a quick test. If pages render correctly, find which other layer is also compressing (CDN, caching plugin, custom .htaccess rule) and pick one.
AccelerateWP enables gzip in its own way. If both are enabled, the response can be doubly compressed in some setups. Try disabling Optimize Website and see if PageSpeed recovers. See the AccelerateWP overview for context.
Check the response headers in your browser DevTools. Content-Encoding: gzip means it’s working. If absent, either compression is off, the response is too small to compress (Apache skips bodies under ~1 KB), or the request didn’t ask for it (clients send Accept-Encoding: gzip to request it).

​
Need a hand?

Open a ticket

Best for anything that needs an account check or a config change on our end.

Live chat

Faster for quick questions during business hours.