Reputifly editorial · Reviewed 27 September 2026 · 2 min read
Test navigation, forms, images and scroll stability on the devices your visitors actually use.
Test the journey, not a resized screenshot
A responsive layout can look correct and still fail when a visitor opens the keyboard, rotates a phone or returns from another app. Start with a cold load, then complete the main task. Test the browser and device mix visible in your analytics; desktop emulation is useful but is not a substitute for an actual iPhone or Android check.
Reserve space before images arrive
Provide intrinsic image dimensions or a stable aspect ratio so text does not move when an image loads. Use responsive sources sized for the display. Keep important text in HTML rather than baking it into a tiny image, and let visitors expand detailed screenshots when necessary.
For decorative animation, avoid repeatedly changing the height of the surrounding section. A stable image and readable content are better than motion that interferes with scrolling.
Check the mobile controls
- Open and close the menu without losing the current scroll position.
- Confirm sticky headers do not cover anchor destinations or form labels.
- Reach close, next and previous controls comfortably without touching neighbouring targets.
- Verify focus visibility and sensible keyboard order.
- Use the form with the on-screen keyboard open, including validation errors.
Measure stability separately from speed
Core Web Vitals distinguish loading, interaction responsiveness and layout stability. A fast first screen can still jump later. Check the entire journey, especially lazy-loaded media, consent notices and expandable panels.
Write a reproducible defect report
Include the URL, device, browser, steps and expected behaviour. A short recording helps with intermittent scroll problems. Retest the public page after the fix and clear any temporary network overrides used in development. Keep a reduced-motion experience usable without decorative effects.
