Mobile Website Audit: Ensure Your Site Works Perfectly on Every Device

Why Mobile Audits Matter

Over 60% of web traffic now comes from mobile devices. More importantly, Google uses mobile-first indexing for all websites — meaning the mobile version of your site is what Google crawls, indexes, and uses for ranking. If your mobile experience is poor, your desktop rankings suffer too.

A mobile audit evaluates your site on the devices your users actually use, under the network conditions they actually experience. What looks and works great on a desktop with fibre broadband may be broken on a phone with a 4G connection.

Mobile-First Indexing

Since 2023, all websites are crawled and indexed using the mobile version. This means:

• Content must be identical: If content exists on desktop but is hidden, collapsed, or removed on mobile, Google may not see it at all.
• Structured data must be on mobile: Schema markup that only appears in the desktop version won't be used by Google.
• Internal links must work on mobile: Navigation that relies on hover states or desktop-only menus may prevent Google from discovering linked pages.
• Images must be present: Images hidden on mobile via CSS display:none may not be indexed. Use responsive images instead of hiding them.

Responsive Design Checks

• Viewport meta tag: Every page must include <meta name="viewport" content="width=device-width, initial-scale=1">. Without it, mobile browsers render the page at desktop width.
• No horizontal scrolling: Content should never overflow the viewport width. Check for fixed-width elements, wide tables, or oversized images that force horizontal scrolling.
• Readable text without zooming: Body text should be at least 16px. Users shouldn't need to pinch-zoom to read your content.
• Flexible layouts: Use CSS flexbox or grid with relative units (%, rem, vw) instead of fixed pixel widths. Test at every common viewport width: 320px, 375px, 414px, 768px.
• Images scale correctly: Images should have max-width: 100% and height: auto to prevent overflow. Use the picture element or srcset for different viewport sizes.
• Tables are readable: Data tables often break on mobile. Use responsive table patterns — horizontal scrolling wrappers, stacked layouts, or simplified mobile versions.

Mobile Speed Optimisation

Mobile speed is a distinct challenge from desktop speed. Mobile devices have slower CPUs, less RAM, and often use cellular connections with higher latency.

• Test on real mobile conditions: Throttle to 4G speeds (1.6Mbps down, 150ms RTT) when testing. Use Lighthouse's mobile emulation or WebPageTest with a mobile device profile.
• Reduce JavaScript payload: Mobile CPUs are 3-5x slower than desktop at parsing and executing JavaScript. Every KB of JS matters more on mobile.
• Optimise for high-latency connections: Each HTTP request adds 100-300ms of latency on mobile. Reduce the number of requests and use HTTP/2 multiplexing.
• Preconnect to critical origins: Use <link rel="preconnect"> for external domains that serve critical resources (fonts, APIs, CDNs).
• Target mobile LCP under 2.5s: Mobile LCP is typically 1-2 seconds slower than desktop. Preload the mobile hero image and minimise server response time.

Touch and Navigation

• Tap targets are at least 48x48px: Buttons, links, and form fields must be large enough to tap accurately with a finger. Google flags tap targets under 48px as a mobile usability issue.
• Adequate spacing between tap targets: At least 8px of spacing between clickable elements to prevent accidental taps.
• No hover-dependent interactions: Dropdown menus, tooltips, and hover effects don't work on touch screens. Ensure all interactive elements are accessible via tap.
• Mobile menu is usable: Hamburger menus should be easy to open and close, menu items should be large enough to tap, and the menu shouldn't cover the entire viewport.
• Forms are mobile-friendly: Use appropriate input types (email, tel, number) to trigger the right mobile keyboard. Labels should be above fields, not beside them.
• No interstitials covering content: Full-screen pop-ups that block content on mobile trigger Google's intrusive interstitial penalty. Use banners instead of modals.

Mobile Content Parity

With mobile-first indexing, your mobile site must have the same valuable content as your desktop site:

• Same primary content: Text, images, and videos on desktop should also be on mobile. Content hidden behind "Read more" toggles is generally fine — Google can access accordions and expandable sections.
• Same headings: H1-H6 heading structure should be identical on mobile and desktop.
• Same internal links: Mobile navigation must link to the same important pages as desktop navigation.
• Same structured data: Schema markup should be present on the mobile version of every page.
• Same alt text on images: If you serve different images on mobile, they still need descriptive alt text.

Testing Tools

• Google's Mobile-Friendly Test: Quick pass/fail check for individual URLs. Shows rendering issues and specific mobile usability problems.
• Google Search Console Mobile Usability report: Shows mobile usability issues across your entire site, grouped by error type.
• Chrome DevTools Device Mode: Emulate any mobile device with responsive design mode. Toggle the device toolbar with Ctrl+Shift+M.
• BrowserStack or LambdaTest: Test on real devices remotely. Essential for catching issues that emulators miss — especially iOS-specific rendering bugs.
• PageSpeed Insights (mobile): Always test the mobile version specifically. Mobile scores are typically 20-40 points lower than desktop due to CPU and network throttling.

Mobile Audit Checklist

• Viewport meta tag present on all pages
• No horizontal scrolling at any viewport width
• Text readable at 16px+ without zooming
• Tap targets 48x48px minimum with adequate spacing
• Mobile menu functional and easy to use
• No hover-dependent interactions
• Forms use correct input types
• No intrusive interstitials
• Content parity with desktop version
• Mobile LCP under 2.5 seconds
• Images responsive with srcset
• Third-party scripts deferred on mobile
• Structured data present on mobile version

For a complete mobile audit alongside our 72-checkpoint review, see our professional audit services.