Mobile UX Audit
by @leooooooow
Audit the mobile shopping experience of an ecommerce store for friction points including page load speed, thumb-reach interactions, form length, checkout flo...
clawhub install mobile-ux-auditπ About This Skill
name: mobile-ux-audit description: Audit the mobile shopping experience of an ecommerce store for friction points including page load speed, thumb-reach interactions, form length, checkout flow, and pay-method breadth. Use when mobile conversion rate is lagging desktop, before a major redesign, or quarterly as a hygiene pass.
Mobile UX Audit
Mobile is usually 65β80% of ecommerce traffic and ~50% of revenue. The gap between traffic share and revenue share is the audit's job: find the thumb-reach errors, the slow hero images, the checkout fields that kill the sale.
Quick Reference
| Decision | Strong | Acceptable | Weak | |---|---|---|---| | LCP (Largest Contentful Paint) | β€2.0s on 4G | 2.0β2.5s | >2.5s | | INP (Interaction to Next Paint) | β€150ms | 150β300ms | >300ms | | CLS (Cumulative Layout Shift) | β€0.05 | β€0.1 | >0.1 | | Tap targets | β₯44Γ44pt with β₯8pt spacing | 40pt with tight spacing | <40pt, close together | | Checkout fields | β€8 fields, one-page | 10β12 fields, 2 pages | 15+ fields, 3+ pages | | Pay methods | Apple Pay, Google Pay, card, 1 local | Card + PayPal | Card only | | Guest checkout | Default, no account required | Account optional after checkout | Forced account creation |
Problems this skill solves
1. Conversion rate 40% lower on mobile than desktop with no clear diagnosis. 2. Cart abandonment spiking at the address-entry step β usually a mobile-keyboard/autofill problem. 3. PDP hero image taking 4+ seconds to load because the team uses the same 3000px-wide asset as desktop. 4. Checkout buttons in the top third of the screen requiring an awkward thumb stretch. 5. Apple Pay / Google Pay not enabled on a store where 70% of users are on iOS or Android. 6. Modals and popups that cover the close button on small screens. 7. Tap targets smaller than the thumb pad, producing fat-finger errors on filters and quantity steppers.
Workflow
Step 1 β Measure Core Web Vitals in the field
Pull the last 28 days of real-user metrics from PageSpeed Insights (CrUX), Google Search Console, or your RUM tool (Datadog, New Relic, Sentry, or Shopify's built-in). Record p75 LCP, INP, CLS for mobile. Compare to the Quick Reference table. Lab-test tools (Lighthouse) give consistent scores but do not reflect real users β always lead with field data.
Step 2 β Walk the funnel on a real device
Not an emulator, not Chrome DevTools device mode. Use an actual iPhone and an actual mid-range Android (Pixel 6a or similar β not the latest flagship). Walk: home β category β PDP β add to cart β cart β checkout β payment. Note every friction: slow load, mis-sized tap target, layout shift, confusing state, keyboard-covers-field moment.
Step 3 β Audit thumb reach
The comfortable thumb zone on a 6-inch phone is the bottom two-thirds of the screen. Anything in the top third (headers, close buttons, primary CTAs) requires a reach or a hand shift. Map every primary CTA on the funnel and flag anything above the middle.
Step 4 β Audit form fields
List every field in the checkout. Score each: required or optional, keyboard type (email, tel, numeric), autocomplete attribute, inline validation. Target β€8 required fields total. Common kill-fields: "confirm password," "phone number for delivery updates," "how did you hear about us."
Step 5 β Audit the payment step
List enabled pay methods. For every market the store serves:
Step 6 β Image and asset audit
width and height attributes or aspect-ratio boxes). element.Step 7 β Document findings with priority
Produce a ranked list: P0 (blocks checkout), P1 (measurably hurts conversion), P2 (polish). Each item gets the friction described, the screen(s) affected, and a concrete fix.
Example 1 β Shopify store, 62% mobile traffic, 28% mobile conversion rate vs. desktop
Findings from a 2-hour audit:
Estimated combined lift: 20β30% on mobile conversion over 4β6 weeks after deployment.
Example 2 β Headless store (Next.js + commerce API), strong desktop, poor mobile INP
The team already optimizes LCP and CLS and has green Core Web Vitals on desktop. Mobile INP is 420ms β users tap and nothing happens for nearly half a second.
Strong teams still have mobile-INP debt. The fix is usually "less JavaScript on tap," not "smaller hero image."
Common mistakes
1. Auditing only on the latest iPhone. A mid-range Android at 4G is the real median user. 2. Using Lighthouse as the only signal. Lab scores miss cold-start jank and main-thread contention. 3. Treating mobile as "desktop minus width." The thumb pattern, keyboard behavior, and attention span are fundamentally different. 4. Fixing LCP with a CDN and declaring victory. LCP is three factors: server response, render-blocking resources, and hero-asset size. The CDN only touches one. 5. Forcing account creation before checkout. This is a 20%+ conversion hit on cold traffic. 6. Modals with no visible close button on 4-inch screens. Test on a small device; buttons crop out. 7. Infinite-scroll product listing without pagination cues. Users feel lost and leave. 8. Autoplay video on mobile. Eats data, battery, and autoplay policies often block it anyway. 9. Sticky headers that eat 20% of vertical real estate. On a phone, every pixel counts. 10. Not testing with JavaScript disabled. Many mobile users have flaky JS loading; a site that only works with full JS is broken for them.
Resources
references/output-template.md β Audit report template with P0/P1/P2 structure.references/core-web-vitals.md β How to measure and interpret LCP, INP, CLS in the field.references/checkout-checklist.md β Mobile checkout audit checklist with field-by-field notes.references/thumb-zones.md β Thumb-reach diagrams and interaction patterns.assets/mobile-audit-checklist.md β Full pre-publish audit checklist.