An editor installs three performance plugins on an already optimised Raidboxes Box. Updated posts stay cached twenty minutes; WooCommerce cart sometimes shows zero euros. Site is « faster » on GTmetrix — wronger in prod.
Raidboxes is managed German WordPress hosting with built-in cache. Optimisation starts by understanding layer order, not stacking plugins.
Typical Raidboxes cache stack
| Layer | Role | Purge |
|---|---|---|
| NGINX / page | Anonymous visitor static HTML | Raidboxes dashboard, TTL |
| Redis object | WP queries, options, transients | Flush object cache |
| CDN (if enabled) | Edge assets | CDN + origin purge |
| Plugin (avoid duplicate) | Often redundant | Frequent conflicts |
| Browser | Cache-Control headers | Asset versioning |
Optimisation method without regression
- Baseline: TTFB, LCP without extra cache plugin.
- Identify dynamic content (Woo, members, geo).
- Exclude sensitive URLs from full page cache.
- Object cache: keep; flush after major option changes.
- Images: WebP, lazy — often more gain than micro-cache plugin.
Purge test: change title → visible in < 60 s in private mode?
WooCommerce and membership
- Exclusions:
/cart,/checkout,/my-account, AJAX fragments. - Fragments: watch Redis cache + mini-cart.
- Stock: never full-cache product pages with real-time stock without invalidation.
The crux: fast stale = silent bug
Optimise by mapping purges first, not installing the tenth « boost » plugin.
Decide and move forward without blind spots
- Inventory active layers on the Box.
- Remove redundant plugins one by one with measurement.
- Document Woo/membership exclusions.
- Purge procedure for content editors.
- Raidboxes profile + guides.
Frequently asked questions
Raidboxes cache layers?
NGINX page, Redis object, optional CDN — distinct TTL and purge.
WP Rocket needed?
Often no — double cache risk; measure first.
Purge correctly?
Raidboxes tools + Redis flush; test headers/private mode.
WooCommerce?
Exclude checkout/cart; object cache yes; selective page cache.
Before the next perf plugin, ask: which Raidboxes layer already handles what I'm adding?