Every cache purge leaves your pages \"cold\": the first visitor after a purge pays the full origin render time. CacheBoost Warmer closes that gap. Whenever a purge or invalidation occurs in WordPress, it tells the CacheBoost API to re-warm the affected pages, so your cache stays hot and every visitor hits a fast, cached response.<\/p>\n\n
Features:<\/strong><\/p>\n\n Go to the CacheBoost<\/strong> menu:<\/p>\n\n WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache<\/p>\n\n This plugin sends data to the CacheBoost API (https:\/\/api.cache-boost.com) to trigger cache warming jobs after a purge event. Data transmitted includes the site URL, the list of page URLs to warm and a timestamp. No personal user data is sent.<\/p>\n\n Requests are only made when:\n- The plugin is enabled in the CacheBoost settings\n- A valid API key (format: cb_live_...) has been configured<\/p>\n\n CacheBoost Terms of Service: https:\/\/www.cache-boost.com\/terms<\/p>\n\n\n No. Warming notifications are fire-and-forget ( Yes, but do not network-activate. Each sub-site should have its own settings and API key.<\/p><\/dd>\n Only the site URL, the list of page URLs to warm (Smart mode), and a timestamp. No credentials and no personal data are ever transmitted.<\/p><\/dd>\n Nothing breaks on the front end. Because notifications are non-blocking, a failed or rejected request is logged silently and your WordPress pages keep serving as usual. Use Test Connection<\/strong> in the admin to validate the key.<\/p><\/dd>\n CacheBoost works with any CDN that serves content via HTTP \u2014 Cloudflare, Fastly, BunnyCDN, KeyCDN, and more. If your CDN caches HTTP responses, CacheBoost can warm it.<\/p><\/dd>\n Absolutely. CacheBoost works with any caching layer \u2014 not just CDNs. If your site uses Varnish, Redis, a file cache, a database cache, or any HTTP-based caching system, CacheBoost can warm it. As long as your pages are served faster on the second request, CacheBoost is useful.<\/p><\/dd>\n Warming requests are sent at a controlled rate to avoid overloading your origin server. You can configure the concurrency and request rate per boost from your CacheBoost dashboard.<\/p><\/dd>\n No problem. On a full warm, CacheBoost reads your sitemap (including multi-level and sitemap index files) with no limit on the number of URLs. Every page gets warmed, regardless of the size of your site.<\/p><\/dd>\n CacheBoost only sends HTTP requests to your public URLs \u2014 the same requests any visitor would make. No credentials and no private data are ever accessed.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
wp_remote_post()<\/code> with blocking => false<\/code>; never delays a WordPress request.<\/li>\nConfiguration<\/h3>\n\n
Step 1 \u2014 Get your API key<\/h4>\n\n
\n
sites:read<\/code>, boosts:read<\/code>, boosts:write<\/code>, runs:read<\/code>.<\/li>\ncb_live_\u2026<\/code>).<\/li>\n<\/ol>\n\nStep 2 \u2014 Configure the plugin<\/h4>\n\n
\n
cb_live_...<\/code> key.<\/li>\nCache plugin support<\/h3>\n\n
External Services<\/h3>\n\n
\n
cacheboost-warmer<\/code> folder to wp-content\/plugins\/<\/code>.<\/li>\n\n
Does this plugin slow down my WordPress site?<\/h3><\/dt>\n
blocking => false<\/code>) and never delay a request. The dashboard widget and history page fetch stats from the API; widget results are cached for a couple of minutes.<\/p><\/dd>\nDoes it work on multisite?<\/h3><\/dt>\n
What is sent to the CacheBoost API?<\/h3><\/dt>\n
What happens if my API key is invalid or the API is unreachable?<\/h3><\/dt>\n
Does CacheBoost work with my CDN?<\/h3><\/dt>\n
Does CacheBoost work without a CDN?<\/h3><\/dt>\n
Will the warming requests affect my server load?<\/h3><\/dt>\n
What if my site has thousands of URLs?<\/h3><\/dt>\n
Is my data safe?<\/h3><\/dt>\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n