Skip to main content

FluentCommunity

#Tips

⚡️Do you use HTML caching — and how?

Most modern projects with dynamic content (communities, CRMs, boards, forms) use Redis or Object Cache by default. That’s become the baseline.

But when it comes to HTML caching, things get more nuanced. Some apply it only to specific pages, others avoid it altogether due to their architecture or the interactive nature of the content.

👀 Share with us:

  • Do you use HTML caching in your projects?
  • If yes — which pages (landing, /about, /privacy, archives, categories)?
  • How do you separate cacheable and non-cacheable zones?
  • What settings or plugins helped you manage it?
  • If not using it — what’s the reason?

📢 This isn’t about being “for” or “against” caching — we’re looking for real-world examples, setups, decisions, and experience.

✍️ Drop your thoughts in the comments — it’ll be useful for everyone building high-performance WordPress platforms without sacrificing functionality.

⚡️Do you use HTML caching — and how?
  • 7 comments

William Beem

No. I operate my community on a separate site from my publishing. That why I can use browser caching tools for published articles and keep it off my community site.

D@vid

I've installed F.C on a website that's purely a showcase. There’s no caching system in place, except for server-side caching with Gzip compression. I use caching plugins very cautiously, as they often cause issues.

Artur Abakarov

D@vid I'm more and more inclined to drop LiteSpeed Cache, as well as move from the /portal slog directly to the root address, since FC is the primary resource. Do you have it like this now?

D@vid

Artur Abakarov
That depends on the purpose.
Mine is solely intended to present and host the training platform. So I've optimized the few pages it contains and don’t need a caching plugin. And aside from the courses, I don't create pages in F.C, because I'm not a fan of iframes.

Artur Abakarov

D@vid Thanks, got it. In our case, it’s the opposite — almost everything runs through FC: posts, discussions, CRM, forms, support.
That’s why we dropped LiteSpeed Cache, kept only Redis + OPCache, and made FC the main part of the site (no /portal slug).
If it were just a showcase or a landing page, caching would make sense. But in our case — everything is dynamic and real-time 🙂

Jonathan Gwyer

D@vid Pretty sure pages in FC are not iframes?

J V

Only Redis since that was the advice and FC has caching build in. My site doing nothing but FC also, so shouldn't be any need for more caching. Like D@vid said, it often just causes trouble.