What does the mobile website check cover?
The source audit looks for viewport metadata and stylesheet or media-query signals across its sample of up to five public pages. These indicate whether basic responsive setup is present, rather than proving that a page fits a phone screen.
Configured rendered checks load the submitted page with JavaScript in mobile and desktop viewports. They can inspect horizontal overflow, visible image-alternative attributes, form-label signals and small interactive targets. The report shows evidence, viewport information and a pass or review result for each check.
How to investigate horizontal scrolling
If the rendered document is wider than the device viewport, review the affected page on a real phone. Common candidates include fixed-width tables, large images, embedded content and long unbroken text. Check the menu and footer as well as the main content.
Do not simply hide horizontal overflow across the whole page before finding the cause. That can conceal content or controls. Ask your developer to identify the wide element and confirm that the fix works with different text lengths and screen widths.
Check the actions your mobile visitors need
Open navigation, follow the main enquiry or booking route and make sure important buttons remain visible and usable. Check that text can be read, fields have meaningful labels and validation messages appear where a visitor can find them.
The automated rendered check does not click menus, complete bookings, submit contact forms or verify message delivery. Use suitable test details and permission for manual journey checks, especially if a submission could create a real booking or charge.
A mobile check is not an accessibility certification
A control-size or label signal is only one part of accessibility. Colour contrast, keyboard navigation, screen-reader behaviour and alternative-text quality need further testing. Likewise, a clean viewport does not establish that a page is fast or easy to understand.
Combine the mobile findings with the separate performance results and manual checks. Keep the scope visible: this report samples public pages and one rendered page at two viewports, rather than testing every device and customer journey.
Turn the evidence into a useful next step
| Signal | What to review |
|---|---|
| Viewport setup | Check that mobile browsers receive a suitable viewport declaration. |
| Horizontal overflow | Investigate content wider than the rendered device viewport. |
| Controls and labels | Use detected small targets or missing labels as prompts for hands-on testing. |
Google: mobile-first indexing best practices ↗
Use the report’s evidence and scope alongside the relevant documentation for your website. Automated findings are a starting point for investigation.
Questions about this check
Can this tell me if my website is mobile-friendly?
It can highlight defined readiness and rendered-layout signals. It does not award a Google mobile-friendly certificate or replace testing on real devices.
Does the check open my mobile menu?
No. The rendered check inspects a loaded viewport without clicking menus, buttons or forms. Test those interactions yourself.
Can a responsive website still have a low score?
Yes. The overall score includes seven source-check categories. A mobile-ready layout can coexist with issues such as missing page descriptions or image alternatives.
All seven audit categories · How the overall score is calculated · What to fix first