Skip to main content
Apply for a Cheap Website
Website explainer · 1:47

Website Caching Explained: Why You Might See an Old Page

Changed a page but still see the old one? A saved copy may be part of the answer.

Jersey Web video: Why is the old page there?

1:47 · No narration: the video shows each step as text on screen, and every step is written out below, with buttons that jump the video to it.

Download the on-screen text track (VTT)

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

  1. Step 1: A cache stores a copy

    Reusing a response can save another download.

    On-screen labels: Saved response; Fewer repeat requests; Faster repeat visits.

  2. Step 2: Copies can live in several places

    Your browser and a delivery network may both cache files.

    On-screen labels: Browser cache; Shared cache; Website origin.

  3. Step 3: Freshness has a time limit

    Cache rules tell services when a copy needs checking.

    On-screen labels: Fresh copy; Expiry time; Revalidation.

  4. Step 4: An update may need a purge

    Ask your developer which shared cache needs refreshing.

    On-screen labels: Publish the change; Refresh shared copies; Check again.

  5. Step 5: Private pages need care

    Personal responses must not be shared with other visitors.

    On-screen labels: Account pages; Personal information; Correct cache rules.

  6. Step 6: Compare a fresh visit

    Test another browser before assuming the update failed.

    On-screen labels: New browser session; Correct page address; Confirm with your developer.

A practical check for your business

When a changed page still looks old, record the exact URL and where it was checked before changing cache settings. Compare the public result with the intended version. Ask which layer supplies the saved copy and how that layer is refreshed.

Sources and further detail

See it in a diagram

Diagram showing a visitor browser, a shared cache and the website origin, with a note about suitable caching for private account content.
Website caching, at a glance. Public content can be reused; private responses need suitable cache rules.
Read the diagram as text
  1. Visitor browser: A local saved copy
  2. Shared cache: Reusable public content
  3. Website origin: The original response

Changed a page?. Check which cache needs refreshing.

Private account content needs controlled caching.

Diagram by Jersey Web. Open full size · Source and further detail (opens in a new tab)

Common questions

Changed a page but still see the old one?

A saved copy may be part of the answer. Check which copy your visitors receive.

Go further

Guide Read the practical guide More context for planning and maintaining your business website. 5 min read → Jargon Buster Cache explained Read the related Jargon Buster explanation. Read the explanation →

Check which copy your visitors receive.

Tell Jersey Web what your website needs to do and which part you want help with.

Talk to Jersey Web →

More video tips

All 205 videos →
Length 1:47 Website performance

What Is a CDN? Website Content Delivery Explained

A shorter delivery route. Length 1:47 Website performance

JPEG, PNG, WebP or AVIF? Choosing Website Image Formats

Choose for the image. Length 1:47 Website performance

Responsive Images Explained: Better Photos on Small Screens

Send a suitable image size.