Supported CDNs and cache requirements

  • Plugin Author Kevin Kyburz (@swissky)

    (@swissky)


    1 day, 21 hours ago

    warmup.rocks can warm public pages behind Cloudflare, Amazon CloudFront, Fastly, Akamai, bunny.net, CDN77, and other CDNs. Detailed provider and edge reporting depends on the response headers returned by the CDN.

    The important requirement is that your CDN must already allow public HTML to be cached. The plugin does not change cache headers or create cache rules.

    For WordPress sites:

    * Keep WP Rocket, LiteSpeed Cache, W3 Total Cache, or another page-cache plugin enabled if you use one. It warms the origin page cache. warmup.rocks handles the separate CDN edge cache.
    * Cloudflare users can use APO or a safe HTML cache rule. A response that remains DYNAMIC or BYPASS cannot become a cache HIT through warming alone.
    * WooCommerce cart, checkout, account, and logged-in responses must remain excluded from CDN caching. Public product and category pages can be warmed.
    * Private, preview, admin, and no-store responses should not be cached or warmed.

    A successful request does not always mean a cache HIT. The dashboard records the status the CDN actually returned, including HIT, MISS, EXPIRED, BYPASS, and DYNAMIC.

You must be logged in to reply to this topic.