Mobile-Friendly Test
Fetch a live URL and check it against the mobile-usability red flags that used to fail Google's own Mobile-Friendly Test: a missing viewport tag, illegibly small text, tap targets packed too close together, content wider than the screen, and legacy Flash/Silverlight embeds.
Input
The page's HTML is fetched server-side and scanned for mobile-usability red flags.
Output
| Category | Result | Details |
|---|---|---|
| No data yet | ||
| Severity | Category | Issue |
|---|---|---|
| No data yet | ||
More ways to use this tool
REST API
curl -X POST https://api.iotools.cloud/v1/tool/mobile-friendly-test \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/"
}'Swap in your own key from your account. The tool's fields are the body — no wrapper.
Ask an AI agent
Use the IOTools `mobile-friendly-test` tool (Mobile-Friendly Test) on this input:
YOUR_INPUT_HEREPaste this at any agent connected to the IOTools MCP server, then add your input.
| Cost per API/MCP call | From 5 credits |
|---|---|
| Need more credits? | View pricing |
Also available with
Guides
What the Mobile-Friendly Test does
Enter a live URL and this tool fetches its HTML server-side and scans it for the mobile-usability red flags that used to fail Google's own Mobile-Friendly Test tool: a missing or misconfigured viewport, text declared too small to read, clickable elements sized or spaced too tightly to tap reliably, content wider than the screen, and legacy Flash/Silverlight embeds that don't run on any mobile browser today.
How to use it
- Enter the full URL of the page you want to check.
- Click Test mobile-friendliness. The page is fetched server-side (cross-origin HTML can't be read from the browser).
- Review the Checks table for a pass/fail per category, and the Issues found table for the specific markup that triggered each fail.
What gets checked
- Viewport not configured (error if missing, warning if misconfigured) — no
<meta name="viewport">tag, or one that's missingwidth=device-width, means the page renders at desktop width and gets scaled down instead of laid out for the screen. A viewport that disables pinch-zoom is flagged separately as an accessibility issue. - Text too small to read (warning) — any
font-sizedeclared under 12px in an inlinestyleattribute or a<style>block. - Clickable elements too close together (warning) —
<a>/<button>elements with an inline width or height under 24px, below the ~48px tap-target size Google recommends. - Content wider than screen (warning) —
<div>,<table>,<img>, or<iframe>elements with a fixed width (inline style or a legacywidthattribute) over 480px, a common trigger for horizontal scrolling on phones. - Uses incompatible plugins (error) —
<object>/<embed>tags pointing at Flash (.swf) or Silverlight (.xap) content.
Scope — this is a static-markup checker, not a headless browser
Every check here reads the fetched HTML and its inline/embedded CSS directly — there's no rendering engine computing actual layout, so cascaded stylesheets, external CSS files, media queries, and JavaScript-driven DOM changes aren't accounted for. That means it will miss issues that only appear after the full CSS cascade resolves, and it can flag a false positive on markup that's overridden by a stylesheet it doesn't fetch. Treat a "Fail" here as "worth checking in a real browser," not a final verdict — for that, use Chrome DevTools' device toolbar or a Lighthouse mobile audit, which are what Google itself now points people to since retiring its own Mobile-Friendly Test tool.
Privacy
The URL is fetched by our server only to scan its markup and isn't stored. Requests to private or local network addresses are blocked.