W3 Total Cache and Cloudflare APO

  • Resolved ungowp

    (@ungowp)


    1 year, 1 month ago

    Hello,

    I am using W3 Total Cache for the first time instead of Litespeed Cache on Litespeed server because I bought Cloudflare APO and I think it is incompatible with Litespeed Cache.

    But W3 Total Cache seems a bit complicated to me and I’m wondering how best it can work together with Cloudflare APO?

    For example, should I disable the W3 Total Cache Minify feature? Also, the APO plugin sets the Browser Cache TTL time to 4 hours. Should this setting remain like this? In this case, do we need to turn off W3TC’s Browser Cache setting?

    Or can I enable all W3 Total Cache settings?

    Thank you.

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

    (@vmarko)

    Hello @ungowp

    Thank you for reaching out and I am happy to help!
    W3 Total Cache has the extension to configure Cloudflare, however, we do not have the APO management there. So if you are using the APO plugin, you should continue using it and make some changes accordingly in the W3TC.

    In most cases, W3TC Minify and Cloudflare Minify work well together. However, in general, you should not be using more than one solution for Minify. So either disable Minify in Cloudflare and keep the W3TC Minify, or vice versa. Please note that W3TC Minify offers much more freedom and options to defer minified scripts and eliminate render blocking scripts/css.

    I would also suggest configuring the Cloudflare to respect the origin headers. The Browser Cache TTL set to 4 hours does not reflect the W3TC Browser Cache settings, and you should cache static files for a year, instead of just 4 hours as the testing tools will suggest this in practice, it’s best to have this enabled.
    So you should use the W3TC Browser Cache settings.

    I hope this helps!

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘W3 Total Cache and Cloudflare APO’ is closed to new replies.