Is your website mobile friendly? How to actually check

Test on a real phone, logged out, off wifi

Your desktop browser resized narrow is not a mobile test. Real phones have touch targets, mobile keyboards, slower connections, and less patience. Open your site on a phone over mobile data in a private window and try to complete your most important action end to end.

The four things that make a site fail on mobile

Text too small to read without zooming, tap targets too close together (menus and buttons under 44 pixels), content wider than the screen forcing sideways scrolling, and intrusive popups that cannot be dismissed with a thumb. Each of these is also a signal Google measures.

The viewport tag - one line that changes everything

A missing viewport meta tag makes phones render your site as a shrunken desktop page. It is one line in the page head, present on every modern template - but older sites, custom builds, and some landing-page tools still ship without it.

Mobile speed is its own problem

A site that is fine on office broadband can take 10+ seconds on a phone in a car park. Mobile Core Web Vitals are measured separately by Google and are usually worse than desktop: images sized for big screens, scripts that block rendering, and fonts that load late all hit mobile hardest.

Forms are where mobile visitors give up

Every extra field costs completions, and on mobile the cost doubles. Check your forms trigger the right keyboards (numeric for phone fields, email keyboard for email), that autofill works, and that error messages are visible without scrolling. A form that is merely annoying on desktop is abandoned on mobile.

Check it all in one pass

The AuditHQ technical suite checks mobile responsiveness signals, viewport configuration, tap-target and text-size issues, and mobile Core Web Vitals from Google PageSpeed Insights - with each finding explained and prioritised. The free scan gives you the headline mobile picture in about 60 seconds.

Frequently asked questions