A Mobile Website Review That Follows the Whole Task

Choose the device conditions that matter

Start with the audience and the task: reading an article, comparing plans, booking an appointment, or uploading a file each creates different constraints. Test the supported viewport range and a real touch device when available. Browser emulation helps inspect layout but does not reproduce every device, keyboard, network, or assistive technology behavior.

Follow the task from entry to completion

Open the page from a realistic entry point, use the navigation, scroll the content, and complete the key action. Observe whether a sticky header hides context, a dialog traps the screen, a form is obscured by the software keyboard, or a confirmation is easy to miss. Record the steps and viewport instead of writing “mobile is broken.”

Example: the keyboard changes the form

Imagine a visitor choosing an appointment time on a narrow phone. The page looks fine before they type, but opening the keyboard covers the submit button and the selected time. Record the device, browser, viewport, field, and scroll position; then try dismissing the keyboard and continuing. That evidence points to a specific state transition to investigate, rather than a vague request to make the mobile layout smaller. This is an illustrative scenario, not a claim about a tested site.

Inspect responsive changes, not just dimensions

• Does content keep its intended reading order when columns stack?
• Can users reach important actions without sideways scrolling or accidental overlays?
• Do images and charts preserve the information they communicate?
• Do text zoom and browser zoom keep content and controls available?
• Are loading, empty, error, and success states usable on the smaller screen?

Check input and interaction

Try opening and dismissing menus, selecting controls, entering longer values, and recovering from errors. Check that focus remains visible and the current step is clear. On a touch device, tap size and spacing matter because an adjacent control can be activated accidentally; keyboard access still needs a separate pass.

If the site claims to support a particular device or browser, include it in the review. Otherwise, report exactly what you tested rather than implying broad compatibility.

Report the environment with the finding

Include device or emulator, browser, viewport, orientation, zoom, starting URL, and steps. A short recording can help with movement or timing; a screenshot can show clipping. Neither replaces the steps needed to reproduce the issue.