← Integrations

Integration

Static Shield + WP Super Cache

Coded compatibility profile

WP Super Cache, from Automattic, is one of the oldest WordPress caching plugins — its own page cache runs as a second, independent caching layer alongside Static Shield's static output, the same shape as WP Rocket or LiteSpeed Cache. Its "Expert" mode goes further, writing its own mod_rewrite rules to serve cached HTML files directly from disk, bypassing PHP almost entirely — functionally the same technique Static Shield itself uses, which makes it a direct rule-ordering conflict rather than just a freshness risk. Its CDN URL rewriting is compatible and fine to leave on.

Performance note

WP Super Cache's Simple mode is the same second-caching-layer conflict WP Rocket and LiteSpeed Cache have. Its Expert mode goes further, writing its own mod_rewrite rules to serve cached HTML directly from disk — the same static-file-serving technique Static Shield itself uses, which makes it a rule-ordering conflict worth resolving, not just a freshness one.

Recommended mode

No single mode applies — WP Super Cache doesn't influence which serving mode a site should use; see the notes below for what it actually does.

Static behavior

CDN URL rewriting is captured in the static HTML like any other asset URL.

Dynamic behavior

None declared — the page cache and preload features are treated as private, admin-side concerns rather than public routes.

Bridges & routes

None declared.

Setup

No special setup — detected automatically once active. Consider disabling its page caching (and Expert-mode rewrite rules specifically) alongside Static Shield's own static release.

Limitations

WP Super Cache's own page cache running alongside Static Shield's static output can serve stale content from one layer after the other has been rebuilt. In Expert mode specifically, its own mod_rewrite rules and Static Shield's static-file rewrite rules can compete for the same request, with whichever rule set runs first in .htaccess deciding what a visitor actually sees. The recommended fix is to disable WP Super Cache entirely for the site (leave CDN URL rewriting on if desired), so Static Shield's build is the single source of truth and the only rewrite rules active in .htaccess. Its preload/cache-warming feature is also redundant once a Static Shield build already serves every page statically. This hasn't been behaviorally validated against a real install, and Static Shield doesn't change any of these settings automatically.

Want to see this against your own site?

Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.

Get Static Shield