Mobile
How the page behaves on a phone
The mobile run loads the page at a phone viewport on a throttled connection and reports what breaks: text too small to read, tap targets too close together, content wider than the screen, and how long any of it takes to arrive.
Three audits every 24 hours with a free account. No card, and nothing switches off.
What it measures
Checked on every run
Most visitors arrive on a phone, on mobile data, often outdoors. A site that is tested on a desktop on office wifi has never been seen the way most of its audience sees it.
Viewport and overflow
Whether the page declares a viewport at all, and whether anything on it is wider than the screen — the cause of that sideways scroll that makes a page feel broken.
Tap targets and legibility
Buttons and links too small or too close to hit reliably, and text below a readable size.
Performance
Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift and Speed Index — the lab versions of the Core Web Vitals Google ranks on, measured on a simulated mid-range phone and on a desktop.
Accessibility
Colour contrast, form labels, heading order, alt text, landmark structure and keyboard reachability — the automated half of WCAG, which is roughly a third of what a real audit covers and all of what a machine can check.
How it works
Three steps, about ninety seconds
Paste the address
Any public page. The engine resolves it, follows redirects and reports where it ended up.
It loads the page twice
Once at a phone viewport on a throttled connection, once on a desktop, in a real browser — not a lookup against a database of old crawls.
You get numbers, ranked
Four scores, the measurement behind each, and the problems in the order they are costing you. Results stay in your dashboard, so a re-run shows what moved.
Questions
What this does, and what it does not
- Is this the same as Google’s mobile-friendly test?
- It covers the same ground and then some — Google retired that tool, and this measures the layout checks it made plus the performance the page actually delivers on a phone. It is a lab simulation, not a device lab: it will not catch a bug specific to one browser on one handset.
- My site is responsive. Do I still need this?
- Responsive is a layout property and most of what goes wrong on a phone is not layout. A responsive page can still ship 4MB of desktop imagery, block the main thread for two seconds and put two buttons 6px apart. Those are what the mobile run measures.
- How does the audit actually run?
- We load the page in a real browser twice — once on a simulated mid-range phone on a slow connection, once on a desktop — and record what happens. Nothing is estimated from a database of past crawls; every number comes from that load, on the day you asked for it.
- Is it free?
- Yes. Three audits every 24 hours with a free account, which exists so the engine is not run by scripts. There is no card, no trial, and nothing switches off.
Measure it now
One address, ninety seconds, and a list you can hand to whoever builds the site. If the list turns out to be longer than an afternoon, that is a conversation we are happy to have.