Gzip compression reduces the size of files your web server sends to visitors before they travel across the network. When a browser requests a CSS file, JavaScript file, or HTML page, the server can compress it with Gzip before sending, and the browser decompresses it on arrival. The transfer is smaller, which means it arrives faster. For text-based web assets, Gzip typically reduces file size by 60% to 80%.
WP Engine enables Gzip compression by default on all plans. No configuration is required. But understanding what it does and how to verify it is working helps you interpret PageSpeed Insights recommendations and audit your site’s performance accurately.
What Gzip Compression Does
Gzip uses the DEFLATE compression algorithm to find and reduce repetitive patterns in text files. HTML, CSS, and JavaScript files are highly repetitive by nature: CSS files repeat property names and values; JavaScript files repeat variable names and function calls; HTML files repeat tag structures. Gzip identifies these repetitions and replaces them with shorter representations, dramatically reducing file size.
| File type | Typical uncompressed | After Gzip | Reduction |
| HTML page | 80KB | 22KB | ~73% |
| CSS stylesheet | 120KB | 30KB | ~75% |
| JavaScript file | 200KB | 60KB | ~70% |
| JSON / XML | 50KB | 10KB | ~80% |
Gzip does not help with images, video, or binary files. These are already compressed by their own formats (JPEG, WebP, MP4). Applying Gzip to already-compressed files adds no benefit and may slightly increase file size.
Gzip vs Brotli: The Modern Alternative
Brotli is a newer compression algorithm developed by Google that typically achieves 15% to 25% better compression ratios than Gzip on text files. All major browsers support Brotli. When a browser sends an HTTP request, it tells the server which compression formats it accepts via the Accept-Encoding header. If the server supports Brotli, it uses it; otherwise it falls back to Gzip.
WP Engine supports Brotli compression through its Cloudflare CDN integration. Assets served from the CDN edge are compressed with Brotli where the browser supports it, with Gzip as the fallback. Origin server responses use Gzip by default. In practice, the combination means most visitors receive the best available compression for their browser without any configuration.
How to Verify Gzip Is Enabled on Your WordPress Site
Several methods confirm Gzip compression is active.
Google PageSpeed Insights. If Gzip is not enabled, PageSpeed Insights flags it as an opportunity under Enable text compression. If no such recommendation appears, compression is working.
GiftOfSpeed.com/gzip-test. Enter your URL and the tool checks whether the server is sending compressed responses and shows the compression ratio.
Chrome DevTools. Open DevTools and go to the Network tab. Load your page and click on a CSS or JavaScript file in the request list. Look at the Response Headers section. If you see Content-Encoding: gzip or Content-Encoding: br, compression is active for that file.
On WP Engine, Gzip is enabled at the server level by default. If a test shows compression is not active, the most likely cause is a plugin or .htaccess rule that is interfering with the server’s compression headers. Contact WP Engine support to investigate.
Does Gzip Compression Affect Server Performance?
Gzip compression adds a small amount of CPU overhead to compress files before sending. On modern server hardware, this overhead is negligible for text files. The bandwidth savings from compression typically outweigh the CPU cost significantly, particularly for visitors on slower connections where transfer time is the bottleneck rather than server processing time.
Compression works best in combination with caching. When a page is cached and served from the cache, the compressed version can be stored and served directly without re-compressing on each request. WP Engine’s EverCache stores and serves compressed cached responses, eliminating even the small per-request compression overhead for cached pages. For more on how caching and performance layers interact, see WordPress Caching Explained.
Frequently Asked Questions
Does WP Engine enable Gzip automatically?
Yes. Gzip compression is enabled by default across all WP Engine plans at the server level. You do not need to configure it, add a plugin, or modify .htaccess. Brotli compression is additionally available for assets served through the Cloudflare CDN edge nodes.
Should I install a Gzip compression plugin on WP Engine?
No. WP Engine handles Gzip at the server level. Installing a plugin to enable Gzip on WP Engine is redundant and adds unnecessary overhead. Plugins like WP Rocket or W3 Total Cache have Gzip settings that should be left disabled on WP Engine since the server-level compression is already active and more efficient.
Why does PageSpeed Insights still recommend enabling text compression on my WP Engine site?
This can happen when a caching plugin or custom code is returning responses that bypass the server’s compression headers, or when a specific resource type is being excluded from compression by a plugin rule. It can also occur when testing a URL that returns a redirect rather than a compressed response. Check the specific resources PageSpeed flags and verify their Content-Encoding headers in DevTools or contact WP Engine support.
