How do you find mobile usability problems?
Test on a real phone, on mobile data rather than office wifi, outdoors, one-handed — a browser's responsive preview shows a narrow layout but not a slow processor, a fingertip or sunlight. Then throttle the network and CPU in developer tools and reload.
Test on a real device, throttled
A browser's responsive preview shows you the layout at a narrow width. It does not show you a slow processor, a poor connection, a fingertip instead of a cursor, or sunlight on the screen.
The minimum honest test:
- Your own phone, on mobile data, not office wifi
- An older, cheaper Android device if you can borrow one
- Outdoors, in daylight
- One-handed, while walking
That last condition is not a joke. A significant share of local service searches happen from a vehicle or a driveway, and a layout that needs two hands and full attention fails there.
Throttle in the browser as a second pass
Device tools let you simulate a slower network and a slower processor. Set the network to a mid-tier mobile profile and the CPU to a four-times slowdown, then reload. Sites that feel instant on a desktop routinely take eight seconds under those settings, and that is closer to what a real visitor gets.
Check what Search Console reports
Page experience and crawl reporting flag mobile problems at scale and group them by URL pattern, which tells you whether an issue is on one page or on a template used by two hundred.
The grouping matters more than the individual URLs. Fixing a template fixes everything it generates.
Walk the actual journeys
Do not just look at the homepage. Complete the things a customer does:
- Find the phone number from a service page and tap it
- Fill in the contact form, on the phone, with the on-screen keyboard
- Find your opening hours
- Get directions
- Read a price
Each one either works in a few taps or it does not. Time them. Anything taking more than about fifteen seconds is worth fixing.
Watch what real visitors do
Analytics tells you where mobile visitors leave. Compare mobile and desktop:
- Bounce rate by device on the same pages
- Conversion rate by device
- Pages where mobile sessions end disproportionately
A page converting well on desktop and poorly on mobile has a mobile problem, and that comparison localises it faster than any tool.
Ask people who use it
For a Greater Houston business, the cheapest research available is asking three customers to find something on your site while you watch and stay quiet. It takes twenty minutes and it consistently finds problems that no automated report surfaces — a button nobody recognised as a button, a menu nobody could find, a form field that rejected their phone number format.
Prioritise by traffic and by task
Fix in this order:
- Anything blocking a call or an enquiry
- Problems on your highest-traffic pages
- Problems on templates generating many pages
- Everything else
A broken layout on a page nobody visits can wait. A phone number that will not tap cannot.
Then re-test
Mobile problems reappear with every release, particularly after theme updates and plugin changes. Put a short device check into your routine after any deployment — five minutes on a real phone catches most of what breaks.
Frequently asked questions
Is a browser's responsive preview enough?
No. It shows a narrow layout but not a slow processor, a poor connection, a fingertip instead of a cursor, or sunlight on the screen. Test on a real phone, on mobile data, outdoors.
How should I throttle for testing?
Set the network to a mid-tier mobile profile and the CPU to a four-times slowdown, then reload. Sites that feel instant on a desktop routinely take eight seconds under those conditions.
What should I test besides the homepage?
The actual journeys — finding and tapping the phone number from a service page, filling the contact form with an on-screen keyboard, finding hours, getting directions, reading a price. Time each one.
How do I tell a mobile problem from a general one?
Compare bounce and conversion rates by device on the same pages. A page that converts well on desktop and poorly on mobile has a mobile problem, and that comparison localises it faster than any tool.
What is the cheapest research available?
Asking three customers to find something on your site while you watch and stay quiet. Twenty minutes, and it consistently finds problems no automated report surfaces.