I have a fairly large website with personalized data (community site). That means that regular users log in and will get personalized info on the header, which limits the amount of caching that they can receive.
I have been using W3TC plugin for a couple of years with object, page, fragment and db caching using Memcached. I also use cloudflare, so anonymous users get a pretty good experience.
As WP updated I noticed TTFB getting longer and longer. I recently tried turning off the cache by turning off W3TC and was surprised to note that TTFB for logged in users dropped from about 2.5s to 1.2s, which is consistent.
Any idea what’s going on? Are these plugins no longer really that important and just adding overhead to the server? Is there a simpler Memcached object cache that wouldn’t add this overhead but still improved performance?
[ad_2]
That’s a interesting observation with the TTFB. Caching plugins, like W3TC, can be incredibly useful, but they’re not one-size-fits-all. It’s possible that as your site grew and WordPress updated, the plugin settings that once worked like a charm need a fresh look. It’s kinda like adding new performance parts to a car—what worked with the old engine might not be ideal for the new one.
With a complex site and personalized data up in the mix, you might need to fine-tune your caching strategy. Fragment caching should help with dynamic content, but if it’s not set up right, it could be slowing you down instead. It could be useful to dive into W3TC’s settings again or even consult with a performance expert to see if there are specific tweaks that can help your unique setup.
And about Memcached, if you’re looking for something more lightweight, you could check out other object caching options that are designed to be more lean & mean without skimping on performance. Sometimes a less popular plugin can suit your needs to a T since it’s not loaded with features you don’t need. Just make sure to back up before trying out new solutions. Good luck!