Independent comparison · no paid rankings
Home / Blog / Technical / Raidboxes: map the NGINX, Redis and plugin caches

Raidboxes: map the NGINX, Redis and plugin caches

Which layer serves HTML, objects and plugins, and in which order to purge. Plugin, SSH and root limits are another article.

Hébergeurs.eu Editorial Team 2 min read Updated Dec 22, 2026

Before adding a performance plugin, name the cache layers already in place: page, object, plugin. What managed hosting takes away — filtered plugins, no root — is another subject: limits of managed WordPress at Raidboxes.

Raidboxes is managed German WordPress hosting with built-in cache. Optimisation starts by understanding layer order, not stacking plugins.

Typical Raidboxes cache stack

LayerRolePurge
NGINX / pageAnonymous visitor static HTMLRaidboxes dashboard, TTL
Redis objectWP queries, options, transientsFlush object cache
CDN (if enabled)Edge assetsCDN + origin purge
Plugin (avoid duplicate)Often redundantFrequent conflicts
BrowserCache-Control headersAsset versioning

Optimisation method without regression

  1. Baseline: TTFB, LCP without extra cache plugin.
  2. Identify dynamic content (Woo, members, geo).
  3. Exclude sensitive URLs from full page cache.
  4. Object cache: keep; flush after major option changes.
  5. 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

  1. Inventory active layers on the Box.
  2. Remove redundant plugins one by one with measurement.
  3. Document Woo/membership exclusions.
  4. Purge procedure for content editors.
  5. 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?

See the RAIDBOXES sheet

Independent scores, plans, pros/cons and alternatives to RAIDBOXES.

Open the RAIDBOXES sheet
Blog

Related reading

All articles →