Yes, W3 Total Cache has object caching. If your host doesn’t recommend using W3TC for object caching, do they have another recommendation?
More info: https://amp-wp.org/documentation/getting-started/amp-site-setup/persistent-object-caching/
Object caching is a best practice for improving WordPress site performance generally, and it’s especially beneficial with AMP.
Thread Starter
pran
(@sarina1)
“The object caching does not work well with our servers and is likely to cause issues. I would suggest to avoid it as much as possible.” this is the response
They said “try to activate object cache on w3tc and see if there are any problems – if there are any deactivate.
No one of the options provided in the page you refered
Does w3tc object cache work the same ?
I’m guessing your server doesn’t have a persistent object caching service, like Redis or Memcached. So that’s why your host doesn’t recommend it.
W3TC has alternative object caching backends which you can use.
Nevertheless, object caching is not required. It’s simply recommended. The most important thing is to have page caching, which apparently you do have with W3TC. So you can ignore the object caching recommendation.
This is very helpful. I’ll contact InMotion Hosting and see if they do Redis… W3 was too complicated for me, though I stuck with it for years.
I’m so grateful to you Mr. Ruter!!! I called up InMotion Hosting and they now have hosting specific to WP. My old hosting didn’t support persistent object caching, just as you had mentioned. So I switched to the WP hosting plan… which I would not have known to do without your help.
Thank you, Thank you!!!!
@sarina1 As we haven’t received a response, I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist. Thank you!
