how do i test my site on a phone i don't own?

web · 2026-09-08 · 3 min

two steps. chrome devtools device mode for the layout, and one real phone for everything else. device mode shows you where things break. it cannot show you how the page feels in a hand, with a keyboard open and a thumb over half the screen.

the mistake is testing at 375 pixels wide on a laptop, deciding it looks fine, and never opening the site on a phone on mobile data.

device mode, honestly

in chrome: right click, inspect, the phone icon, then set the width to 360 and 390 and reload. check three things. does the page scroll sideways, which means something is wider than the screen. is there text you have to zoom to read. are there buttons closer together than a fingertip.

the throttling menu simulates a network, not a phone: a slow connection is not a slow processor. firefox and safari have the same tool; safari's responsive mode is the closest thing to ios rendering you get on a desktop.

the real phone, ten minutes

open the site on your own phone, on mobile data, not office wifi. then, in order: tap every button, fill the contact form and send it, tap the phone number and see if it dials, open and close the menu, dismiss the cookie banner, rotate the phone, and try to understand the first screen without scrolling.

the keyboard is the test people forget. tap the email field and look at whether the field is still visible above the keyboard, or whether the page has scrolled somewhere useless.

which devices, and how many

look at your analytics before buying anything. most small italian sites see a mix of iphone and mid-range android. you do not need all of them. test on the oldest phone in the house and on the newest; if the page works on both, it works for most people in between.

for a specific bug, borrow the device. a friend's phone is a better lab than a service, because you can watch the person use the site.

faq

is device mode enough?

for layout, almost always. for touch, the keyboard, autoplay, pdf downloads and safari quirks, no. treat it as a first pass, not as a test.

do i need an iphone to test?

only if your visitors use them, which in italy is likely. safari on ios is a different engine from chrome on android, and some bugs exist only there. borrow one for an afternoon before launch.

how do i test speed on mobile?

pagespeed insights has a mobile tab and measures with a simulated slow connection. lighthouse in devtools does the same locally. then load the page on a real phone on mobile data and count to three. more on this here.