VaryCache

VaryCache combines page caching with content personalization. Unlike traditional caching plugins that serve the same cached page to everyone, VaryCache can serve different cached versions based on A/B tests, visitor location, or URL parameters.

Yes! You can use VaryCache purely as a page cache. Enable “General Page Cache” in the Page Cache tab and configure which pages to cache. A/B testing, geo targeting, and query parameters are optional features.

VaryCache reads country information from HTTP headers provided by CDNs: – CloudFront: CloudFront-Viewer-Country – Cloudflare: CF-IPCountry – Custom: You can configure your own header name

If no header is detected, the country code will be “XX”.

Yes! The shortcodes work with any page builder including Elementor, Gutenberg, Divi, WPBakery, and others. Simply add the shortcode blocks where needed.

Visitors are randomly assigned based on the weights you configure (e.g., 50% variant A, 50% variant B). The assignment is stored in a cookie so they see the same variant on subsequent visits.

No. Search engine bots see the default variant, and the canonical URL remains unchanged. This is the recommended approach per Google’s guidelines for A/B testing.

VaryCache includes several Core Web Vitals optimizations: – HTML Minification – Reduces page size by removing whitespace – DNS Prefetch – Pre-resolves external domains (Google Fonts, Analytics, etc.) – Preload Resources – Preloads critical fonts, CSS, and hero images (improves LCP) – Disable Emoji – Removes WordPress emoji scripts (~15KB savings) – Image Dimensions – Adds missing width/height to prevent layout shifts (CLS) – Gzip Compression – Compresses HTML output to reduce page size by ~70% – Link Prefetch – Preloads pages when user hovers over links

You can configure specific REST API endpoints to be cached (e.g., /wp/v2/posts ). Cached responses are served directly without executing PHP, significantly reducing server load for API-heavy sites.

Cache files are stored in wp-content/cache/varycache/ . Settings are stored in wp-content/uploads/varycache/settings.json . Both locations are WordPress-compliant.

Yes, use VaryCache_Cache::clear_cache() in your code. The cache is also automatically cleared when posts are saved or deleted.

Yes, but for A/B testing and geo targeting to work correctly, configure your CDN to: – Pass through cookies (for A/B test variant assignment) – Forward country headers (for geo targeting)