Worst Cache Plugin Hands Down

  • dansperfect

    (@dansperfect)


    9 months ago

    If I could give it negative stars I would. Using this plugin slowed my site down by seconds and then cause numerous issues like slow connection speeds and more. Many times you would visit the site and the site would become overloaded just because of this plugin. So i disabled it and removed it. The second I removed it and it’s relevant files I created to make it work my site was totally unusable. Now I have to have this horribly performing plugin installed just to keep my site functional. But at least with it disabled my sites performance is back up to were it should be and I now actually have a better SEO Score without it according to Google then with it because of the increase in performance. My server doesn’t crash anymore either. I know use WP Optimize, which works like a dream compared to this plugin.

    Don’t think my server isn’t built well. It’s a Google Cloud Server with 8 Core Processor and 32GB of RAM and the connection speed is well Google so I can’t get much quicker.

    I would not recommend anyone adding this plugin to their site unless they want an undetachable leach as part of their file system. I will have to take a lot of time to figure out how to follow de-integrate this plugin, which I should send W3 the bill for.

    Yes I know what I’m doing, I have 12 WordPress Sites and have been doing web design since I was 13 or so and I’m 42 now. I even have a college degree in Web Design and one in Computer Science.

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

    (@vmarko)

    Hello @dansperfect

    First of all, thank you for your review and I am sorry abou the experience you’ve had with the W3 Total Cache.

    I’ve read your review, and while I do not want to dispute the fact that you have had issues, it would be great if you’d share more details about the issues (slowing down, loss of functionality etc) and we would be more than happy to assist you with any issues or the configuration.
    W3 Total Cache is known for offering a wide range of configuration options, which can be both an advantage and a challenge. Users with a good understanding of caching and server settings may appreciate the flexibility, but it might be overwhelming in some cases.
    There are a lot of things to consider when it comes to the configuration. Yes, the server resources are one of them, however, the availability of the different options, other plugins’ impact, server-side caching, and of course the understanding of the user about the impact of different features.

    Since you have not shared the configuration, I can only guess what the problem was, however, one of the common mistakes is utilizing the DB caching or Object Cahing with Disk as a caching method. While this method is available, it should be used with caution and on websites where the memory-based caching methods are not available and the database is not a bottleneck of the performance. Caching all of that on disk even with an awesome server build can prove to be counterproductive.
    Once again, this is just an example.
    As I’ve stated before, we would be more than happy to assist you with any issues you have with the W3 Total Cache, and you can open a new topic on the forum(as I can see no topic was opened for this), or drop us a note directly.

    Once again, I am sorry about the experience you’ve had with the W3 Total Cache and we are hoping on assiting you further.

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Worst Cache Plugin Hands Down’ is closed to new replies.