Your existing preload
Prepares HTML on your server.
Preload your CDN cache so visitors can get your pages faster.
Warm important URLs, confirm cache hits, and see the difference in response time.
/MISSHIT/articles/a-better-first-visitMISSHIT/aboutHITHITWarm eligible public pages through your existing CDN. We confirm hits when its response headers expose cache status.
Your preload plugin can prepare pages on your server. Your CDN has its own cache, which can still be empty after a purge, a new publication, or expiry. CacheCharger helps prepare that next layer.
Prepares HTML on your server.
Your public pages. Prepared at the edge.
More conversions. Stronger revenue. Fewer visitors leaving. Published performance studies show why it is worth making every first response count.
The performance-optimised version also delivered 53.37% more revenue per visitor.
Read the studyAfter a three-month project that reduced average load time by 23%.
Read the studyWith nearly fourfold better INP, alongside 43% more pageviews.
Read the studyNine published studies covering sales, revenue, bounce, order value and engagement.
31% better Largest Contentful Paint (LCP).
+8% sales · +15% lead-to-visit rate · +11% cart-to-visit rate.
Core Web Vitals work; mobile test page loaded 0.4 seconds earlier.
+33.13% conversions · +53.37% revenue per visitor · +15.20% average order value · −35.12% exit rate.
23% lower average load time and 55% better LCP over a three-month performance project.
+42% mobile revenue. Mobile-to-desktop conversion ratio rose from 24% to 34% (10 percentage points).
Compared LCP with conversion and bounce across its landing-page data.
A 1-second LCP improvement was associated with +13% conversions around 1-second LCP; −14 percentage points in bounce below 1.6-second LCP, versus −5 points above it.
Interaction to Next Paint (INP) improved nearly fourfold, alongside a migration to Next.js.
−50% bounce rate · +43% pageviews on topic pages.
Reduced interaction delays; one input-state optimisation improved page INP by 72%.
+7% overall sales after the wider INP improvement project.
Browser article prefetching: LCP −51% mobile / −73% desktop; TTFB −83% / −84%.
Ad click-through rate +11% mobile / +30% desktop; ad viewability +10.5% / +6%. This tested browser prefetching, a separate technique from CDN warming.
Observed a natural 0.1-second improvement in mobile site speed over four weeks.
Retail: +8.4% conversions and +9.2% average order value. Travel: +10.1% conversions. Luxury: +8.6% pageviews/session. Lead-gen information pages: 8.3% better bounce rate.
Compared mobile page-load times of 1 and 3 seconds.
32% higher predicted bounce probability at 3 seconds. A modelled relationship, not a measured CacheCharger uplift.
These are case-specific, company-reported results and research models—not CacheCharger results or a forecast. The projects improved broader page performance; CDN warming is one part of that picture. CacheCharger measures response-header time and cache evidence, not full page-load speed or revenue.
Connect a website you own and start with its important public pages. Your first report shows confirmed hits, observed waiting time, and the pages that need attention.
Get my free cache report No card. No CDN API key. Ownership verification required.Use DNS, a verification file, or the WordPress connector.
Choose URLs or import a sitemap. Sensitive pages stay excluded.
Before and after observations, with clear next steps.
Before your visitors arrive.
A download isn’t proof of a hit.
Catch changes that need attention.
Your CDN cache warmer should do more than visit URLs.
It should tell you whether those visits helped.
Verify ownership, then discover your public pages from a sitemap or add the URLs that matter.
We request eligible public pages through your CDN, verify cache headers, and report before-and-after response times where comparable.
Set a schedule, connect WordPress updates, and review the pages that need a closer look.
/articles/your-latest-postThis response is bypassing the cache.
Review its cache directives and cookies.
cf-cache-status: BYPASS
cache-control: privateA green “crawl complete” message only tells half the story. CacheCharger separates confirmed hits from uncached, blocked, and unsuccessful requests.
Start with the pages that matter. Warm on a schedule or after published content changes, with sensible limits that protect your origin.
Meet the WordPress connectorWe request your public pages, then check the CDN’s response headers for a confirmed HIT. Eligible misses get up to two follow-up checks. If a page stays uncached, is blocked, or bypasses the cache, the report explains what needs attention. We stop there rather than repeatedly hitting your server. Cache rules, expiry and CDN location still determine which visitors receive a HIT.
Free account. Three websites. 1,000 warming units per month.