A desktop test on office Wi-Fi can hide the problems customers experience. Use a repeatable mobile test plan.
Choose representative journeys
Test the homepage, a service page, an article and the enquiry route. Include first visits and repeat visits because caching changes behaviour. Record device, browser, connection condition and whether third-party widgets were active.
Combine controlled and real tests
Use throttled laboratory runs to compare releases, then inspect ordinary phones on real connections. Avoid interpreting one weak-signal result as a universal condition. Repeat tests and distinguish network variability from consistently heavy pages or blocked interactions.
Record usable outcomes
Note when content becomes readable, when navigation responds and whether an enquiry completes. Save screenshots or traces for reproducible defects. Prioritise failures that block customer actions before cosmetic differences in a scoring dashboard.