Mobile-Friendly
Test Free

The Viewport Meta Tag: The #1 Mobile Signal

The single most critical mobile-friendly signal is the viewport meta tag: <meta name="viewport" content="width=device-width, initial-scale=1">. Without it, mobile browsers render your page at a desktop width of around 980px and then shrink it down, making text impossibly small and buttons impossible to tap. Google's mobile-first crawler checks for this tag before anything else.

Two common mistakes: (1) Blocking user zoom with user-scalable=no — this fails WCAG accessibility criteria and is flagged as a mobile usability issue in Google Search Console. (2) Using a fixed initial-scale without width=device-width — this still renders at the wrong width on many devices. Always use the standard viewport tag shown above.

Mobile-First Indexing: Why Your Mobile Page IS Your SEO

Since March 2021, Google has used mobile-first indexing for all websites — meaning Googlebot primarily crawls and indexes the mobile version of your site. If your mobile site has less content, fewer internal links, missing structured data, or lower quality than your desktop site, your rankings suffer — even for desktop users searching Google.

Critical implication: if you serve different content to mobile vs desktop users (dynamic serving or separate m-dot site), the mobile version must have all the same content, structured data, and internal links as the desktop version. Check your canonical tag setup to ensure mobile and desktop point to the same canonical URL.

Page Speed & Core Web Vitals for Mobile

Page speed is a confirmed Google ranking factor, and its impact is far more pronounced on mobile. According to Google and SOASTA data, pages loading over 3 seconds have a 53% higher bounce rate on mobile. For every additional second of load time, conversions drop by 7%.

Google's Core Web Vitals — LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift) — are now direct ranking signals. LCP should be under 2.5s, INP under 200ms, and CLS under 0.1. Mobile pages are measured separately from desktop in Chrome UX Report data, and mobile scores are typically 2–3x worse than desktop. Fixing render-blocking resources, enabling lazy loading, using next-gen image formats (WebP/AVIF), and implementing a CDN are the highest-impact improvements.

Use our Page Speed Checklist Tool for a detailed performance audit alongside this mobile-friendly test.

Touch Targets, Font Sizes & Tap Usability

Google's mobile usability guidelines (and Google Search Console's Mobile Usability report) specifically flag three usability problems: text too small to read, clickable elements too close together, and content wider than screen. These are checked during Googlebot's crawl and can trigger manual actions or ranking penalties in severe cases.

Touch targets should be at least 48×48 CSS pixels with 8px spacing between interactive elements. Font sizes should be at least 16px for body text — never set base font below 12px. Horizontal scrolling is caused by fixed-width elements wider than the viewport. Use CSS Grid, Flexbox, and max-width with percentages instead of fixed pixel widths to prevent layout overflow. Check your heading structure to ensure your content hierarchy is clear on mobile.

Mobile SEO for AI Search, LLMs & Answer Engines (AEO)

In 2024–2025, the SEO landscape shifted dramatically with AI search. Google AI Overviews, Perplexity AI, ChatGPT browsing, Claude, and other LLMs now crawl and index web content to answer user queries directly. These AI crawlers behave like mobile Googlebot — they request your page's HTML and parse its content, including structured data, headings, and semantic markup.

Answer Engine Optimisation (AEO) best practices overlap heavily with mobile SEO: fast page load (AI crawlers abandon slow pages), clean semantic HTML (LLMs parse heading hierarchies to understand content structure), Schema.org structured data (FAQ, HowTo, and Article schemas are directly consumed by AI Overviews), and concise, well-structured content that answers specific questions. A page that passes a comprehensive mobile-friendly test is also better positioned to be cited by AI search engines, as it signals technical quality and crawlability to both Google and AI systems.

For AI and LLM discoverability, also ensure your robots.txt doesn't accidentally block AI crawlers like GPTBot, ClaudeBot, or PerplexityBot — and that your XML sitemap is valid and submitted to Google Search Console.

Image Optimisation for Mobile: Lazy Loading, srcset & WebP

Images are typically the largest contributors to mobile page weight, often accounting for 60–70% of total bytes. Three techniques dramatically improve mobile performance: Lazy loading (loading="lazy" on img tags) defers off-screen images until the user scrolls near them, reducing initial page weight and improving LCP. Responsive images with srcset and sizes attributes serve smaller images to mobile devices — a 1200px image should never be loaded on a 390px iPhone screen. Next-gen formats (WebP saves 25–35% over JPEG/PNG, AVIF saves 50%) reduce file size without visible quality loss.

Use our Image ALT Tag Checker to also audit your alt attributes — missing alt text hurts both SEO and accessibility on mobile, where users may rely on screen readers or have images disabled to save data.