Nexora Engine handles static delivery through a mirror generation pipeline that operates independently of your WordPress page cache. Instead of intercepting requests at the PHP level, Engine regenerates full HTML snapshots and serves them from your web server configuration directly — resulting in measurable TTFB reductions without modifying your existing caching plugins.
How mirror regeneration works
When Engine triggers a mirror build, it crawls your WordPress URL list, renders each page in a headless context, and writes the resulting HTML to a configurable static directory. Your Apache or Nginx configuration then routes matching requests to those static files before PHP is invoked.
The regeneration can be triggered in three ways: manually from the Engine dashboard, on a scheduled interval (hourly, daily, or custom), or automatically on specific WordPress events such as post publish, plugin activation, or option changes.
Apache configuration basics
On an Apache stack, Engine places a set of RewriteRules in your virtual host or .htaccess that check for the existence of a static file before proxying the request to WordPress. If the static file exists and is within its freshness window, Apache serves it directly from disk. If not, the request falls through to PHP.
RewriteCond %{REQUEST_METHOD} GET
RewriteCond %{DOCUMENT_ROOT}/static-mirror%{REQUEST_URI}/index.html -f
RewriteRule .* /static-mirror%{REQUEST_URI}/index.html [L]This pattern eliminates PHP execution time for cached URLs. On a mid-range VPS with a standard WordPress install, TTFB typically drops from 400–800ms to under 50ms for mirrored pages.
Nginx equivalent
On Nginx, the same pattern uses a try_files directive within your server block. Engine generates the configuration fragment on setup and validates it against your existing Nginx config before applying:
location / {
try_files /static-mirror$uri/index.html $uri $uri/ /index.php?$args;
}Cache control and invalidation
Engine exposes cache control policies per post type, taxonomy, or URL pattern. You can set a global freshness TTL (e.g., 24 hours for static pages, 1 hour for product pages) or tie invalidation to WordPress hooks. The invalidation queue is managed through Engine’s dashboard and supports batch invalidation for site-wide rebuilds after a theme update or major content push.
Core Web Vitals impact
Because static mirrors bypass PHP and database queries entirely, the principal performance gains show up in LCP and TTFB. Engine’s dashboard surfaces these as lab-measured values alongside real-user data from the CrUX dataset where available. You can track before/after comparisons per URL group.
To evaluate Engine on your Apache or Nginx stack, submit a demo request with your server environment details. The walkthrough will be configured for your specific setup.