Run a Repeatable Website Speed Check

A useful speed check records the URL, device assumptions and test conditions, then investigates the largest bottleneck. It should help you choose and verify a change rather than turn a single performance score into a judgment about every visitor.

Establish a baseline

Choose a representative URL and record when it was tested. Note mobile or desktop configuration, redirects and whether the run encountered a cookie dialog or unusual content. Repeat comparable lab runs to understand variability. Check whether field measurements are available and whether they apply to the page or a wider origin.

Read the report in order

1. Confirm that the expected page actually loaded.
2. Identify the main content element and investigate its request path.
3. Review script execution, render-blocking work and layout changes.
4. Exercise an important interaction in a browser instead of assuming the load test measured it.
5. Separate unavailable data from measured zero values.

Total Blocking Time can help diagnose main-thread load work, but it is not INP. A high Lighthouse score does not certify field Core Web Vitals, conversion performance or search ranking.

Worked example: mobile and desktop disagree

Suppose desktop appears fast while a mobile lab run loads a large product image late. Compare the selected image resource, device settings and connection assumptions. Test appropriately sized responsive images, then rerun the same mobile configuration. Check image quality and layout dimensions as well as timing. The example describes a test design, not a promise of a specific improvement.

Keep a change log

Record the deployed change, before and after measurements, and whether the affected user journey still works. Avoid combining unrelated changes if you want to understand what caused the result. Field reports can take time to reflect new visits; immediate lab improvements and later field outcomes should be reported separately.

Start a Speed Checker run, then use browser performance tooling for deeper diagnosis. See PageSpeed Insights documentation for what the service measures.