Mobile Usability on Real Phones
A layout that works on a large monitor can hide the main action, shrink tap targets or turn a simple form into a struggle on a phone. We test your key tasks on real devices and explain what to change.
Short answer
A mobile usability review checks your key tasks on real phones for tap target size, form input, menus, layout at narrow widths, speed and layout shifts. It can include sessions with participants on their own phones. You receive ranked findings with screenshots and fixes.
On this page
Why mobile needs its own review
Phones change how people use a site. Screens are narrow, fingers are less precise than a mouse pointer, connections vary and people are often interrupted. A design reviewed only on a desktop can pass every check there and still fail on a phone, because the menu collapses into an icon nobody notices, the sticky banner covers the form button or the on-screen keyboard hides the error message.
Google also changed how it reports on mobile issues. In December 2023, Google retired the Mobile Usability report in Search Console, the Mobile-Friendly Test tool and its API, and pointed site owners to Lighthouse instead 1. Automated tools remain useful for speed and technical checks, but they cannot tell you whether a person can complete a task comfortably.
What we check
| Area | What we look for |
|---|---|
| Tap targets | Targets at least 24 by 24 CSS pixels or with enough spacing, as WCAG 2.2 Target Size (Minimum) requires, and larger targets for primary actions |
| Layout | No sideways scrolling at 320 CSS pixels wide, readable text without zooming, nothing important hidden off screen |
| Navigation | Menus that are easy to open, read and close, with the current location clear; structural problems go to information architecture research |
| Forms | Correct input types for email, phone and numbers, labels that stay visible, errors visible above the keyboard |
| Overlays | Cookie banners, chat widgets and pop-ups that do not block the task |
| Speed and stability | Loading, responsiveness and layout shifts measured against Core Web Vitals thresholds |
| Gestures | No task that depends on dragging or precise gestures without a simple alternative |
The target size requirement comes from WCAG 2.2 success criterion 2.5.8, which sets a minimum of 24 by 24 CSS pixels with exceptions for spacing, equivalent controls, inline links, user agent defaults and essential cases 2.
How the review works
A reviewer completes each task on a small set of real phones covering common screen sizes, both major mobile operating systems and at least one older or lower-powered device. We record the screen during each task so that findings come with clear evidence. When the scope includes participants, they use their own phones, which shows how the site behaves with real settings such as larger text sizes.
Speed and stability are checked with field data from your analytics or the Chrome UX Report where available, and with lab tools where it is not. Our Core Web Vitals guide explains the thresholds and why field data matters.
What you receive
A ranked findings report with screenshots or short recordings from real devices, the device and browser for each finding, severity, and a specific fix. Where a problem appears only on certain devices, we say which. A short summary lists the changes to make first.
Timeline
We plan for one to two weeks for an expert review of key tasks on real devices, and three to five weeks when the scope includes recruited participants.
Common mobile problems worth checking first
If you want to start before commissioning a review, check three things on your own phone. Open your most important form and try to complete it with one thumb while standing; note any field where the keyboard hides what you are typing or the error message. Load your home page on a slow connection and watch whether anything jumps as it loads. Then open the menu and try to find your pricing or contact page without scrolling past it. Each of these checks takes minutes and can expose serious problems.
Mobile review questions
Do you test on both iPhone and Android?
Yes. We cover both major mobile platforms and a range of screen sizes. If your analytics show a dominant device or browser, we weight the review toward it.
Is a responsive design enough?
Responsive layout is a starting point. A site can resize correctly and still have small targets, hidden actions or forms that fight the on-screen keyboard. The review checks the experience, not just the layout.
Do you review mobile apps?
Our focus is websites viewed on phones, including web apps. We can review a native app for usability, but we do not test app store submission requirements.
Sources
- Google officially drops Mobile Usability report, Mobile-Friendly Test tool and Mobile-Friendly Test API, Search Engine Land (Barry Schwartz), December 2023.Secondary source, industry news
- Understanding Success Criterion 2.5.8: Target Size (Minimum), W3C Web Accessibility Initiative, checked November 3, 2026.Primary, standards body
Have a page that should work better than it does?
Send the address and a sentence about what worries you. You get questions back, then a fixed-fee quote in US dollars.
- No obligation
- Written scope
- Plain-English findings