Three cache delivery methods with different trade-offs
WP Super Cache offers three delivery methods, balancing speed against configuration effort and flexibility.
Expert mode uses server rewrite rules to serve static files directly, bypassing PHP for the fastest delivery, but editing .htaccess incorrectly can disrupt a site. Simple mode serves the same kind of cached file through PHP; it is nearly as fast and avoids .htaccess changes, making it a lower-risk option for many site owners.
WP-Cache handles logged-in visitors, parameterized URLs, feeds, and other personalized cases. It is more flexible but slightly slower, so sites with visitor-specific content may need it alongside static caching.
Preloading and cache cleanup for changing sites
Preloading can build cache files ahead of visits, while cleanup settings help balance freshness against storage use.
- Preloading: visits posts, categories, and tags to generate cached pages. It runs sequentially, so a large site may take time to process.
- Preload Mode: disables routine garbage collection, helping keep older cache files available. Pages can become stale, though edits and new comments clear relevant cached files.
- Garbage collection: set how long files remain fresh and how often stale files are removed. Active sites may need shorter intervals; mostly static sites can keep files longer.
- Notifications: enable email updates about cleanup jobs to help monitor cache maintenance. Consider available server space when choosing how long to retain files.
Checking that cached pages are being served
Several checks can confirm caching, though Apache’s pagespeed module may interfere with the Cache Tester.
The Cache Tester requests the homepage twice and compares timestamps. For further checks, enable debugging logs and inspect activity, or view page source for cache-related markers and timestamps. HTTP headers distinguish files served through PHP from WP-Cache files, and the cache directory can be checked for static files. If the tester behaves unexpectedly, check whether Apache pagespeed is enabled before treating that result as a caching failure.
A long-running cache plugin with support activity to monitor
WP Super Cache combines broad adoption with a support record worth checking before relying on help for time-sensitive issues.
- Publisher: Automattic is listed as the author, and the plugin is among the directory’s most widely installed.
- Support: Six recent threads are listed, with 67% resolved. That resolution share suggests room to check current responsiveness if prompt support matters to your site.
- Rating and freshness: The rating is good, with many reviews, and the plugin was updated about a month ago. Its adoption and rating are useful signals, but neither replaces checking whether recent support answers meet your needs.
For sites that benefit from static delivery and can manage cache freshness, the mix of delivery modes and verification tools is useful. Choose Simple mode when avoiding rewrite-file edits matters; sites with personalized pages should account for the slower, more flexible WP-Cache path. Before adopting it, consider how quickly your content changes, how much cache storage you can spare, and whether the support response pattern suits your expectations.
