Hi Product Hunt! I built CacheCharger to help answer a simple question: after a cache purge or a content update, are my public pages ready for the next visitor?

A preload on your server can prepare the origin cache, while your CDN cache may still be cold. CacheCharger requests eligible public pages through your CDN, checks the response headers for confirmed HITs, and shows matched before-and-after response-header times where available.

You can import a sitemap, choose important URLs, schedule warming runs, or connect WordPress to queue pages after updates. Pages that bypass the cache get diagnostics so you can see what needs attention.

There is a free plan with three websites and 1,000 warming units per month, with no credit card or CDN API key needed. You can also explore the public demo before connecting a site.

A quick measurement note: results reflect the pages checked and the observed probe location. They are not a measure of full page-load speed or a promise that every CDN location is warm.

I would love feedback on the reports: when a page stays uncached, is the evidence clear enough to help you decide what to fix next?

Hi Product Hunt! I built CacheCharger to help answer a simple question: after a cache purge or a content update, are my public pages ready for the next visitor?

There is a free plan with three websites and 1,000 warming units per month, with no credit card or CDN API key needed. You can also explore the public demo before connecting a site.

A quick measurement note: results reflect the pages checked and the observed probe location. They are not a measure of full page-load speed or a promise that every CDN location is warm.

I would love feedback on the reports: when a page stays uncached, is the evidence clear enough to help you decide what to fix next?

CacheCharger

Preload your CDN cache before visitors arrive

Preload your CDN cache before visitors arrive