Cache Layer Activation
Turn caches back on in a controlled order so you can validate behavior at each layer.
Recommended Activation Order
| Order | Layer | Why |
|---|---|---|
| 1 | Origin page cache | validate HTML caching behavior first |
| 2 | Browser cache headers | validate client caching is sane |
| 3 | CDN caching | validate edge behavior after origin is stable |
| 4 | Optional extras (guest optimization/APO) | add only after the baseline is correct |
caution
If you enable everything at once and something breaks, you will not know which layer caused it.
Verify With Headers
Check cache headers on a public page
curl -sI https://example.com/ | grep -iE 'x-litespeed-cache|cf-cache-status|cache-control'
What you want:
- public pages: cache hits after warm-up
- admin/login/checkout: bypass
Purge Intentionally
- Purge once when you switch layers.
- Avoid purging constantly during testing; it destroys your ability to observe steady-state cache behavior.
Warm the Cache (Optional)
If you have a crawler/warmup tool, warm key pages after major purges so real visitors do not pay the cold-cache penalty.
Checklist
- Origin cache enabled and verified.
- Dynamic routes bypass caching.
- CDN caching enabled only after origin is stable.
- Headers validated on key pages.