A faster repeat visit hides a slow first arrival

What to change

Separate first-arrival and repeat-visit conditions. Ask the supplier to show both using the same representative page and explain which optimisations affect each case. A warm-cache result may be valid for returning users but should not stand in for acquisition traffic. The acceptance evidence should state the cache condition explicitly and include an external fresh-session check after deployment, since local developer caches can hide missing or stale public assets.

A worked example

Illustrative example

Illustrative test: A new browser profile and a returning session open the same guide.

How to check the result

Both experiences are described accurately and the claimed improvement names its relevant condition.

A mistake to avoid

Clearing only one cache layer may not reproduce a genuinely fresh arrival.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordRecord whether each test uses a warm or empty cache.Run matched first-visit and repeat-visit checks.Compare the assets and delays responsible for the difference.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.