Faith Forge LabsWebsite Speed Optimization
5 MIN READ

Your website is faster, but is it showing old information?

Caching can save time by reusing a response. Make sure new prices, dates, and other corrections still reach visitors when they should.

Identify the content's lifetime

A long-lived illustration and a changing product price have different needs. A service description may change occasionally, while availability can change frequently. List the information that must be current for the customer task.

For a fictional training business, an old course date remaining visible after an update can create confusion. A faster page isn’t enough if the visitor acts on outdated information.

Understand the layers

A browser, content-delivery service and application may each cache something. Clearing one layer may leave another copy in place. The developer should document which layer owns the behavior and how an update invalidates the relevant content.

The MDN HTTP caching guide provides the technical foundation. The project decision is which responses can be reused and for how long under the site's requirements.

The owner sees the holiday hours. What does the customer see?

At noon on Christmas Eve, a bakery is closing for the day. Its owner changed the hours on Monday. On her screen the location page says “December 24: 7 am to noon.” A customer calls just after lunch because his phone says the shop is open until six. Both can be looking at the right address. The useful thing to ask him for is the page he used and where he saw the hours. Sometimes the old time is in the footer, sometimes it's on a search listing the bakery manages elsewhere, and sometimes it's on the very page the owner just checked.

Start with the public website. Keep the owner's editing window open and visit the location page in a separate browser where nobody is signed into the bakery's account. Read the actual hours in both places. A signed-in editor may get a freshly generated preview while a visitor gets a saved copy. If the two disagree, check that the edit was published and that the owner updated the right location. Clearing every cache on the site takes seconds on some systems. Clearing it before you look can also wipe out your best clue.

Now follow that one edit. A bakery might store hours once and show them on a location page, in a banner and beside the pickup choices at checkout. Or those might be three separate entries that someone types by hand. In the second case, changing a cache setting won't fix the underlying problem. I'd have the owner show me how they make the change and keep the three public pages open for comparison. It's a fairly quick way of finding out whether we're looking for an old copy or a second source of hours.

The edit that should set an update in motion

If the hours are entered once, write down which pages need a new copy when that entry changes. The location page is an obvious one. The home page might show all branches today. An old blog post about how the bakery makes its sourdough probably doesn't use the hours at all. On a system that supports targeted invalidation, we can ask it to discard the affected copies as part of publishing the edit. The next visitor can then receive the new information without making everyone who opens a recipe download the same photographs again.

The detail worth checking is who holds each copy. A page saved by the website and a copy at a delivery network may expire separately. Even after those have been updated, a returning customer's browser may reuse an earlier response according to the instructions it received at the time. That's why I'd test a fresh visit and a repeat visit. I want to be able to tell the owner how someone who checked the hours yesterday will fare today.

Try the opposite edit as well. Holiday hours have an end date. If the site says the bakery is closed on Thursday, when, and in whose time zone, should normal hours reappear? A change scheduled for midnight may happen with nobody in the office to press Publish. Check how a saved page gets refreshed in that situation. The same question comes up with a sale price or a notice about a weather closure.

For a performance review, bring one example of information customers have seen too late, along with the place your staff change it. A good result is something the person behind the counter can verify: they make an edit once, a customer can read the correct information in time to use it, and the rest of the site can carry on serving its fast copies.

Test an update, not just a repeat visit

Change a safe representative item in the agreed test environment, then check how a new visitor sees it. Verify relevant regions or provider layers where the setup requires it. Don’t rely only on the developer's already-open browser tab.

Keep personalized pages, carts and account information in the review. Their correctness and privacy requirements can differ sharply from public content. A blanket cache rule needs particular care.

After implementation, compare both a cold request and an appropriate cached request. Explain which experience improved. Keep recovery and cache-clearing instructions available for the team maintaining the site.

For a scoped plan, see website caching. Bring examples of stale content as well as slow pages, because both describe the arrangement the site needs.