
Checking a mobile website through a real task
Open the page on a phone and try to do what visitors actually came for.
Read storyConnect each comment to the visitor’s task and distinguish required fixes from personal preferences.

“Something feels wrong” describes a feeling but does not help choose an action. Useful feedback includes an observation, its consequence and the intended result. For example: “The enquiry button gets lost among the links, so a visitor may not understand the next step; the primary action needs to stand out.”
Return to the page’s purpose and audience. If the task is to help someone choose a service, assess whether differences and terms are clear. For a long article, examine readability and navigation. Do not apply advertising-banner criteria to editorial content without explaining why.
Ask the designer to show the solution in context: adjacent sections, the mobile version and a state with longer text. An isolated fragment may look empty even though it provides a necessary pause in the complete page.
A misspelt name, an inaccessible button and a preferred shade carry different weight. Mark what must be fixed, what needs discussion and what can be tested later. Resolve conflicting opinions within the team before sending them to the contractor.
Suggesting an option can help, but you do not have to dictate each element’s exact position. Let the designer explain the trade-off behind the current solution. After the revision, repeat the original user scenario. If the problem no longer occurs, record the decision so the next review does not reopen it without a new reason.