Posted on Leave a comment

The Hidden Caching Problem That Broke My Site (And How I Fixed It)

Everything looked like it was working.

Until it wasn’t.

  • Pages wouldn’t update
  • Changes didn’t reflect
  • External tools saw different results

And the worst part?

It wasn’t obvious why.


Why This Happens

Modern websites don’t just run from one place.

You may have:

  • server caching
  • plugin caching
  • CDN caching (Cloudflare)

All layered together.

If they conflict, things break in subtle ways.


What I Experienced

  • Changes not appearing after updates
  • Different responses depending on request method
  • Inconsistent behaviour across tools
  • Unexpected errors (including 429s at one stage)

Everything felt unstable.


The Real Problem

The issue wasn’t one thing.

It was:

multiple caching layers interfering with each other

Examples:

  • Server cache vs plugin cache
  • CDN serving stale content
  • Different cache rules for bots vs users

What Actually Fixed It

The solution wasn’t adding more tools.

It was simplifying:

  • Reducing overlapping caching systems
  • Defining clear exclusions (e.g. dynamic pages)
  • Testing responses outside normal browsing

And most importantly:

” understanding what layer was doing what “


What You Should Do

If your site behaves inconsistently:

  1. Identify all caching layers
  2. Remove unnecessary overlap
  3. Set proper exclusions (cart, checkout, APIs)
  4. Test using multiple methods (not just browser)
  5. Keep caching simple and predictable

The Bigger Lesson

Most platforms don’t explain this well.

So beginners:

  • add more plugins
  • create more conflicts
  • and make things worse

Simplicity beats complexity every time.


Bridge to System

This is one of many hidden problems that slow people down.

Instead of guessing through it:

FROISK gives you a structured path that avoids these traps.


Finally,

Build smarter, not harder.

Start with a system that removes the confusion.