Page speed is not a luxury anymore — it is a ranking factor, a conversion factor, and on a busy site, a direct cost. Every millisecond adds up, and for a WordPress site the single biggest win available is full-page caching: serving each visitor the finished HTML of a page instead of letting WordPress regenerate it from PHP and database queries on every single request.
The EDZNET Super Cache plugin takes the classic full-page cache approach and wraps it in a zero-configuration experience. Install it, activate it, and the site gets noticeably faster — no settings pages to wrestle with, no rewrite rules to configure, no technical decisions to make.
What You Get Out of the Box
Full-Page Disk Cache, Served Before WordPress Boots
The plugin installs an advanced-cache.php drop-in. On a cached request, the cached HTML file is served before WordPress even boots — no PHP framework, no database connection, no plugin loading. That is the fastest page delivery WordPress can offer, and it directly protects your site from traffic spikes.
HTTP 304 Support
Returning visitors can be served a 304 Not Modified response for unchanged pages, so their browsers reuse the local copy instead of re-downloading the whole page — saving bandwidth for you and load time for them.
Mobile-Aware Caching
Desktop and mobile visitors get their own cached copies (optional), so responsive sites are never served a broken mobile layout from a desktop cache.
Built-In Performance Features
- Lazy loading — images and iframes below the fold load only as the visitor scrolls to them
- HTML minification — whitespace and redundant bytes stripped from served markup
- Deferred JavaScript — scripts load without blocking the page render, while advertising, analytics, and reCAPTCHA scripts are automatically skipped so they continue to work exactly as before
- Emoji script removal — the hidden emoji polyfill bloat is disabled
- Gzip compression — automatic via Apache's
.htaccess - Browser caching expiry —
Expiresheaders tell browsers to cache static assets
Works on Apache, Nginx and LiteSpeed
Many caching plugins only work properly on Apache with specific rewrite rules. EDZNET Super Cache serves its cached files at the PHP level, so it runs on Apache, Nginx, and LiteSpeed with zero configuration — no Nginx helper config, no rewrite-rule fiddling. It also coexists with BitNinja and other WAF/server protection stacks.
Stale Caches Never Bite
A cache is only as good as its invalidation. The plugin automatically purges the affected cache — and preloads the fresh page in the background — whenever your content changes:
- A post or page is published, updated, or trashed
- A comment is added or a comment status changes
- The theme is switched or updated
- A plugin is activated, deactivated, or updated
And when you need to force it, the "Purge EDZNET Cache" button sits right in the admin toolbar.
Page Builder Friendly
Editor previews inside Elementor, Divi, and other builders are never cached, so you always see live changes while building. When you save a post, the plugin purges (and preloads) the affected pages automatically — and if you change a global setting in your builder's theme options, one click on Purge EDZNET Cache in the admin toolbar refreshes the whole site.
Frequently Asked Questions
Does it work on Nginx or LiteSpeed?
Yes. Unlike plugins that depend on Apache-specific rewrite rules, Super Cache serves cached files from PHP, so it works identically on Nginx, LiteSpeed, and Apache without extra configuration.
Will deferred JavaScript break my ads or analytics?
No. Deferral deliberately skips advertising, analytics, and reCAPTCHA scripts, so they continue to load and execute normally while everything else is deferred.
Do my visitors ever see stale pages?
Stale pages are a thing of the past. Content-triggered purges, background preloading, and the admin-toolbar purge button together guarantee that what visitors see matches what is published.
Is there anything I need to configure?
Nothing to get started. The plugin makes sensible decisions on your behalf; the advanced options are there purely if you want to tune them.
