Mobile product page audit for fashion e-commerce

Capture a reproducible starting point

Record the URL, product and variant, market, language, device, browser version, date and connection conditions. Include a normal product, a sale item and an item with unavailable sizes. Review a fresh visit and a return visit, including consent and other overlays. Browser emulation helps cover widths; use a real phone for touch, the on-screen keyboard and browser behaviour. Remove personal information from evidence shared with the team.

Check the offer before asking for a click

Can the visitor identify the product, selected colour, current price and relevant sale conditions without guessing? Check readable text, useful image zoom, material and care information, and delivery and return information for the chosen market. Compare the ad or collection promise with the destination. Verify shipping and availability claims against their source. Sticky bars, cookie notices and promotional layers should not cover essential information or the next action.

Follow size and variant changes

Select an available size, change the colour and return to the original variant. Check whether price, image, availability and selected state still agree. An unavailable size must be distinguishable without relying on colour alone. Open and close the size guide, then confirm that the choice remains intact. For measurement definitions and fit-research design, continue to the dedicated size-and-fit guide; this audit records whether the product journey works as intended.

Verify the handoff to the cart

Try adding without a required selection, then add a valid item. Check the error message, loading feedback and the actual cart line: SKU, size, colour, quantity and price. A second tap must not silently create an unintended duplicate. Test quantity changes, removal and returning to the product. Investigate network failures without treating an animation as proof of a successful add. Use an approved test environment for any order or payment testing.

Review access and interaction barriers

Test keyboard order, visible focus, control labels, zoom and closing dialogs without losing the place in the page. Check that errors explain how to recover. WCAG 2.2 target-size guidance sets a 24 by 24 CSS-pixel minimum with defined exceptions, including spacing; larger primary controls can be more comfortable. Review the applicable criteria, contrast and assistive-technology behaviour together. A quick mobile checklist is not a full accessibility conformance audit.

Source: W3C: target size and spacing ↗

Separate speed evidence from the action decision

Use lab traces to diagnose loading, interaction delay and layout shifts, then compare with available real-user data. Google’s good Core Web Vitals thresholds are LCP at most 2.5 seconds, INP at most 200 milliseconds and CLS at most 0.1, assessed at the 75th percentile with mobile and desktop separated. Record the URL or origin scope and measurement window; missing field data is unknown, not a pass. A single lab score does not prove conversion uplift.

Source: Google: Core Web Vitals ↗

Use this at work

1. Record scope, state, reproduction steps and supporting evidence.
2. Separate verified blockers, missing information and hypotheses.
3. Assign priority from impact, reach and confidence; name an owner.
4. Write acceptance criteria and retest the original scenario.
5. Use the A/B test plan for uncertain improvements, with downstream guardrails.