webtoolshelper
Website Tools

Website Cache Checker

See how well browsers and CDNs can cache your site. The checker reads the caching headers of the page and up to 24 of its CSS, JavaScript, font, image and icon files: Cache-Control with max-age, immutable, no-cache and no-store, Expires, ETag and Last-Modified validators and CDN cache-status headers such as cf-cache-status and x-cache. Static files with short or missing cache rules are flagged with the recommended setting.

  • Encrypted connection
  • No sign-up
  • Free to use

How to use Website Cache Checker

  1. Enter the page address.
  2. Click “Check caching”.
  3. Review the flagged files.
  4. Set long cache lifetimes for versioned files.

Website Cache Checker features

Per-resource rules

Cache-Control and Expires.

Validators

ETag and Last-Modified.

CDN status

HIT, MISS, DYNAMIC.

Versioned files

Detected in URLs.

Safe fetching

Public addresses only, with size and time limits.

Clear advice

What each file should use.

When to use Website Cache Checker

  • Fixing “serve static assets with an efficient cache policy”.
  • CDN configuration checks.
  • After deploying a new build.
  • Performance audits.

Website Cache Checker FAQ

How long should static files be cached?

Files whose name changes with each version can be cached for a year: public, max-age=31536000, immutable.

Should HTML be cached?

Usually briefly or with revalidation (no-cache), so visitors see updates.

What do ETag and Last-Modified do?

They let browsers ask “has this changed?” and get a tiny 304 answer instead of the whole file.

What does cf-cache-status: DYNAMIC mean?

Cloudflare did not cache the response, usually because it is HTML.

Cache-Control Header Generator Decide how long browsers and CDNs may keep your files, and get a Cache-Control… Website CDN Checker Find out which content delivery network serves a site. The checker looks at three… Website Compression Checker See whether your server compresses pages and how much it saves. The checker… HTTP Header Checker Look at the headers a server sends before the page itself. Enter a URL to get the…

Caching for speed

Repeat visitors should download almost nothing: long cache lifetimes for versioned files and short ones for HTML give both speed and freshness.

Use the Cache-Control Header Generator to write the right headers.

How it works: our server downloads the page once through a guarded fetcher that only connects to public addresses, follows a limited number of redirects and stops after a size and time limit. The HTML is then analysed in your browser as inert text – scripts on the page never run and nothing is stored.

What it cannot see: content and resources that a page adds with JavaScript after it loads, pages behind a login, and servers that block automated requests. For those, open the page in your browser, use its developer tools, or paste the page source where the tool offers a paste option.

Use the results as a starting point: fix the items marked red first, review the yellow warnings in context, and run the check again after a change. Requests are rate-limited to keep the service fair; if you check many pages in a row, wait a few minutes.

Related checks on this site cover the rest of a technical review – speed and Core Web Vitals, security headers, structured data, accessibility and SEO signals – so you can work through a whole site audit one topic at a time.

Who it is for: site owners checking their own pages, developers debugging a release, SEO and marketing teams auditing clients or competitors, and students learning how the web works. No account or installation is needed, and the results are plain text and tables you can copy into a report or ticket.

Other useful tools