The FacetWP Cache Add-On is a performance-focused extension designed to speed up filtering on high-traffic WordPress sites. While FacetWP is inherently fast, this add-on specifically targets the database load generated by complex AJAX requests.
This is EXACTLY the same product as distributed by the developer. Sales Page
| Feature | Details |
| Current Version | 1.7.1 (as of late 2024/early 2025) |
| Developer | Matt Gibbs (FacetWP) |
| License | GPL |
| Primary Goal | Reduces database queries by caching FacetWP AJAX requests. |
| Database Table | Creates wp_facetwp_cache with columns: id, name, uri, value, expire. |
AJAX Caching: Caches both facet data (the choices shown) and the template results (the posts returned).
Performance Boost: Significantly improves Time to First Byte (TTFB) for filtered pages.
Smart Invalidation: The cache can be set to expire globally (default is 1 hour), but it also auto-purges when content or products are updated.
Compatibility: Works alongside standard caching plugins like WP Rocket or W3 Total Cache (since these often ignore AJAX requests by default).
Background Warming: Supports basic cache priming so the first visitor doesn’t have to wait for the cache to build.
FacetWP Version: Requires FacetWP 4.0+ for the latest versions of the add-on.
PHP Version: Supports PHP 7.0+ and is fully compatible with PHP 8.x.
Object Caching Conflict: It is generally not compatible with persistent object caching (like Redis or Memcached) if those systems interfere with FacetWP’s query detection.
Symlink Dependency: Upon activation, it attempts to place a db.php file in the wp-content folder. This can conflict with plugins like Query Monitor or W3 Total Cache if they have already placed their own db.php file there.
Workaround: You may need to manually merge the contents of the FacetWP db.php into the existing one.
This add-on is most effective for:
High-traffic landing pages with specific, popular facet combinations.
Large WooCommerce stores where calculating facet counts (ghost entries) for every user is resource-heavy.
Sites with limited server resources that struggle with concurrent AJAX filtering requests.
