Mobile Friendly Test Tool
Check whether any webpage is easy to use and read on mobile devices. Test for viewport configuration, touch target sizing, font legibility, responsive layout signals, and device-specific compatibility across iPhone, Android, iPad, tablet, and iPod models.
Analyze a Website
Enter a domain, with or without http/https. Select a device, then press Enter or click Check.
Mobile Performance Summary
Mobile Readiness Signals
Technical checks related to mobile usability, touch design, responsive layout, and device compatibility.
Findings
What the checker found in the page source.
No findings yet
Run a check to view detections and warnings.
Recommended Fixes
Action steps to improve mobile usability and search friendliness.
Run a test first
Once a site is checked, this area will list the most important improvements first.
SEO Impact
Google uses mobile-first indexing, meaning the mobile version of a page is primarily used for ranking. A non-mobile-friendly site can rank lower and lose organic traffic.
User Experience Impact
Poor mobile usability causes high bounce rates, low engagement, and poor conversion. Touch targets that are too small, text that is too small to read, and broken layouts all damage the user experience.
Indexing Notes
Without a correct viewport meta tag, search engines and users see a desktop-only layout scaled down on mobile screens. Responsive design ensures content is accessible and readable on all device sizes.
Useful for Search and Voice Queries
This page is structured to answer common natural-language questions about mobile usability and responsive design.
- Is my website mobile friendly?
- How do I check if a site works on iPhone?
- What viewport size does Android use?
- Why does my website look bad on mobile?
- How to fix mobile usability issues for SEO?
- Does tablet compatibility affect Google rankings?
How to Fix Mobile Usability Issues
The most common mobile usability problems and how to resolve them for better UX, SEO, and device compatibility.
- Add the viewport meta tag
Every mobile-ready page should include:<meta name="viewport" content="width=device-width, initial-scale=1.0"> - Avoid user-scalable=no
Disabling zoom hurts accessibility. Removeuser-scalable=noormaximum-scale=1from the viewport tag. - Use responsive CSS with media queries
Example:@media (max-width: 768px) { .container { padding: 10px; } } - Keep touch targets at least 44×44 pixels
Apple HIG and Google guidelines recommend a minimum tap target of 44px to avoid mis-taps. - Use a base font size of at least 16px
Smaller text triggers automatic zoom on iOS and can be hard to read on all phones. - Avoid horizontal scrolling
Usemax-width: 100%on images and setoverflow-x: hiddenon the body to prevent sideways scroll. - Remove Flash and non-mobile plugins
Flash is not supported on iOS or modern Android. Replace with HTML5 video, SVG, or Canvas. - Test real rendering with developer tools
Use Chrome DevTools Device Mode or Safari Responsive Design Mode to emulate real devices.
Important: This tool checks page source signals. Always verify with browser devtools and real device testing to confirm how the page actually renders and behaves on target devices.
How to Read the Results
A good mobile-friendly setup typically includes a proper viewport meta tag, responsive CSS with media queries, adequately sized touch targets, readable font sizes, and no Flash or plugin dependencies.
Design mobile-first. Start with the smallest screen layout and layer on complexity for larger screens using min-width media queries rather than breaking down from desktop.
- High score (80–100): Strong mobile readiness signals across viewport, layout, touch, and font sizing.
- Medium score (55–79): Basic mobile support exists but there are specific usability or compatibility gaps to address.
- Low score (0–54): Critical mobile usability issues detected. Missing viewport tag, no responsive signals, or other major problems found.
Mobile Friendly Test FAQ
What does this mobile friendly test check?
This tool checks for the viewport meta tag, responsive CSS and media queries, touch target size signals, font size legibility, horizontal overflow risks, Flash and plugin usage, mobile-specific meta tags, AMP signals, CSS framework detection, and overall mobile readiness indicators in the fetched HTML source.
Why does device selection matter?
Different devices have different screen widths and pixel ratios. An iPhone SE has a 320px wide screen while an iPad Pro is 1032px wide. A layout might look fine on a large phone but be broken on a small one. Selecting a specific device targets recommendations to that viewport.
Does this tool actually render the page on mobile?
No. This is a source-based checker that reads HTML signals. It does not render pages in a real browser viewport. For live rendering tests, use Chrome DevTools Device Mode, BrowserStack, or Google Search Console's Mobile Usability report.
What is the minimum touch target size?
Apple's HIG recommends 44×44 points. Google's Material Design guidelines recommend 48×48 density-independent pixels. Smaller targets cause accidental taps and harm usability ratings.
Why are some websites blocked from this checker?
Some websites block cross-origin requests or public proxy access. This tool uses multiple fetch strategies but some highly protected sites may still be inaccessible from a browser-based client-side tool.
Does mobile friendliness affect SEO rankings?
Yes. Google has used mobile-first indexing since 2019, meaning the mobile version of a page is the primary version used for crawling, indexing, and ranking. A poor mobile experience can directly lower rankings in both mobile and desktop search results.