• Plugin Author Kevin Kyburz (@swissky)

    (@swissky)


    If runs complete but the hit ratio stays at zero, start with the cache status shown in warmup.rocks.

    DYNAMIC

    The CDN received the request but did not consider the HTML cacheable. Check whether HTML caching is enabled for public pages. On Cloudflare, static-file caching alone does not cache WordPress HTML. Use APO or a carefully scoped cache rule that excludes admin, login, preview, cart, checkout, account, and session traffic.

    BYPASS

    A cache rule, cookie, or response header told the CDN not to cache the page. Test while logged out and inspect Cache-Control, Set-Cookie, and CDN-specific cache headers. WordPress login and WooCommerce session cookies should bypass the cache. Anonymous public pages should not carry those cookies unnecessarily.

    MISS or EXPIRED on every pass

    The CDN allows caching, but the copy may expire too quickly, be purged between runs, or vary by a header or cookie. Check edge TTL, purge hooks, and the Vary header. A first MISS followed by HIT is normal. Repeated MISS responses across the same locations need investigation.

    Blocked or error responses

    Allow the documented WarmupRocks user agent or custom header through your WAF where appropriate. Do not weaken protection for admin or private routes. A challenge page or 403 response is not cached as a successful warm result.

    When asking for help, include the CDN provider, one public example URL, the cache status shown in warmup.rocks, and the relevant response headers. Remove tokens, cookies, and private URLs before posting.

You must be logged in to reply to this topic.