Hi @motouta
I hope you’re well today!
Most common reasons for that are:
1. Site is behind CloudFlare or similar CDN that applies compression on its own.
In such case compression settings may be overwritten by it or, rather, “hidden”. What I mean by this, that compression would work but only on the way “between” your server and that CDN and between end-user and CDN, it would be compression (or lack of it) applied by that CDN. It would also affect results of Hummingbird’s compression check (not the compression itself).
2. Compression type is different – Brotli instead of Gzip.
Sometimes Brotli is used either by the CDN/proxy used or is forced by the webserver/host despite adding gzip rules. Brotli is just another type of compression and it’s perfectly fine but Hummingbird simply doesn’t detect it yet (that’s planned to be fully supported).
3. Rules weren’t added to correct config file or nginx wasn’t restarted after they are added.
In nginx relationships between config files may be pretty complex but also – if you are not in full control of the server: while in theory nginx config can be customized by the individual config file for the site, some hosts (especially Managed WP hosting type) block that and such file simply is ignored.
In any case, nginx needs to be restarted after any changes were made to its config files to fetch and apply them.
I can’t tell for sure which case is it without checking the site but I’d suggest starting with this:
1. visit this 3rd-party (free) site
https://www.giftofspeed.com/gzip-test/
2. and run you site’s homepage URL, then some random CSS URL (but from your site’s domain; not any external one) and then JS URL (again, from your site’s domain, not external one) through it and see what it reports.
If it reports Brotli or Gzip – it means compression works and the status in plugin can be ignored.
If it reports no compression:
– make sure that nginx was restarted after rules are added to its config
– and if that doesn’t help, you’ll need to contact your host for help with this (note that compression is not done by Hummingbird, it’s done by the server and Hummingbird only helps control it if server is configured in a way that allows it).
A “last resort” alternative solution is to use Hummingbird’s built-in “software” compression:
– you need to have “Page Caching” enabled in Humminbird
– then go to “Hummingbird -> Caching -> Page Caching”
– and enable “Serve compressed version of cached files” option there
Kind regards,
Adam
