I installed this diabolical plugin. The moment it activated it crashed my site and I was unable to login. Support sends you a link to a URL full of people complaining that the plugin has affected their entire installation. This plug in cost me one week work.
I manage many WordPress installations, and I used this plugin on all of them. Then it started growing in size, adding features and eventually becoming the most annoying piece of software ever written. It takes over your WordPress installation and the authors face poping up all the time asking for likes and reviews is just the beginning of your troubles.
Uninstalling this plugin is not easy, there are pages and pages about this online, do yourself a favour and pick a different caching plugin, WP-Super Cache is great. W3TC will drive you crazy eventually. Its faults are many and the author is not so good at support.
Do your research and avoid this mess.
W3 Total Cache busted all of my login access, on 3 different sites. When I deleted the plugin, it then created huge issues, since it DOES NOT delete or remove the files it installs. I would not recommend this plugin to anyone who isn't very proficient and comfortable heading in to their server files and changing things. MY BAD for not trusting the negative reviews of late.
No plugin should EVER crash a WordPress site on deactivation. But this plugin does. And if for any reason you don't have FTP access to the server to manually delete object-cache file(s), you're screwed.
I'm really surprised that this plugin has been around this long, and still does this type of stuff. For me this isn't suitable for any business or production site.
Was very excited initially, now totally disappointed. After installation and activation it took a very very long time to load!!
Use at own risk! But if you ask me, dont use at all!
I once loved this plugin but not so much any more. My site scores are not what they once were and I struggle with how slow it makes my admin panel run.
I also get this error: " Unfortunately, an error occurred while creating the minify cache. Please check your settings to ensure your site is working as intended." I've tried everything, including turning off the Minify option but still get this error.
The last thing I'll mention is that when I test my site on "Page Speed" it tells me I should use browser caching. However, the browser caching feature is turned on in W3TC so it's clearly not working.
Totally useless and could potentiality harm you rankings. After the September update google bot couldn't access some of my pages. I wasn't aware of this issues until got a message in WM tools regarding soft 404 errors. To make a long story short, after hours of investigating I deactivated the plugin and fetched the pages in question, and I could see in 'live activity view' using another plugin that google was crawling those pages in question. When I made it active again, no matter how many times I fetched those pages, no sign of google bot.
Those pages used to rank very well for number of keywords, and now all the hard work is gone. Courtesy of W3 Total Cache. Thanks for ruining it.
On the surface it may look like everything is fine. But if you start to lose rankings and traffic you know where to look.
*** Use it at your own risk***
Thought it would be good, but mistaken. Caused my WooCommerce shop to only have MASSIVE images and over-write the settings about how many columns to have per page, or what size the product images should be and where.
Also, for a non-programmer like me it is not intuitive.
I've used W3 Total Cache on my site for a couple of years with no problem. I picked it because of it's high ratings and widespread good press. It is surely a complex product, but sticking with the basics just worked.
Then, when I converted my site to SSL/HTTPS because Google announced they will start using this in ranking, I immediately ran into a problem with pages getting a gzip decode error on first load from an empty cache; subsequent loads worked fine. In Chrome, the error is Error 330 (net::ERR_CONTENT_DECODING_FAILED).
I decided to seek W3's support with their $75 email support offering. Despite my careful documentation of the issue, Mr. Willie Jackson immediately copped an attitude with me. My site is on a shared server, as I think most small businesses must be, and of course the host doesn't provide root access, but I offered to obtain from the host whatever files Mr. Jackson needed. I gave him WordPress administrative access to my site. But Mr. Jackson took the stance that they have never had this problem (hmmm, Google Search turns up a number of old reports of it), it must be my server (my host found no errors logged), if I couldn't provide root server access he couldn't help me, and if my host wouldn't provide root access then I should change hosts.
This is not support. This is especially not paid support. I have since switched to the WP Super Cache plugin, by Automattic, the WordPress.com people.
Moral of my review: Don't pay W3 for support.
To many strange behaviours.
To many spam after 30 days using it.
Trying to satisfy every need results with errors like in w3 total cache.
You must log in to submit a review. You can also log in or register using the form near the top of this page.