Gzip, Brotli, and Browser Cache Setup
This section explains the server side clearly.
FastMe can help at the WordPress level, but compression is often strongest when configured at the web server or CDN layer.
Pages in this section
Open a dedicated guide for each topic
Recommended Compression Setup
For the best performance results, compression should typically be handled at one primary layer of your website stack.
Apache Example
If your server uses Apache and compression is not already enabled, a server admin can review a standard setup like this:
Nginx Example
If you do not control Nginx directly, send the above examples to the host and ask them to apply equivalent server-side rules.
How to Check Whether Gzip or Brotli Is Actually Working
You can verify whether Gzip or Brotli compression is working by checking the response headers returned by your website. Compression is commonly handled by the server, CDN, reverse proxy, or optimization layer depending on the hosting environment.
If Compression Seems Not to Work
If Gzip or Brotli compression does not appear to be working correctly, the issue is often related to server configuration, caching layers, CDN behavior, or response handling outside of FastMe itself. Compression can sometimes already be enabled elsewhere without appearing obvious at first glance.
Continue reading