Why doesn’t W3TC like zlib.output_compression?

  • Resolved wrip

    (@wrip)


    5 years, 5 months ago

    I received this warning in Dashboard:

    Either the PHP configuration, web server configuration or a script in the WordPress installation has zlib.output_compression enabled.

    Why W3TC doesn’t like zlib.output_compression enabled?

    Not sure if this is caused by zlib.output_compression – my website’s frontend speed seemed to have improved after zlib.output_compression enabled but the Dashboard is quite slow.

Viewing 1 replies (of 1 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello,

    You enabled zlib.output_compression, which compresses all responses in Apache. We use PHP to compress the page and store the compressed page in a file to be accessed directly from Apache so we don’t have to build the page anymore. That’s the difference. your PHP configuration doesn’t allow us to compress the page.
    Using zlib.output_compression is not as fast, because then we have to store the page uncompressed (takes up more disk space) and it has to be compressed on every request.
    So you should disable zlib.output_compression and leave Gzip compression enabled.

Viewing 1 replies (of 1 total)
  • The topic ‘Why doesn’t W3TC like zlib.output_compression?’ is closed to new replies.