Mobile readiness website checks
Mobile website checks examine viewport configuration, overflowing content and controls that are difficult to use on a narrow display. A screenshot records one width and state; it cannot establish usability in every orientation or text scale. The public crawler also cannot inspect states that require login or submission. Use findings to select journeys for hands-on testing.
Try the smallest supported width before widening the page. Check navigation, long labels, tables, consent controls and error messages with enlarged text. Confirm that targets have enough separation and fixed banners do not cover the focused control. Exercise touch and keyboard input in portrait and landscape, and verify that a layout fix does not hide content elsewhere.
The check pages below describe the exact observable condition, why it matters, practical fixes and the limits of the detector. Open the affected URL and inspect its evidence before making a change. After correction, repeat the scan and verify the result in a browser. The related guide connects these individual checks into a review workflow. Keep deliberate exceptions documented so that a passing automated result is never mistaken for a complete manual assessment.
Checks and fixes
Apple Touch Icon Missing: Declare and Test the Home-Screen Asset
Add an appropriate Apple touch icon, verify the actual image and saved-site result, and recognise where filename and icon-count heuristics misclassify it.
Images Without Srcset: Deliver Suitable Responsive Resources
Review images without srcset. Match candidates and sizes to actual layout and density, prioritise useful savings, and test the resources the browser selects.
Slow LCP on Mobile: Diagnose the Measured Critical Path
Improve mobile LCP by finding the candidate and delay. Compare lab and field conditions, prioritise resources, and understand the shared score.
Tap Targets Too Small: Measure CSS Size and Applicable Exceptions
Review small tap targets using CSS pixels and WCAG exceptions. Measure active areas, preserve useful spacing, and separate scan severity from conformance.
Viewport Meta Tag Missing: Declare the Intended Mobile Layout
Fix a missing or empty viewport declaration. Set a suitable responsive baseline, preserve zoom, and test actual layout rather than presence-only metadata.
Viewport Width=Device-Width Missing: Review the Configuration
Review a viewport without explicit width=device-width. Understand fixed-width and scale behaviour, preserve zoom, and verify real breakpoints and layout.