Ask for website speed reports you can compare

What this means for your practice

Ask the supplier to compare the same pages under clearly described conditions. Discuss controlled tests alongside actual visitor experience where available, and connect each proposed fix to a problem people encounter.

A practical example

For example, a homepage tested on a fast desktop connection is not a useful before-and-after comparison for a service page on a slower phone. Ask for the same page and conditions, with an explanation of what changed. Where information about actual visits is available, discuss it alongside the controlled test. A good report helps you decide whether a proposed fix improves an important task and whether a new problem needs attention.

Ask the supplier to translate the findings into priorities. Which problem affects an important task, what is the proposed fix and how will improvement be checked? This keeps the report useful to the practice rather than leaving staff to choose between technical measurements they cannot interpret confidently.

Make this improvement work

Agree the pages, device assumptions and connection conditions used for comparisons. Ask the supplier to explain material variation between repeated tests rather than select only the best result. Controlled checks and actual visitor observations can answer different questions, so identify what evidence supports each recommendation. Connect a proposed fix with the part of the journey it should improve, such as opening a service page or completing a form. Keep a record of significant changes made between measurements. This lets the practice assess progress from comparable evidence without treating a single headline score as a complete description of everyone's experience.

How to check the result

Track confirmed problems introduced by a change rather than isolated score changes.