Enter a URL to see the page as an iPhone renders it, plus a check of the issues that make sites hard to use on phones: a missing viewport tag, content wider than the screen, text that is too small, tap targets that are too close together, and blocked zoom. Real Chromium, free, no signup.
Takes about 5 seconds. Free: 5 tests a day.
| Check | Pass when |
|---|---|
| Viewport meta tag Without it, phones lay the page out 980px wide and shrink it | <meta name="viewport" content="width=device-width, initial-scale=1"> is present |
| Content fits the screen Sideways scrolling is the most common mobile bug | The page is no wider than the 390px screen. If it is, the widest elements are listed so you know what to fix |
| Readable text Same 12px line as Lighthouse's legibility audit | At most 40% of the visible text is smaller than 12px once scaled to the phone screen |
| Tap targets WCAG 2.2 target size, level AA | Links and buttons are at least 24×24px, or have enough space around them. Links inside a sentence don't count |
| Zoom allowed An accessibility problem, not a layout one | The viewport tag doesn't set user-scalable=no or maximum-scale=1 |
The page counts as mobile-friendly when the first three checks pass. Tap targets and zoom are reported as warnings.
Google shut down its Mobile-Friendly Test, the Mobile Usability report in Search Console and the related API in December 2023. Its advice is to use Lighthouse in Chrome DevTools instead. That works, but it means opening DevTools, switching to mobile emulation and reading a long report. This page does the mobile layout checks in one step and shows you the screenshot next to them.
The page loads in headless Chromium with the settings of an iPhone: a 390×844 viewport, a 2x pixel ratio, touch support and the Safari user agent, so the site serves its real mobile layout. When the page has loaded, the tool measures the rendered page: the document width, the computed font size of every visible text node and the size and spacing of every link, button and form field. The screenshot is the first screen a phone user sees.
The checks run on the same rendering engine as the Shotmint API. To capture the phone view of every page in your sitemap, or after each deploy in CI, call the screenshot API with mobile=true:
curl "https://shotmint.creasework.com/v1/screenshot?url=https://example.com&width=390&height=844&mobile=true&device_scale_factor=2&full_page=true" -H "X-API-Key: YOUR_KEY" -o phone.png1 credit per screenshot. €5 buys 2,000 with no subscription, and credits never expire. Get 25 free API renders a month
Is "mobile-friendly" still a Google ranking factor? Google indexes the mobile version of every site (mobile-first indexing), so what it sees is your phone layout. Page experience signals still count, but Google no longer gives a mobile-friendly label or a separate test.
My page fails "fits the screen". How do I find the cause? The result lists the elements that stick out past the right edge, with their tag, id or class. The usual causes are fixed widths (width: 600px), wide images without max-width: 100%, tables, long URLs or code without wrapping, and elements pushed right with negative margins or transforms.
Can it test pages behind a login or on localhost? No, the page has to be publicly reachable. The API can send cookies or headers to capture logged-in pages.
Do you store the results? No. The screenshot and the report are sent to your browser and nothing is kept.
Related: mobile website screenshot (iPhone, Android, iPad, full page), responsive mockup generator, meta tag generator, Open Graph checker, robots.txt checker.
Mobile website screenshot · Mobile mockup generator · all free tools