Build
How to test a website on a real phone
Open the site on an actual mid-range phone over mobile data, not on desktop Chrome resized. Emulation gets the layout right and everything else wrong — touch accuracy, real network latency, and how the device actually performs.
Before you start
- A real phone, ideally a mid-range Android
- Mobile data rather than home wifi
The steps
-
Step 1: Use a mid-range device
Not the newest flagship. Most visitors are two or three years behind, and that is the experience that matters.
-
Step 2: Turn off wifi
Test on mobile data. Latency and variability are what real visitors have.
-
Step 3: Load the home page and time it
By feel. If you notice waiting, so does everyone else.
-
Step 4: Tap every interactive element
Targets should be at least 24 by 24 CSS pixels with adequate spacing.
-
Step 5: Complete a form
Confirm the right keyboard appears for each field type and that the submit button is not hidden behind it.
-
Step 6: Rotate the device
Landscape breaks layouts that were only ever checked in portrait.
-
Step 7: Test with one hand
Can the main action be reached with a thumb, or is it in the top corner.
-
Step 8: Check in bright light
Low-contrast text that looks refined on a monitor is unreadable outdoors.
What emulation cannot show you
Real CPU throttling, real network variability, real touch precision, and how the on-screen keyboard covers your form. DevTools device mode is a layout tool, not a testing environment.
Why the mid-range device matters
A recent flagship hides performance problems entirely. A three-year-old mid-range Android on mobile data is closer to the median visitor, and it surfaces the problems your analytics show as bounces.
The background behind this
Core Web Vitals, and the order that actually reduces them covers the reasoning in about 3 minutes — free, ungated, written from client work.
Who wrote this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada, Ireland and Pakistan. These procedures are the ones I run on client work, written down rather than invented — including the ones where the honest answer is that the fix is not available on your current hosting.