Skip to content

Mobile Friendly Test

This mobile friendly test fetches a page twice, once as Googlebot Smartphone and once as desktop Googlebot, and reads the HTML and CSS a phone receives.

Try it on or paste any public URL. Fetching the page twice and its stylesheets can take up to 20 seconds.

Note

We request the page from our server as Googlebot Smartphone and as desktop Googlebot, then read its inline styles and up to six linked stylesheets. Nothing is rendered on our side and nothing is stored. The phone preview is loaded by your browser, straight from the site.

It checks the viewport meta tag, looks for width-based media queries in the inline styles and up to six linked stylesheets, flags fixed page widths, small base text and Flash or Java content, and then lines the two responses up side by side so you can see whether the version Google indexes carries the same title, robots rules, canonical, text, links and structured data as the desktop one. Where the site allows framing, the page also loads in a phone-sized preview in your own browser. No sign-up and nothing to install.

Use this tool often? Bookmark this page, so it is one click away next time.

Email me this result

Want a copy for your records or a client? Leave your email and we'll send you this result. It is written by a real person at Crawl Cove, not an automated blast, so it may take a little while to arrive. We'll only use your address to send it, unless you also tick the box below. Privacy policy.

That email address doesn't look right. Please check it and try again.

Something went wrong saving your address. Your result above is unaffected; please try again.

Got it. We'll email your result to you. Nothing else lands in your inbox unless you ticked the tips box.

How to test if a page is mobile friendly

  1. Paste the URL

    Enter any public address, with or without https://. Redirects are followed, including a redirect that sends phones to a separate m. site.

  2. Read the layout checks

    Viewport, media queries, fixed widths, base text size and plugins each come back as Pass, Improve, Fail or Note, with the fix written next to anything that needs one.

  3. Compare phone and desktop

    The parity table puts the smartphone and desktop answers next to each other. A red or amber row is something Google either sees differently or does not see at all.

  4. Look at the preview, then measure

    Scroll the phone preview to see the page at phone width. For tap targets and rendered text size, open the PageSpeed Insights link for a Lighthouse run on mobile.

What a mobile friendly test checks

A mobile-friendly page fits a phone screen without sideways scrolling, has text you can read without zooming, and has nothing on it that a phone browser cannot run. A test for that looks at the things that decide it: whether the page tells the browser to use the screen's own width, whether the CSS changes the layout for narrow screens, whether anything forces the page wider than the phone, and whether the content relies on plugins. Since Google moved to mobile-first indexing there is a second question as well. The page Google stores is the one it fetched as a smartphone, so a site that sends phones less content than desktops loses that content from search.

Google retired its Mobile-Friendly Test in December 2023

Google switched off the Mobile-Friendly Test tool, the Mobile-Friendly Test API and the Mobile Usability report in Search Console on 1 December 2023. Its stated reason was that better tools now exist, and it pointed people at Lighthouse, which runs in Chrome DevTools and powers PageSpeed Insights. The old URL redirects there. Lighthouse renders the page in an emulated phone and reports tap target sizes, legible font sizes and content wider than the screen, alongside its speed scores. What it does not do is compare the smartphone and desktop versions of a page, the part of mobile friendliness that most affects indexing, and that comparison is what the parity table on this page is for.

Core Web Vitals explained

How this mobile friendly test works

Our server requests the URL with the user agent Google documents for Googlebot Smartphone, follows each redirect by hand, and keeps the final response. It then does the same with the desktop Googlebot user agent. Many sites block anything that claims to be Googlebot but does not come from Google's addresses; when that happens the test repeats both fetches as phone and desktop Chrome and says so in the result. From the smartphone response it reads the viewport tag, every inline style block and up to six linked stylesheets, fetched in parallel. Nothing is rendered on our side, so the results describe the code the page ships rather than a screenshot. Nothing is stored either, and a result link stays cached for ten minutes so sharing it does not fetch the page again.

The checks, and what each result means

A missing viewport tag fails, because phones then lay the page out at about 980 pixels and shrink it. A fixed width such as width=1024 fails for the same reason. width=device-width with initial-scale=1 passes, and user-scalable=no or a maximum-scale below 2 is marked Improve, since it stops people who need larger text from zooming. Width-based @media and @container rules count as responsive CSS; finding none is marked Improve rather than Fail, because a fluid layout built with percentages, flexbox or grid can fit a phone without them. An html, body or main wrapper rule with a width or min-width of 600px or more outside any media query is flagged, as is base text under 12px. Images, tables, iframes and videos with a width attribute over 480 and no max-width rule are listed as a Note. Flash, Java and Silverlight content fails, since no phone browser runs it.

Mobile-first indexing and the parity check

Google crawls and indexes with its smartphone crawler, so the mobile version of a page is the version that ranks. The parity check compares the two responses on the final URL, HTTP status, meta robots and X-Robots-Tag, canonical, title, meta description, first H1, visible word count, internal links, structured data types, hreflang links and image count. A different status, robots rule or canonical is a Fail, because it changes whether or which page gets indexed. Content, link and structured data differences beyond a small tolerance (word counts within 10% count as the same) are marked Improve, with the reason. Text that only the desktop page carries is missing from the index, and links that only desktop visitors see pass no value to the pages they point at. If phones are sent to a separate m. site, the test checks for the rel=alternate link on the desktop page and a canonical on the mobile page pointing back, which is how Google pairs the two. When the HTML differs by device and the server sends no Vary: User-Agent header, that is noted too, because a cache can then serve the wrong version.

Mobile-friendly and fast on mobile are separate questions

A page can pass every layout check and still be slow on a phone, and a fast page can still have a fixed 1200 pixel layout. Speed on mobile depends on how much the page weighs, how quickly the server answers and how long the main content takes to appear, which Core Web Vitals measure from real Chrome users. If the layout checks here pass, the next step is usually to look at page weight and Largest Contentful Paint.

Page Size Checker · Core Web Vitals checker · Largest Contentful Paint

What a static test cannot see

Reading the code tells you what the page asks the browser to do. It cannot tell you how far apart the buttons end up once the styles apply, what size the text renders at after every rule has cascaded, or whether a script injects a wide banner after the page loads. Those need a real browser. The phone preview on this page helps, since it is your own browser drawing the page at phone width, and the PageSpeed Insights link in the result runs Lighthouse on mobile for the same URL. Some sites forbid framing with X-Frame-Options or a Content-Security-Policy frame-ancestors rule; for those the result explains why there is no preview, and the PageSpeed Insights screenshot is the fallback.

How to fix the common failures

Most failures have short fixes. Add <meta name="viewport" content="width=device-width, initial-scale=1"> to the head of every template. Replace fixed widths on the page wrapper with max-width and a percentage, or move them inside a min-width media query so they only apply on large screens. Add img, video, iframe and table rules with max-width: 100% so embedded media shrinks with the screen. Set body text to at least 16px on small screens. Remove anything that needs Flash or Java. Parity problems only arise when phones and desktops get different HTML, and the cause is usually in the theme or the CDN: a mobile template that drops sections, a menu built only for desktop, or structured data that a plugin adds to one template and not the other.

Technical SEO guide

Who this test is for

It suits anyone checking a page before or after a redesign, a theme change or a move to a new CDN, and agencies who want a quick answer on a prospect's home page. The parity table is most useful on sites that serve different HTML to phones, such as older WordPress setups with a mobile plugin, m. sites, and stores whose themes hide sections on small screens. Developers can use it to confirm that a CSS change reached the stylesheets the page actually loads.

Frequently asked questions

Is this mobile friendly test free?
Yes. It is free and needs no sign-up or email. Each check fetches the page twice and up to six stylesheets, so it is limited to 10 checks a minute per visitor.
Does Google still have a Mobile-Friendly Test?
No. Google retired the Mobile-Friendly Test tool, its API and the Mobile Usability report in Search Console on 1 December 2023, and points people to Lighthouse and PageSpeed Insights instead.
How do I check if my website is mobile friendly?
Paste a page into the test above. It checks the viewport tag, responsive CSS, fixed widths, text size and plugins, and compares the phone and desktop versions. Then open the phone preview, and run PageSpeed Insights on mobile for tap targets and rendered text size.
What makes a website mobile friendly?
A viewport tag set to the device width, CSS that adapts the layout to narrow screens, nothing fixed wider than a phone, text readable without zooming, tap targets far enough apart, no plugins, and the same content on phones as on desktops.
What is mobile-first indexing?
Google crawls and indexes pages with its smartphone crawler, so the mobile version of a page is the one stored and ranked. Content, links or structured data that only the desktop version carries are left out.
Why does the test say no media queries were found when my site looks fine on a phone?
A layout built with percentage widths, flexbox or grid can fit a phone without any media query, so this is marked Improve rather than Fail. It is also possible the rules live in a stylesheet loaded by JavaScript or beyond the first six, which this test does not read.
Why is there no phone preview for my page?
The page sends X-Frame-Options or a Content-Security-Policy frame-ancestors rule that stops other sites showing it in a frame, or it is served over plain http. The result names which one. PageSpeed Insights shows a mobile screenshot instead.
Can I check every page on my site?
Not here: this tool tests one URL at a time. Crawl Cove, the desktop crawler, flags every indexable page it crawls that has no viewport meta tag, and it has a permanent Free plan.

From one page to your whole site

This tests one page. Crawl Cove flags every indexable page it crawls that has no viewport meta tag, alongside its other on-page and technical checks. See check Core Web Vitals or check one page's full SEO.

Download free