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.

Meta viewport · 30 zoom · 5 responsive CSS · 20 fixed widths · 10 horizontal scroll · 10 font size · 10 tap targets · 10 plugins · 5

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

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: 2026-10-13

Alternatives

Other tools for the same job, and what each one does well:

PageSpeed Insights — Google’s service: runs Lighthouse for mobile and desktop and shows real Chrome user data (Core Web Vitals) when available.
Lighthouse (Chrome DevTools) — 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 Mobile Friendliness Test — Bing Webmaster Tools’ test: enter a URL and see whether Bing considers the page mobile-friendly.

When to choose this tool: 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.

Descriptions checked against each tool's own site in October 2026.

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.

Meta viewport and zoom blocking (accessibility)

Media queries in inline styles and up to 6 same-site CSS files

Fixed widths, wide tables, images and iframes

Small text, small tap targets, Flash and frames

iPhone screenshot, pop-up hints and page weight

Free, no sign-up: 15 checks a day, 45 with an account, unlimited with Pro

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

No. 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 docs. Google still indexes with the smartphone Googlebot, so checking the mobile version still matters — in Lighthouse, PageSpeed Insights or here.

It is the sum of eight checks: meta viewport 30 points, responsive CSS 20, fixed widths, horizontal scroll, font size and tap targets 10 each, zoom and legacy plugins 5 each. 85+ looks mobile-friendly, 60–84 has issues, below 60 or no viewport is likely not mobile-friendly. Pop-ups and page weight are shown as hints and are not part of the sum.

We read HTML and CSS but do not run JavaScript or measure the rendered page. Styles added by scripts, CSS files on other domains (CDNs) and the spacing between links cannot be seen this way. That is why there is always a screenshot: if it shows sideways scrolling or cut-off text, trust the screenshot and run a precise audit in Lighthouse.

For a responsive site, <meta name="viewport" content="width=device-width, initial-scale=1"> in the <head> is enough. Do not add user-scalable=no or maximum-scale=1: they stop people from zooming text. The tag alone does not make a site responsive — you also need a fluid layout and media queries.

For a precise audit use Lighthouse in Chrome DevTools and PageSpeed Insights: they render the page, and PageSpeed also shows real Chrome user data (Core Web Vitals). Bing has its own mobile friendliness test in Webmaster Tools. Our tool is quicker for a first look: it explains each issue in plain English, Ukrainian, Russian or Polish, shows an iPhone screenshot and needs no sign-up.

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.