Hello @kerdezo
Thank you for your inquiry and I am happy to assist you with this.
In short, yes you should enable Browser Cache in W3TC as it offers much more than gzip, meaning cache-control header, expires header, Etag, etc.
If Gzip compression is already enabled you should not enable it in W3 Total Cache to avoid double compression.
This being said make sure that Gzip is enabled (working on your server) or you just have mod_deflate enabled. If you only have mod_deflate enabled (required for gzip compression), this means that you should also enable Gzip compression in W3 Total Cache to compress the files.
If gzip compression is already doing its’job, then as mentioned, you should not enable in W3 Total Cache. To make sure check your .htaccess file and see if there are any gzip rules outside of W3TC rules.
Thank you!
Hi Marko,
Thanks for the swift respond.
Now it’s clear.
As I wrote – on server – not only mod_deflate is enabled but also Gzip compression is switched on through CPanel.
As you explained “Browser Cache in W3TC offers much more than gzip”, so I will
first switch off my server side Gzip compression but keep the mod_deflate enabled and then enable Browser Cache in W3TC.
Thanks again for the explanation!
Have a nice day!
Hello @kerdezo
You are most welcome!
Thanks!
