Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01Review critical screens from narrow mobile to wide desktop
- 02Find fixed widths, overflow and tiny controls
- 03Check order changes when grids collapse
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Set content-led breakpoints
- 02Prioritize primary information on narrow screens
- 03Use flexible type, media and touch targets
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Test real devices and browser zoom
- 02Rotate and resize during active tasks
- 03Check long content and software keyboards
Common pitfall
A shortcut to avoid
A clean mobile screenshot can hide broken intermediate widths and interactive states.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.