Prioritize the slow interaction people actually need
Separate loading, responsiveness and visual stability before choosing a fix. A page can load its hero quickly but freeze when a menu opens, or respond promptly while images push the enquiry button around. Use field data when available and controlled laboratory tests to investigate causes. Record device assumptions, network conditions and page state so a before-and-after comparison remains meaningful.
Worked example
Illustrative scenario; not a claim of measured client results.
Suppose a service page contains a large video above the enquiry form and a long strip of client logos below it. Compare the loading sequence before deciding whether the video, fonts or scripts dominate the delay. Deferring below-the-fold logos may reduce initial work, but lazy-loading the main visual can make the first screen slower. Make one attributable change, then test the same journey again.
Checks, limitations and next decisions
If a score improves while users still struggle, test the task directly: read the offer, open the navigation, complete fields and recover from an error. When field reports show insufficient data, state that limitation instead of treating a lab result as a field pass. Track the specific behavior fixed and keep regression checks for the templates that share the same assets.
A practical starting point
Work through these checks in order. Use the results to decide what needs to change in your own workflow.
- Group measurements by page template and device class.
- Identify whether loading, interaction or visual movement is the main issue.
- Fix the largest repeatable cause and compare measurements under consistent conditions.
A mistake to avoid
Do not compare unrelated test conditions and attribute every score change to one code edit.
How to check progress
Track field data where available and record lab conditions when field data is insufficient.
Your action checklist
Use this checklist while reviewing your own setup. Checkmarks are temporary and stay in this open page.
For the wider decision process, read Diagnosing a page that Google has not indexed.
Further reading
Official background resources for this topic. The workflow above is general guidance, not a guarantee of a particular result.
AI-assisted editorial content. Examples are illustrative, not client case studies. Read our editorial policy or report a correction.