Websites
Walk through your website on a phone before you launch
A practical mobile review covering real customer tasks, menus, readable content, contact actions and loading behavior.
By Bridge Builder editorial 3 min read
A website shrinking to fit a phone is only the beginning of mobile quality. A visitor still needs to read, compare, navigate and contact the business without fighting the page. Run a task-based walkthrough on an actual phone as well as the developer's responsive preview.
Start with the device your customers are likely to use, then include at least one other screen size. Record the browser and device so a problem can be reproduced rather than described as the mobile site being weird.
In this article
Start where a customer would enter
Do not test only the homepage. Open a service page directly, as someone might from a search result or shared link. Find the service, check the area covered, and follow its inquiry path. Repeat from a page containing a long price explanation or gallery.
Google uses the mobile version of content for indexing and recommends equivalent primary content across mobile and desktop. That makes hiding important service information on small screens a poor shortcut. Rearrange the page and improve its spacing without silently removing the answers a visitor needs.
Use the menu and controls normally
Open the menu, select a destination, return and close it. Check that the page is not permanently stuck behind a layer. Turn the phone sideways if that is a supported orientation. Try the same menu using a keyboard on a computer to expose focus problems that touch alone may miss.
Tap the contact buttons near nearby controls. You should not need exceptional precision to choose the right one. Sticky bars should not cover the final form field, policy text or submission feedback. If a control moves while the page loads, record exactly what loaded before the jump.
Enlarge the content
Increase text size or browser zoom and read a full paragraph. Watch for clipped headings, prices separated from their terms and cards that spill outside the screen. W3C's reflow guidance addresses preserving information and function when content is enlarged; a normal-size screenshot does not demonstrate that.
For a menu, comparison table or detailed image, consider what the visitor actually needs to read. A downloadable file may be useful, but it should not be the only way to access essential information if it is awkward on a phone. Ask the builder to show how the same task works with enlarged text.
Observe loading and the last step
Open the site on a typical mobile connection with a fresh page load. Notice when the main message appears, whether the navigation responds and whether images push content around. Google's Core Web Vitals measure loading, responsiveness and visual stability; use those measurements alongside your observed task, not as a replacement for it.
Finish with a controlled inquiry test when the business has approved the recipient and message. Verify actual receipt and the reply path. For an email link, opening the mail app is only the start: the visitor still has to send the email.
- Record the URL, screen size and task for each failure.
- Fix blocked actions and unreadable content before decorative details.
- Retest the changed page and any shared menu or contact component.
- Keep screenshots of both the problem and the corrected state.
Your next step
Review mobile quality by completing the customer's task. A responsive layout, a screenshot and a performance score each show only part of the experience.