Support » Plugin: WP-Optimize - Clean, Compress, Cache. » Clash with WP Fastest Cache?

  • Resolved solid_snake

    (@solid_snake)


    Hello,

    I just saw that the plugin has been updated to include cache as well. I have two questions regarding this:

    1. Will this interfere in any way with WP Fastest Cache? (https://wordpress.org/plugins/wp-fastest-cache/)

    2. I dont plan to use the cache feature of Wp Optimize. However, will this feature add any sort of load on the wp-admin backend and the main site?

    Please let me know and thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author David Anderson

    (@davidanderson)

    Hi @solid_snake,

    1. No, it should not interfere in any way if you don’t turn on the page cache in WP-O.

    2. No, it will make no difference, If it’s off, it’s not doing anything.

    Please do give us any feedback you have on what makes you prefer WP Fastest Cache. On our testing, our page cache is at least as fast as other page caches, and is much easier to configure. (We’re aware that WP Fastest Cache also has minification features as well as page cacheing – is it those?).

    David

    Feedback on why I prefer WP Fastest Cache: I have had WPFC from the beginning, changing themes adding new plugins, basically handles just about anything you can throw at it without breaking your styles. It builds its cache incredibly fast, it connects to Cloudflare flawlessly. I did try WPO Cache, because you never know, I disabled Asset Cleanup Plugin (for min/combine css js) and disabled WPFC … WPO’s pre-build took what seemed to be an eternity. In the end, it cached well but not being able to use my “Go To” plugins along side of WPO Cache, I had to disable. I offer this feedback with the MOST respect! Team Updraft has SAVED my site on many occasions and I am forever thankful! Best Wishes!

    • This reply was modified 4 weeks, 1 day ago by  shirtguy72.
    Plugin Author David Anderson

    (@davidanderson)

    Thank you.

    WP-O’s pre-populating of the cache is coded to make sure that it isn’t requesting more than one page at a time, so that it doesn’t overload the webserver. It could go faster if it did more, but at the risk of using (especially on lower-end hosting with strict limits) all available resources, so that actual human visitors are slowed down (or the web hosting company throttles you for using too much). We thought it was right to err on that side.

    David

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.