In this guide: Test your website on mobile with a practical workflow for layouts, navigation, forms, accessibility, performance and repeatable verification.
Your mobile audience share depends on the website and its visitors; check your analytics instead of assuming a universal split. Google also uses mobile-first indexing, meaning it primarily evaluates the mobile version of your site. A page that works on a laptop can still prevent phone users from reading content or completing a task.
Chrome DevTools (and other browsers’ developer tools) can simulate mobile devices:
F12 (or Cmd + Option + I on Mac).Ctrl + Shift + M (Cmd + Shift + M on Mac).Also try:
Emulation is fast and convenient, but it’s not perfect: it doesn’t fully replicate real touch behavior, real device performance, mobile browser UI quirks, or iOS Safari rendering.
Always test on at least one real iPhone and one real Android phone.
Test key journeys:
Tiny text — body text should be comfortable to read (typically around 16 px or larger).
Buttons and links too close together — make targets comfortable to use with suitable spacing, and review the applicable accessibility criteria and exceptions.
Horizontal scrolling — caused by wide images, tables, or fixed-width elements. Make tables scrollable within their container and images responsive.
Intrusive popups — full-screen popups that block content on mobile frustrate users and can hurt search visibility. Use small, easy-to-close banners.
Unoptimized images — large images slow down mobile loading. See How to Optimize Images for the Web.
Fixed headers taking too much space — sticky headers should be compact.
Forms that are hard to fill — use correct input types (type="email", type="tel") so phones show the right keyboard, and enable autofill.
Hover-only features — menus or tooltips that require hovering don’t work on touch screens.
Layout shifts — ads or images loading late push content around. See Core Web Vitals Explained.
tel: links).Add mobile testing to every launch — it’s part of our Launch Checklist.
To test your website on mobile meaningfully, begin with the tasks a visitor needs to complete. A screenshot of the homepage cannot establish that the navigation works, the contact form delivers an enquiry or the checkout displays the correct order. Choose representative pages and follow the same journeys on each device you can access.
The examples below are a testing framework, not results from a laboratory benchmark of your site. Record the browser, operating system, screen orientation, network and account state alongside each finding. When you test your website on mobile, these details help distinguish a reproducible defect from a problem caused by an extension, a stale cache or an unusual local setting.

Select the homepage, a long article, a category or search page, and an important service or product page. Include contact, sign-in and purchase journeys when relevant. Start with devices represented in your analytics and add a different browser family where possible. If you cannot access a device, record it as untested rather than claiming full coverage.
A practical first pass can use responsive browser mode plus available real phones. Add portrait and landscape, a clean logged-out session and any relevant logged-in state. You do not need to own every handset to test your website on mobile, but you do need to be explicit about the coverage and the limitations.
Record one expected result for each journey. For example, “The visitor can open the menu, select the contact page, submit a permitted test enquiry and see confirmation.” Keep the steps short enough that another person can reproduce them. This is more useful than a vague instruction to check whether a page looks good.
Open the device toolbar and resize the viewport gradually. A layout can work at two popular presets and fail between them. Check the point at which the navigation changes, cards wrap and columns collapse. When you test your website on mobile, use the width that exposes the defect rather than forcing every problem into a named phone model.
Look for unexpectedly wide images, embedded content, code examples and tables. Identify the component responsible for overflow instead of hiding horizontal overflow on the whole page as a blanket fix. Hiding the symptom can also hide content or focus indicators. A wide data table may need its own scrollable container while the rest of the article remains within the viewport.
Check that the page has an appropriate viewport configuration and that zoom remains available. A common responsive starting point is shown below. Do not add restrictions that prevent visitors from enlarging content merely to keep a layout visually fixed.
<meta name="viewport" content="width=device-width, initial-scale=1">
For a media element, provide intrinsic dimensions and responsive presentation appropriate to the design. These attributes describe the image’s proportions; CSS controls how it fits the available space. After a change, test your website on mobile again at narrow and intermediate widths.
<img src="example.webp" alt="Describe the useful content"
width="1200" height="675"
style="max-width:100%;height:auto">
Open and close the mobile menu several times. Follow a submenu, return to the previous page and check that the menu state makes sense. Test the close control and the area around it. A navigation component should not depend on hovering, and the first tap should not unexpectedly activate a different link behind an overlay.
When you test your website on mobile, inspect sticky headers and floating buttons on long pages. They can cover anchor destinations, form controls or the bottom of a dialog. Check what happens after rotating the device and after the browser’s address bar changes size during scrolling. A fixed screenshot may miss those states.
Where a keyboard is available, check focus visibility, tab order and whether a dialog or navigation drawer can be exited. Use meaningful accessible names for controls; an icon alone may not explain what the button does to a screen reader. Do not assume touch support makes keyboard behavior irrelevant.
Use an appropriate test address and non-sensitive sample data. Check required fields, validation messages and the confirmation after submission. Test longer names, international telephone formats when relevant, and an intentional error. To test your website on mobile fully, verify that the enquiry reaches the expected destination rather than stopping at the visual success message.
Labels should remain clear while typing. Use input types and autocomplete attributes that match the information requested. The example below illustrates a labeled email field; it is not a complete submission system. The form still needs accessible validation, a working server endpoint and appropriate handling of the submitted information.
<label for="email">Email address</label>
<input id="email" name="email" type="email"
autocomplete="email" required>
Open the on-screen keyboard and check whether it obscures the active field or submit button. Move between fields, correct an error and return from a confirmation page. Avoid requesting unnecessary information just because the desktop layout has space for it. Every field adds work on a small screen.

Read an entire section rather than inspecting the first heading only. Check body text, captions, quotations, tables and inline links. Increase text size or zoom using the device’s supported controls and confirm that content remains usable. When you test your website on mobile, look for clipped text and controls that stop working after enlargement.
Comfortable touch targets are a design goal, but different accessibility criteria have specific requirements and exceptions. WCAG 2.2’s target-size minimum criterion uses 24 by 24 CSS pixels with defined alternatives and exceptions; enhanced guidance uses a larger threshold. Consult W3C’s target-size explanation rather than describing one number as a universal compliance rule.
Check spacing in dense navigation and article links, not only the primary call-to-action. A visitor should be able to select the intended control without repeatedly hitting its neighbor. Contrast, focus indication and clear wording also matter. A large button with an ambiguous label can still create a poor experience.

A page can fit the screen and still respond slowly. Test opening the menu, typing into search, expanding an accordion and interacting with filters. Watch the main content appear and observe whether the layout jumps. To test your website on mobile effectively, investigate loading, responsiveness and stability separately.
Use browser diagnostics to examine resource requests and expensive processing. Record whether the test was cold or already cached and whether network throttling was enabled. Device emulation approximates some mobile conditions; it does not reproduce every real device limitation. Chrome describes that scope in its Device Mode documentation.
Use the actual LCP, INP and CLS information where available rather than equating a Lighthouse score with a complete pass. Our Core Web Vitals guide explains the distinction between field reports and laboratory investigation. If there is insufficient field data, report that limitation explicitly.

For each defect, record the affected component, the steps to reproduce it and the expected behavior. After a targeted fix, repeat those steps under the same conditions. Then check a neighboring layout width and a related page. A change to a shared header can affect many templates, while a specific oversized image may affect only one article.
Keep functional checks with the layout checks. When you test your website on mobile after a change, ensure that forms still submit, menus remain accessible and private content stays isolated. If you use a staging copy, prevent it from processing real payments or sending unnecessary customer messages during testing.
Repeat a short mobile regression checklist after meaningful theme, advertising, consent, form or commerce updates. A layout that worked at launch may break when another component is added. Assign an owner and keep a dated test record so the review becomes routine maintenance rather than an emergency after visitors complain.
| Field | What to record | Example description |
|---|---|---|
| Page and state | URL, login state and relevant consent choice | Public service page in a clean session |
| Environment | Device, browser, version and orientation | Available Android phone in portrait |
| Steps | The shortest repeatable sequence | Open menu, select contact, focus email field |
| Observed result | What happened without speculation | Keyboard covers the remaining controls |
| Expected result | The task the visitor should complete | All fields and submit control remain reachable |
| Verification | Retest date and result | Repeat on the original device and another width |
Use sample content in evidence whenever possible. Avoid capturing private messages, account details or customer payment data in screenshots shared for debugging. A useful report makes the defect reproducible without exposing more information than the person fixing it needs.
Open an actual published link from the social platform when you can do so safely. In-app browsing can differ from opening the same URL directly in Safari or Chrome. Check redirects, consent screens, navigation, external links and the primary call-to-action. Record which application and browser context you used rather than assuming every social platform behaves identically.
If the article is intended to attract traffic from America, Canada, Britain, Ireland, Australia or New Zealand, keep the content and customer journey relevant to those audiences. Test the applicable currency, contact format or delivery flow where the site offers regional features. Do not assume that changing a country label proves the underlying regional experience is correct.
Preserve tracking parameters when testing a campaign link, but verify that they do not lead to a broken or different page. Use analytics to compare mobile visits and successful actions by source. When you test your website on mobile, a high click count does not establish that readers could use the page after arriving.
Wide tables: provide a usable table-specific overflow solution and a clear indication that more columns exist. Preserve headings and relationships. Do not shrink the entire page until the text becomes unreadable. Retest with longer cell content and with zoom.
Embedded videos: use a responsive container and reserve the correct proportions. Check the controls in portrait and landscape. A late embed should not unexpectedly push the paragraph a visitor is reading out of view.
Popups and notices: verify that the close control is reachable and that important content remains accessible. Check the keyboard and focus behavior as well as touch. A design that appears compact on one phone may occupy most of another phone’s visible area.
Slow images: inspect dimensions, transfer size and loading priority. Do not lazy-load the immediately needed main image merely because it is an image. See our image optimization guide, then test your website on mobile again with representative conditions.
Google’s mobile-first indexing guidance emphasizes the mobile content used for indexing. Check that important text, headings, images and links remain available on the mobile version. Do not remove useful content purely to make a small-screen layout look simpler without considering how readers will access it.
A good mobile experience is worthwhile, but it does not guarantee rankings or a specific number of visits. Use Search Console to observe search performance and Analytics to understand what visitors do after arriving. When you test your website on mobile, keep technical findings separate from assumptions about future traffic.
No. It is useful for quick layout and diagnostic checks, but real devices can reveal touch, keyboard, browser and performance differences. Combine the tools you have and state what remains untested. The goal is evidence about the important journeys, not an unsupported claim of compatibility with every device.
Not necessarily. Begin with available phones, browser diagnostics and a documented checklist. A remote device service can expand coverage when your needs justify its cost, but it is not a substitute for deciding what to test. Verify the service’s current device availability and terms before paying.
For your own site, repeat important journeys after meaningful changes and review the coverage as the audience changes. A frequently updated store may need a different routine from a static portfolio. Prioritize components shared across many pages and the tasks visitors rely on most.
Start with defects that prevent access or completion of important tasks, such as unusable navigation, broken forms or incorrect account behavior. Then address readability, layout and measured performance problems. Reproduce each issue, make a targeted change and verify the result instead of enabling unrelated optimization settings.
We may earn a commission on purchases made through these links, at no extra cost to you.
Don’t miss the chance to participate in the biggest giveaway of this year.