Mobile Friendly Test

Enter any URL to preview your website on mobile, tablet and desktop — spot layout issues before they cost you rankings.

Enter a URL to test responsive layout

Manual Audit Checklist

Check these items while viewing the site:

Related Tools

More than half of all web traffic now comes from mobile devices. If your site isn’t optimized for phones and tablets, you’re losing visitors — and rankings. Enter any URL here and the tool renders it across mobile, tablet, and desktop viewports so you can see exactly how it looks and behaves on each screen size.

No phone needed. No emulator to install. Results in seconds.

How to Use This Mobile Friendly Test

  1. Enter a URL — paste any webpage address and click Test
  2. Switch viewports — toggle between Mobile, Tablet, Large, and Desktop to see how the layout adapts across screen sizes
  3. Check the manual audit checklist — the tool highlights four key areas to inspect while viewing the site: horizontal scrolling, text readability, tap target size, and viewport behavior
  4. Run a Technical Audit — click “Run Technical Audit” to trigger a PageSpeed Insights check for deeper mobile performance data

Why Mobile Friendliness Affects Your Google Rankings

Google switched to mobile-first indexing in 2019 and completed the rollout for all sites by 2021. What this means in practice: Google primarily uses the mobile version of your site for crawling, indexing, and ranking — not the desktop version.

If your desktop site is well-optimized but your mobile version is broken, hard to read, or slow to load, Google sees your site as the broken mobile version. That directly affects where you rank.

This matters especially because over 60% of searches now happen on mobile devices. A site that ranks for a keyword on desktop but delivers a poor mobile experience will see high bounce rates — users leave immediately — which further signals to Google that the page isn’t relevant or useful.

What This Tool Checks

Horizontal scrolling — Content should never extend beyond the width of the screen. When users have to scroll sideways to read text or see images, it’s a strong sign the page wasn’t designed for mobile. Google flags this as a mobile usability issue.

Text readability — Text that’s too small forces users to pinch-zoom to read. Google recommends a base font size of at least 16px for body text on mobile. If someone needs to zoom to read your content, the page fails basic usability standards.

Tap targets — Buttons, links, and interactive elements need to be large enough to tap accurately on a touchscreen. Google recommends tap targets of at least 48×48 pixels with adequate spacing between them. Tiny or closely-packed links cause accidental clicks and frustration.

Viewport configuration — The viewport meta tag (<meta name="viewport" content="width=device-width, initial-scale=1">) tells browsers how to scale and display the page on different screen sizes. Without it, mobile browsers render the page at desktop width and shrink it down — making everything tiny. Every mobile-optimized page needs this tag.

Mobile-First Indexing — What It Means for Your Site

Mobile-first indexing doesn’t mean Google only indexes mobile pages. It means Google’s crawler visits your site using a smartphone user agent and uses what it finds as the primary version for ranking decisions.

Practical implications:

Content parity — If you show less content on mobile than on desktop (common with collapsed sections or “load more” patterns), Google only sees the mobile content. Hidden content may not be indexed or weighted as heavily.

Structured data — If your desktop pages have schema markup but your mobile pages don’t, Google may not see your structured data. Implement schema on both versions, or ensure it’s in your universal template.

Images and videos — Make sure your mobile pages load the same images as your desktop pages. Lazy loading is fine as long as Google’s crawler can access the images.

Page speed — Mobile users are often on slower connections. A page that loads in 2 seconds on desktop may take 6 seconds on a 4G connection. Core Web Vitals — especially Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS) — are measured based on the mobile experience.

Common Mobile Friendly Issues and How to Fix Them

Text too small to read Add font-size: 16px as the base body font size in your CSS. Avoid using px units for font sizes that need to scale — use rem or em instead.

Viewport not configured Add this to your <head>: <meta name="viewport" content="width=device-width, initial-scale=1.0">

Content wider than screen Usually caused by a fixed-width element. Check for width: 600px or similar fixed values in your CSS and replace with max-width: 100%.

Tap targets too small or too close Increase button and link sizes using padding. padding: 12px 16px on links gives them enough tap area. Use margin to space them apart.

Images not scaling Add img { max-width: 100%; height: auto; } to your CSS. This ensures images shrink on small screens rather than overflowing.

Slow load time on mobile Compress images, use modern formats like WebP, minimize render-blocking CSS and JavaScript, and enable browser caching. Run a PageSpeed test to identify the biggest opportunities.

Mobile Friendly Test vs Google’s Tool

Google previously offered a standalone “Mobile-Friendly Test” tool at search.google.com/test/mobile-friendly. That tool was retired in December 2023. Google now recommends using Google Search Console’s Mobile Usability report for site-wide mobile issue detection.

This tool provides a visual iframe-based preview across multiple viewport sizes — useful for a quick visual check of any URL without needing access to Search Console. For a deeper technical analysis, the built-in PageSpeed audit runs a Lighthouse check with detailed recommendations.

Frequently Asked Questions (FAQ)

Google’s standalone Mobile-Friendly Test tool was retired in December 2023. Google now directs users to the Mobile Usability report in Google Search Console for site-wide mobile issue checking. This tool provides a similar visual preview function — enter any URL to see how it renders across mobile, tablet, and desktop viewports, with a manual audit checklist for common mobile usability issues.

Google uses mobile-first indexing, meaning it crawls and indexes the mobile version of your site for ranking purposes. If your mobile experience is poor — broken layout, unreadable text, slow loading — it directly impacts where your pages rank in search results. Over 60% of searches happen on mobile, so Google weights mobile usability heavily. A page that passes mobile friendliness checks is more likely to maintain its rankings than one with mobile usability errors.

The viewport meta tag (<meta name="viewport" content="width=device-width, initial-scale=1.0">) tells mobile browsers how to scale and display your page. Without it, browsers render the page at desktop width and shrink everything down, making text and buttons tiny and unusable. Every mobile-optimized page needs this tag in the <head> section. It’s one of the first things to check when a site doesn’t display correctly on mobile.

This usually happens when an element has a fixed pixel width that exceeds the mobile screen width. Check your CSS for values like width: 800px or min-width: 600px and replace them with max-width: 100%. Also add overflow-x: hidden to your body element to prevent horizontal scrolling. Images without max-width: 100% are another common cause — add img { max-width: 100%; height: auto; } to your stylesheet.

Mobile-first indexing means Google primarily uses the mobile version of your website for crawling, indexing, and determining search rankings — not the desktop version. It doesn’t mean Google ignores your desktop site, but the mobile version is treated as the primary source of truth. If your mobile page has less content, different structured data, or missing images compared to your desktop page, those differences affect your rankings.

Enter your WordPress site URL into this tool and switch between Mobile, Tablet, and Desktop viewports to check how the layout adapts. Common WordPress mobile issues include themes that aren’t fully responsive, plugins that inject fixed-width elements, and images that weren’t added with responsive settings. Most modern WordPress themes are mobile responsive by default, but custom CSS or page builder styling can break responsiveness. Run the technical audit to check Core Web Vitals and page speed on mobile.

Google recommends tap targets (buttons, links, interactive elements) be at least 48×48 pixels with at least 8 pixels of space between them. This ensures users can tap accurately without accidentally hitting the wrong element. Small tap targets are one of the most common mobile usability issues flagged in Google Search Console. Fix them by adding padding to buttons and links rather than increasing font size alone.