The Mobile-Friendly Website Checklist for Small Businesses

“Responsive” and “mobile-friendly” aren’t the same thing. A site can technically shrink to fit a phone screen and still be frustrating to use: buttons too small to tap, a phone number you can’t press, a form that fights you on every field.

For a Sedona business, that matters. Many customers find you on a phone, often while they’re out driving, walking around Uptown or standing at a trailhead. And Google uses mobile-first indexing, which means it primarily looks at the mobile version of your site when deciding how to rank it. Our local SEO checklist covers where this fits in local search.

Here’s a checklist you can work through on your own phone.

Are the mobile basics in place?

• The page fits the screen. No sideways scrolling, no zooming out to read.
• The viewport is set correctly. Your developer will know this as the viewport meta tag. Without it, phones show a shrunken desktop page.
• Nothing important is hidden on mobile. With mobile-first indexing, content you remove from the mobile layout may not count in search. Collapse long sections if you like, but don’t delete them.
• No full-screen popups on arrival. Popups that cover the page as soon as someone lands are especially annoying on a phone, and Google has long advised against intrusive interstitials.
• The mobile menu is easy to open and close, with a clearly labeled button, and your most important pages are in it, not buried three levels deep.
• Long pages have clear headings so people can scan to what they need, and visitors can always get back to the homepage.

Are your buttons and links easy to tap?

Fingers are less precise than a mouse pointer.

• Buttons and links are large enough to tap comfortably. WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels for AA. Bigger is better for main buttons.
• Links have space around them, so tapping one doesn’t hit its neighbor.
• Menu items in the mobile navigation are well spaced.
• Your main call to action, such as Book, Call or Get a Quote, is easy to find without scrolling far.

Do this: a full-width “Book a Tour” button. Not this: a small text link squeezed between two other links.

Tap target size is also an accessibility requirement; our accessibility guide explains how to give tap targets enough room for people with limited dexterity.

Can people call or email you with one tap?

The phone number is often the most important thing on a local business’s mobile site.

• Your phone number is a tap-to-call link (tel:), not plain text or an image.
• It’s in the header or very easy to reach from every page.
• Email addresses use mailto: links where you list them.
• If you take text messages, say so clearly and consider an sms: link.

Test each one. A typo in a tel: link sends calls to a stranger.

Can visitors read your text without zooming?

• Body text is comfortable to read on a phone. Around 16 CSS pixels is a common baseline.
• Line length is short enough that reading isn’t tiring, and line spacing isn’t cramped.
• Text contrasts clearly with the background. Light gray text on a white background is hard to read in bright Arizona sun. Our accessibility guide shows how to check your color contrast.
• Text never sits over a busy photo without a solid or darkened backing.
• Headings are short. Long headings wrap into four or five lines on a narrow screen.
• Menus, prices and hours are text on the page, not a PDF or an image someone has to pinch and zoom.

Are your forms easy to fill in on a phone?

Forms are where many mobile visitors give up.

Do this	Not this
Ask only for what you need	A long form “just in case”
type="tel" and type="email" fields that bring up the right keyboard	Plain text fields for everything
autocomplete attributes so phones fill in name, email, phone and address	Making people type every detail
Labels that stay visible above each field	Placeholder text that disappears as you type
Clear error messages next to the field with the problem	A red outline and no explanation
An obvious submit button and a clear confirmation	A form that quietly resets after sending

Booking widgets and date pickers are a common weak spot. If you use a third-party booking tool, test its full checkout on a phone; our post on tour company websites explains why you should design the mobile checkout first.

Can people find you from their phone?

Visitors who arrive by car need to find you quickly.

• Your address is written as text, so phones can recognize and copy it.
• There’s a “Get directions” link that opens the phone’s own map app.
• An embedded map, if you use one, doesn’t trap scrolling. Big embedded maps can catch people’s thumbs as they scroll the page.
• Parking or arrival tips are on the page if your location is tricky to find.
• Key details like hours and address are near the top of the contact page, not below a large map.

Cell signal can be patchy in canyons and on trails around Sedona. Directions and hours that load as plain text are far more reliable than a heavy map that might not load at all. For meeting points that are hard to find, see our advice on directions and meeting points.

Is the site fast on a real mobile connection?

A mobile-friendly site that takes too long to load still loses visitors. Google measures loading, responsiveness and visual stability with its Core Web Vitals: LCP, INP and CLS.

• Images are resized and compressed for the web. Our guide to preparing photos for the web walks through it.
• No autoplaying header video on mobile.
• Third-party scripts like chat widgets and social feeds are kept to a minimum.
• The layout doesn’t jump around while loading.

See how to check your site’s speed for what to look at in PageSpeed Insights.

Which tools should you test with?

Desktop browser previews are useful but not enough. They don’t show you what a real thumb, a real screen in sunlight or a real weak connection feels like. Use a mix:

Tool	Good for	What it misses
Your own phone and an older one	How the site really feels to tap, read and book on	Problems on devices you don’t have
Browser developer tools (device mode, throttling)	Quick layout checks at many screen sizes and slow connections	Real touch, real screens in sunlight
Lighthouse and PageSpeed Insights	Performance and many accessibility issues	Whether a task is actually easy to complete
Watching someone else	Where real people hesitate or get stuck	Technical causes of the problem

Google retired its standalone Mobile-Friendly Test, so these are now the practical options. The step-by-step process below shows how to combine them.

If your site fails more of these checks than you’d like, a few targeted fixes are sometimes enough, and sometimes a website redesign is the better answer. If you’re starting fresh, ask for a web design process that plans the phone layout first rather than treating it as an afterthought.