Mobile friendly test
Check what your site does on a phone-sized screen and a slow connection, where most of your visitors already are. One URL, no account.
The free run measures what a mobile client receives. Viewport and tap-target checks need a browser, so they start on a monitored site.
What mobile friendly actually means here
Not whether it is responsive — almost everything is. Whether it is usable: text you can read without pinching, buttons a thumb can hit, nothing sliding sideways, and a page weight that survives a connection with one bar. Those are four separate failures with four separate fixes.
- Tap targets
Interactive elements under 44px, or too close to their neighbours.
- Horizontal overflow
The single element that makes the whole page slide sideways.
- Legible text
Body text under 16px, and viewport settings that block zooming.
- Weight on a slow link
What the page costs on a throttled mobile connection.
What a result looks like
Both in the sticky filter bar.
Nothing slides sideways at 360px.
Against 4.1s on the same page over broadband.
Each finding names the element and the screen width where it fails, with the rule that caused it. There is no mobile score, because a site can be perfectly responsive and still have a checkout button under a cookie banner.
A test tells you about today. Monitoring tells you at 04:00.
Mobile breaks in the places nobody reviews on a phone: a promotion banner overlaps the buy button, a new filter bar shrinks the tap targets, a font change pushes a form off-screen. Testing on every release catches it before the traffic that pays your bills meets it.
Common questions
- Is this the same engine as the paid monitoring?
- Yes — the same checks, run the same way. The difference is that monitoring repeats them on a schedule and keeps the history, which is what turns a number into a trend and a trend into an alert.
- Does testing my site slow it down or change anything?
- No. Everything is read from the outside, the way a visitor arrives — no agent, no script on your pages, nothing written. Our requests identify themselves so you can recognise them in your own logs.
- Which device does it emulate?
- A common mid-range phone viewport on a throttled connection — deliberately not the newest flagship. Testing on the best hardware your team owns is how mobile problems survive to production.
Related tests
A free test is a snapshot. Monitoring is the product.