Mobile-Friendly Website Checklist

Most people will meet your website on a phone first. Use this checklist to check whether the experience is genuinely comfortable, not merely technically functional. Test on a real device wherever possible.

Layout

The page fits the screen with no sideways scrolling
The viewport meta tag is present. See responsive design basics
Content reflows sensibly when zoomed
Nothing is cut off, overlapping, or hidden behind fixed headers
Images scale to fit

Text

Body text is comfortably readable without zooming, generally 16 pixels or larger
Line length and spacing are comfortable. See readable text
Contrast is sufficient, including in bright light. See color contrast

Touch

Buttons and links are large enough to tap accurately
There is enough space between tappable items. See touch target sizes
Nothing depends on hover to work
Phone numbers are tappable, and addresses open maps

The menu opens and closes easily and is simple to use
Visitors can reach key pages in a few taps. See navigation best practices
The main call to action is easy to find. See calls to action

Forms

Fields are large and clearly labelled
The right keyboard appears for email, phone, and numbers
Autofill works
Error messages are clear. See accessible forms and contact form design

Content parity

The mobile version contains the same important content as desktop, since Google uses mobile-first indexing. See mobile-first design
Structured data and meta tags are present on mobile

Speed

Pages load quickly on a typical mobile connection. See how to test website speed
Images are compressed and sized properly. See compressing images
Layout does not jump around while loading. See Core Web Vitals

Interruptions

Pop-ups do not cover content or are easy to dismiss
Cookie banners do not block the whole page. See cookie banner basics

Real-world testing

Try your site on at least one iPhone-sized and one Android-sized screen, and on a slow connection. Ask someone unfamiliar with the site to complete a task, such as finding opening hours or submitting a request.

Fix in priority order

Handle anything that blocks a visitor from reading or taking action first, then polish.

The bottom line

A mobile-friendly site is readable, tappable, quick, and complete. Run this checklist after every significant change.