This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
CDN caches are per-location: a hit in Frankfurt does nothing for Tokyo. warmup.rocks requests every page of your sitemap from 42 countries, warming 90+ edge locations on any major CDN — with per-location hit-ratio reports that prove it worked.
Hey PH, Kevin here — I built warmup.rocks after my own sites kept showing 600 ms response times from regions I cared about, despite "everything cached at the edge."
The uncomfortable truth: CDN caches are per-location. Your traffic keeps caches warm exactly where your visitors already are — and cold everywhere else, including the US data centers Googlebot crawls from. A crawler or plugin can't fix that from one server.
So this requests every URL of your sitemap from 42 countries, one per edge location, and shows a per-location hit-ratio report to prove it worked.
Fastest way to see if you have this problem: run the free cache checker on your own domain.
Curious what the community thinks — and happy to nerd out on cache keys, tiered caching, or why your cf-cache-status says MISS.
Hit ratio reports sound super useful. One thing i'd love: schedule recurring warmups on a cron so the cache stays primed after deploys or TTLs expire, instead of me remembering to re-trigger it every time.
have been waiting for something like this for ages, the per-location hit ratio reports are a really nice touch. one idea though: let me schedule recurring warmups on a cron basis so my edge stays primed automatically after deploys or content updates instead of having to trigger it manually each time.
the per-location hit ratio reports are genuinely useful, most tools just tell you "yes it's cached" and leave you guessing. ran it on a 200-page sitemap and the dashboard showed exactly which edges were cold
Would love to see a way to exclude URLs with certain query params or regex patterns from the warmup run, some of our paginated/campaign pages just bloat the crawl without adding real cache value.
Ran it on a client site and the per-location report caught a dead zone in Singapore I never would have guessed existed. Worth it just for that visibility.
About warmup.rocks on Product Hunt
“Your cache is cold. Your visitors pay for it.”
warmup.rocks was submitted on Product Hunt and earned 0 upvotes and 10 comments, placing #130 on the daily leaderboard. CDN caches are per-location: a hit in Frankfurt does nothing for Tokyo. warmup.rocks requests every page of your sitemap from 42 countries, warming 90+ edge locations on any major CDN — with per-location hit-ratio reports that prove it worked.
warmup.rocks was featured in SEO (37.9k followers), SaaS (43.3k followers) and Developer Tools (516.3k followers) on Product Hunt. Together, these topics include over 136.9k products, making this a competitive space to launch in.
Who hunted warmup.rocks?
warmup.rocks was hunted by Kevin Kyburz. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how warmup.rocks stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Kevin Kyburz
Hey PH, Kevin here — I built warmup.rocks after my own sites kept showing 600 ms response times from regions I cared about, despite "everything cached at the edge."
The uncomfortable truth: CDN caches are per-location. Your traffic keeps caches warm exactly where your visitors already are — and cold everywhere else, including the US data centers Googlebot crawls from. A crawler or plugin can't fix that from one server.
So this requests every URL of your sitemap from 42 countries, one per edge location, and shows a per-location hit-ratio report to prove it worked.
Fastest way to see if you have this problem: run the free cache checker on your own domain.
Curious what the community thinks — and happy to nerd out on cache keys, tiered caching, or why your cf-cache-status says MISS.