Free Mobile Friendly Test
Check if your site is optimized for mobile devices. Free, fast, and works entirely in your browser with no sign-up required.
Updated
Mobile Friendly Test
Check if your website is optimized for mobile devices.
Mobile Friendly Test
Demo Mode: Results are simulated for educational purposes. For real mobile-friendly testing, use Google's PageSpeed Insights API.
Mobile-First Best Practices
- Use responsive design with flexible layouts and CSS Grid/Flexbox
- Set viewport meta tag:
width=device-width, initial-scale=1 - Use minimum 16px font size for body text
- Make tap targets at least 48x48 pixels with 8px spacing
- Avoid horizontal scrolling - use
max-width: 100%on media - Optimize images with responsive srcset and lazy loading
- Test with Google's Lighthouse and real devices
Frequently Asked Questions
What is the Mobile Friendly Test?
The Mobile Friendly Test is a free online tool that checks whether your website is optimized for mobile devices and provides responsive design recommendations.
Is the Mobile Friendly Test free?
Yes, it is completely free with no registration required.
Why is mobile-friendliness important?
Google uses mobile-first indexing, meaning mobile-friendliness directly impacts search rankings. The Mobile Friendly Test helps you ensure your site works well on all devices.
Is my data safe with this tool?
Absolutely. The Mobile Friendly Test processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.
Do I need to create an account to use this tool?
No account or registration is needed. Simply open the Mobile Friendly Test in your browser and start using it immediately. There are no sign-up walls or usage restrictions.
How do I use the Mobile Friendly Test?
Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.
Which browsers are supported?
The Mobile Friendly Test works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.
What is the viewport meta tag and why does the test check for it?
The viewport meta tag tells mobile browsers how to size and scale a page to the device screen. Without it, phones assume a desktop width of around 980px and shrink the whole layout to fit, leaving text tiny and forcing users to pinch-zoom. The correct tag is <meta name="viewport" content="width=device-width, initial-scale=1">, placed in the page <head>. "width=device-width" matches the layout to the device's real width, and "initial-scale=1" sets a 1:1 zoom level on load. It is the single most important signal for mobile usability, which is why a missing or misconfigured viewport tag is one of the first checks this test runs. Paste your URL above to see whether the viewport check passes and review the exact tag you should be using.
How big should tap targets be for a mobile-friendly page?
Tap targets are the buttons, links, and form controls a user presses with a fingertip, which is far less precise than a mouse cursor. The working guideline this test applies is roughly 48x48 pixels per target, with at least 8 pixels of spacing between adjacent elements. Targets smaller than that, or crammed too close together, lead to mis-taps where someone hits the wrong link or has to zoom in to aim. Common offenders are tightly packed navigation menus, small text links inside paragraphs, and icon buttons sized for a desktop pointer. The fix is to give interactive elements generous padding and margins rather than relying on the visible graphic alone. Enter your URL above and the tap-target check will flag elements that fall below the 48px guideline so you know exactly what to enlarge.
What font size counts as legible on mobile and why does small text fail the test?
Body text should be at least 16 pixels on mobile, which is the threshold below which most readers have to pinch-zoom to read comfortably. Anything smaller forces an extra interaction on every visit and signals a layout that was designed for desktop and never adapted for phones. The test flags body copy under roughly 16px as a readability failure. The recommended fix is to set a base font-size of 16px and use relative units like rem or em so text scales predictably with the user's settings and across breakpoints, rather than locking sizes in fixed pixels. Headings and captions can vary, but the main reading text is what this check evaluates. Run your URL through the test above to see the minimum text size it detects and whether your page clears the legibility bar.
Why does content overflowing the viewport cause horizontal scrolling on phones?
Horizontal scrolling on mobile almost always means an element is wider than the screen and the page cannot shrink to contain it. The usual causes are fixed pixel widths in CSS, large unconstrained images, wide tables, or absolutely positioned elements that extend past the right edge. Because a phone screen is narrow, even one oversized element pushes the whole layout sideways and breaks the reading flow. The test checks whether all content fits within the viewport without requiring horizontal scroll. The standard fixes are responsive layouts built with CSS Grid or Flexbox instead of fixed widths, and keeping media fluid with max-width: 100% so images never spill past their container. Enter your URL above to see whether the content-width check passes and which kinds of overflow the report calls out.
Which Core Web Vitals affect a mobile-friendliness score the most?
Mobile usability is about layout, but performance shapes the real experience, so this test surfaces a performance score alongside three Core Web Vitals that matter most on phones: First Contentful Paint, Largest Contentful Paint, and Cumulative Layout Shift. FCP marks when the first content appears, LCP measures when the main content finishes loading, and CLS captures how much the layout unexpectedly shifts while elements load, which is especially jarring on a small screen mid-tap. On mobile, slower networks and weaker processors make these metrics harder to hit than on desktop. Practical fixes include serving responsive images with srcset, lazy-loading anything below the fold, and reserving space for media so nothing jumps. Run your URL above to view the simulated performance score and the FCP, LCP, and CLS values the report breaks out.
Related Tools
Free Website Speed Test
Analyze website page load time, performance metrics, and optimization opportunities. Free, fast, and works entirely in your browser with no sign-up required.
Free Meta Tag Extractor
Extract and review all meta tags from any webpage for SEO and social media analysis. Free, fast, and works entirely in your browser with no sign-up required.
Free Website Screenshot Tool
Capture full-page or viewport screenshots of any webpage for design review and testing. Free, fast, and works entirely in your browser with no sign-up required.
Free Accessibility Checker
Check website accessibility compliance with WCAG standards and get actionable fix suggestions. Free, fast, and works entirely in your browser with no sign-up required.
About the Mobile Friendly Test
The Mobile Friendly Test is a free tool that walks through the criteria Google uses to decide whether a page works well on phones and tablets. Enter a URL, run the test, and you get a mobile usability score out of 100 plus a check-by-check breakdown covering the viewport meta tag, text readability, tap-target sizing, content width, and core mobile performance metrics. It is built for developers, site owners, and SEOs who want a quick, plain-language refresher on what "mobile-friendly" actually means before they ship a layout or chase a ranking problem.
One thing to be upfront about: this tool runs in a demonstration mode. The results it shows are simulated for educational purposes rather than fetched from a live crawl of your page, and the in-tool notice says as much. For a real audit of a specific URL, Google's PageSpeed Insights and Lighthouse pull live field and lab data. Where this test earns its place is in teaching the checklist itself — what each signal is, why it matters, and how to fix it — so you know exactly what to look for when you do run a live audit.
What the test checks
Each run produces a pass or fail against the signals that drive mobile usability, with a short explanation and a concrete fix for anything that fails:
- Viewport configuration — confirms a
width=device-width, initial-scale=1meta tag is present, so mobile browsers render the page at the device's real width instead of a zoomed-out desktop layout. - Text readability — flags body text smaller than roughly 16px, the point below which most readers have to pinch-zoom to read comfortably.
- Tap-target size — checks that buttons and links are large enough and far enough apart to tap accurately. The working guideline is about 48x48 pixels with at least 8px of spacing.
- Content width — looks for elements that spill past the viewport and force horizontal scrolling, a classic sign of fixed-width CSS or unconstrained images.
- Mobile performance — surfaces a performance score alongside the Core Web Vitals that matter most on phones: First Contentful Paint, Largest Contentful Paint, and Cumulative Layout Shift.
Why mobile-friendliness matters for rankings
Google has used mobile-first indexing for years, which means it predominantly crawls and ranks the mobile version of your page rather than the desktop one. If your site renders poorly on a phone — text too small, buttons crammed together, content running off-screen — that is the experience Google evaluates, and it is the experience most of your visitors get. More than half of global web traffic now comes from mobile devices, so a page that only looks right on a desktop is failing the majority of its audience. The test frames these issues the way a search engine would, so the gaps you close here are the same ones that protect your rankings and bounce rate.
Turning results into fixes
The value of the report is in the "how to fix" guidance attached to every failed check, which mirrors the mobile-first practices the tool recommends:
- Build with responsive layouts using CSS Grid or Flexbox rather than fixed pixel widths.
- Add the viewport meta tag to the page
<head>if it is missing. - Set a base font size of at least 16px and use relative units like
remorem. - Keep media fluid with
max-width: 100%so images never trigger horizontal scroll. - Serve responsive images with
srcsetand lazy-load anything below the fold to protect your performance scores.
Treat this tool as a learning checklist and a pre-flight pass: use it to understand every signal and rehearse the fixes, then confirm the live numbers for your real URL with Lighthouse or PageSpeed Insights before you call the work done.