The terms “page cache” and “static delivery” are often used interchangeably in WordPress performance discussions, but they describe meaningfully different architectural patterns with different trade-offs. Understanding the distinction is useful before evaluating any static delivery tool, including Nexora Engine.
What page caching does
Traditional WordPress page caching (LiteSpeed Cache, W3 Total Cache, WP Super Cache) intercepts requests at the PHP level, renders the page on first request, stores the HTML output, and serves the stored version on subsequent requests until the cache expires or is invalidated.
The critical characteristic is that this cache is still managed by PHP. On a cache hit, PHP loads, checks the cache, finds the stored HTML, and serves it. This is fast — typically 50–150ms TTFB on reasonable hardware — but it is not as fast as serving a file directly from disk at the web server level.
What static mirroring does
Engine’s static mirror approach generates full HTML snapshots and writes them to disk as files. Apache or Nginx serves these files directly using standard file serving — no PHP invocation at all. TTFB on cache hits typically falls below 20ms.
The trade-off is regeneration complexity: a static mirror must be explicitly rebuilt when content changes, because there is no PHP interceptor to trigger cache invalidation on the fly. Engine manages this through a regeneration queue with event-driven and scheduled triggers.
When page caching is sufficient
Page caching is the right choice when your server has excess PHP capacity and your primary performance constraint is database query time or uncached PHP execution. It’s also simpler to configure and maintain on managed hosting environments where web server configuration is not accessible.
When static mirroring adds value
Static mirroring produces the largest gains when your server is PHP-constrained — high traffic volume relative to PHP-FPM worker capacity, or an underpowered VPS where even cached PHP requests add latency. It also applies when your hosting environment supports custom Apache or Nginx configuration and you need TTFB below 30ms for a significant percentage of requests.
For SEO, sub-30ms TTFB can affect crawl budget utilisation on large sites. Googlebot allocates crawl time based on server responsiveness; a faster server allows more pages to be crawled within the same session.
Measurement approach
In our lab environment, we compare these approaches by running WebPageTest measurements with LiteSpeed Cache in full-page mode, then Engine in mirror mode, against the same WordPress install. We use five-run averages with cable throttling to reduce variance. Results are documented in case study articles on this site.
To compare these approaches on your stack, include your current cache plugin and server type in a demo request. The Engine walkthrough will include a configuration specific to your environment.