Mobile-Friendly Test
Free, no sign-up: enter a URL and we load the page as an Android phone and check the meta viewport, CSS media queries, fixed widths over 480 px, small text, small tap targets, horizontal-scroll risks and legacy plugins, next to an iPhone screenshot. The 0–100 score is a transparent sum of weights based on the page code, not Google’s verdict — Google retired its own Mobile-Friendly Test in December 2023.
How the score works
The sum of eight checks; without a meta viewport the verdict is always “likely not mobile-friendly”, whatever the sum.
85+ looks mobile-friendly; 60–84 has issues; below 60 is likely not mobile-friendly. Pop-ups and page weight are shown as hints and are not part of the sum. Website screenshot
Key facts
Mobile-friendly test online: enter an address and get a 0–100 score from 8 checks (viewport, responsive styles, font size, tap targets and more), explanations and a screenshot. Free. It analyses HTML and CSS without running JavaScript; it is not Google's rendering.
- Price
- Free
- Sign-up
- Not required
- Processing
- On our server: HTML is fetched with an Android phone user agent, JavaScript is not executed; the screenshot comes from thum.io
- Input
- One public URL (http/https); up to 6 same-site CSS files, 400 KB each
- Limits
- 10 checks a minute; 15 a day without an account, 45 with one, unlimited with Pro
- Output
- A 0–100 score from 8 checks with published weights, an explanation and examples for each, an iPhone screenshot, pop-up hints, page weight
- Last updated
Video walkthrough 0:57
Mobile-Friendly Test (Google Retired Its Own) — Free Alternative with iPhone Screenshot
Google retired its Mobile-Friendly Test in December 2023. Check a page for free: a 0–100 score from eight weighted checks plus an iPhone screenshot.
Video transcript
Google retired its Mobile-Friendly Test in December 2023. Here's a free alternative for a quick check. Enter a page address. I'm testing our own homepage. Click Test page. It loads the page as an Android phone and returns a score out of a hundred, with the verdict: looks mobile-friendly. The checks are listed with points: meta viewport, zoom, responsive CSS, fixed widths, scroll risk, font size, tap targets and legacy plugins. And an iPhone screenshot to see it yourself. It's a heuristic, not Google's verdict. JavaScript isn't run, so styles added by scripts can't be seen. Trust the screenshot, and use Lighthouse for a precise audit. Free, no sign-up. The link is in the description. Subscribe for more free tools.
See it in action



Free Mobile-Friendly Test
The tool loads your page the way an Android phone requests it and checks the code for the usual reasons a site is awkward on a smartphone: no meta viewport, no media queries, blocks wider than 480 px, small text, tiny buttons and links, wide tables and iframes, Flash and frames. Next to it you get a screenshot with iPhone emulation. The 0–100 score adds up eight checks with published weights. Google retired its own Mobile-Friendly Test in December 2023, so this is not Google’s verdict but a clear list of what to fix; for speed and Core Web Vitals use PageSpeed Insights.
How to Use
- Paste the page URL
- Click “Test page” and wait for the score and the screenshot
- Fix the issues using the hints and test the page again
FAQ
Who it is for and typical uses
- After a redesign or a new theme. Make sure there is a viewport tag and no fixed width or horizontal scroll on a phone.
- A page looks bad on a phone. Get a list of causes with points: how much each problem costs.
- Before launching ads. Check the landing page; speed is covered separately by the page speed check.
Honest limitations
- No JavaScript execution. For script-built sites (SPA) the server HTML may be empty and the score inaccurate.
- CSS is capped. Up to 6 same-site stylesheets of 400 KB each are parsed; external and dynamic styles are not counted.
- A third party makes the screenshot. The iPhone-framed image is produced by thum.io.
- This is not Google. Google's test is closed; our score is not Google's rating and does not directly affect rankings.
PromoPilot vs alternatives: comparison
We compare only what is confirmed on each service's own pages. Where we could not confirm a fact, the cell shows "—".
| Parameter | PromoPilot | PageSpeed Insights | Lighthouse (Chrome DevTools) | Bing Mobile Friendliness Test |
|---|---|---|---|---|
| A score from 8 weighted checks | ✓ | — | — | — |
| Real-user data and Core Web Vitals | ✗ | ✓ | — | — |
| Notes | an iPhone-framed screenshot, pop-up hints, page weight | Google’s service: runs Lighthouse for mobile and desktop and shows real Chrome user data (Core Web Vitals) when available. | Built into Chrome: renders the page in phone emulation and audits accessibility, performance and SEO. The old Google Mobile-Friendly Test address now points here. | Bing Webmaster Tools’ test: enter a URL and see whether Bing considers the page mobile-friendly. |
Scroll the table sideways
Where we are weaker: no JavaScript execution, real rendering or Core Web Vitals data; the score is heuristic.
When to choose PromoPilot: When you want a quick read without signing up: what exactly breaks on phones, how many points it costs and how to fix it — in plain English, Ukrainian, Russian or Polish, with an iPhone screenshot alongside.
Checked on: . "—" means not confirmed on the official page; terms and prices change, so check the services' own sites.
What “mobile-friendly” actually means
A page is mobile-friendly when people can read it and tap on it without pinch-zooming or scrolling sideways. There are three ways to get there:
| Approach | How it works | What to watch |
|---|---|---|
| Responsive design | One URL and one HTML; CSS changes the layout (media queries, flex, grid) | Google’s recommendation: easiest to maintain, no duplicates |
| Dynamic serving | One URL, but the server sends different HTML to phones and desktops | Send Vary: User-Agent; both versions must have the same content |
| Separate mobile site (m.) | Phones are redirected to a subdomain such as m.example.com | Needs reciprocal rel="alternate" and canonical; signals are split across two URLs |
Google indexes sites with the smartphone Googlebot: what a phone sees is what gets indexed. If the mobile version trims text or drops links, search does not see them either.
Google’s Mobile-Friendly Test is gone: what to use now
In December 2023 Google retired the Mobile-Friendly Test, its API and the Mobile Usability report in Search Console. The old address now leads to the Lighthouse documentation. Replacements:
- Lighthouse in Chrome DevTools — renders the page in phone emulation and gives a detailed audit.
- PageSpeed Insights — the same Lighthouse in the cloud, plus real Chrome user data (LCP, INP, CLS) when the site has enough traffic.
- Device mode in Chrome DevTools — look at the page at 360–430 px wide and spot what overflows.
- This tool — a quick code review with no sign-up: what breaks, how many points it costs and how to fix it, plus an iPhone screenshot.
Common problems and how to fix them
| Problem | Fix |
|---|---|
| No meta viewport | Add to the <head>: <meta name="viewport" content="width=device-width, initial-scale=1"> |
| Zoom blocked | Remove user-scalable=no and maximum-scale=1 — people with low vision need to zoom |
| Blocks 960–1200 px wide | Swap width for max-width or percentages; keep fixed widths only inside a media query for large screens |
| Images wider than the screen | img{max-width:100%;height:auto} |
| Wide tables | Wrap the table in a block with overflow-x:auto, or turn rows into cards on narrow screens |
| Videos and maps in iframes | iframe{max-width:100%} plus aspect-ratio to keep proportions |
| Small text | Body text around 16 px; use rem rather than points |
| Small buttons and crowded links | Tap areas around 48×48 px with spacing between links; move menus into a hamburger |
| Full-screen pop-up on arrival | Show it later or make it a small bar; cookie banners and age checks are fine |
| Flash, Java, frames | Replace with HTML5 video, regular layout and separate pages |
How to read the result
The score is the sum of eight checks on the page code. We do not run JavaScript, cannot see CSS on other domains (CDNs) and do not measure the spacing between links, so on sites whose layout is built by scripts the result can be incomplete. If the screenshot shows cut-off text or a scrollbar at the bottom, trust the screenshot. Phone speed is a separate topic: see the page speed test and PageSpeed Insights. For a full-length or desktop capture use website screenshot, and find other technical issues with the SEO audit.
