Find the failed task before choosing a redesign
A desktop screen gives a page more room than a phone. Fixed-width layouts, oversized media, overlapping banners and crowded controls can make an otherwise attractive site difficult to use. Start by recording what a visitor cannot do. A screenshot of a tidy homepage is not proof that its menu, form or checkout works.
Run this five-step phone check
First, open the page on a real phone as a visitor, not as an administrator. Read the main heading and first paragraph at your normal settings. Second, enlarge the text or zoom and check that information is not hidden or covered. Do not solve a layout issue by preventing visitors from zooming.
Third, check whether ordinary text requires sideways scrolling. W3C’s reflow guidance describes preserving information and function at narrow equivalent widths, with exceptions for content such as maps or tables that genuinely needs two-dimensional layout. A single width test is not a complete accessibility audit.
Fourth, use the menu and important buttons by touch. Watch for accidental taps on a neighbouring control. W3C’s target-size guidance explains minimum size and spacing rules, including exceptions; larger well-spaced controls can make important tasks easier.
Fifth, complete a real visitor task: find the correct service, read the instructions and use the intended contact route. For a test enquiry, identify it as a test and use authorized test information. Do not place orders or submit real customer data just to see what happens.
Write a useful fault report
Record the page URL, device and browser, the action you tried, what you expected, and what happened. For example: “On my phone, the menu opens but the quote link is covered by the cookie banner.” That is more actionable than “make it mobile-friendly.”
Fictional example: a contractor’s four desktop service cards stay side by side on a narrow screen. A stacked layout may help, but the editor must also test the actual contact button and content order. A layout change alone does not prove the whole journey is fixed.
Retest without removing the useful content
Fix the most important failed task first, then repeat the same steps. Include keyboard and assistive-technology testing in the broader review. Browser emulation is useful for development, but it does not replace checking touch behaviour on real devices. Keep the before-and-after observations so the team knows what improved.
Explore CLM Studio guides.

