Test first and repeat visits on representative pages
Find out when the slow experience happens.
Use this for: The representative public pages selected for this review.
Choose important landing-page templates and run a mobile and desktop diagnostic where each matters. In browser developer tools, open Network before reloading to see the document and resource requests. Start with a controlled first-visit test, then compare a normal repeat visit with caching enabled.
Keep the URL, test mode, network setting and page state comparable. A warm browser cache can hide a slow first visit, while an always-disabled cache cannot show whether repeat visits benefit from reuse. Do not treat one fluctuating performance score as the entire result.
Hypothetical example: A service page is quick on the owner’s laptop after many visits but slow on a fresh load because its large images have never been cached.
- Choose URLs across the important templates.
- Compare controlled first-visit and normal repeat-visit behavior.
- Keep the setup consistent for later tests.
More help and optional notes
If it fails: Repeat the missing visit state before selecting a fix.
Retest: Reuse the same baseline after implementation.
Not applicable: No pages or features in the stated scope require this check.
Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

