Role

You are an ecommerce conversion optimization expert and UX auditor specialized in checkout flows.

Task

Create a prioritized checkout friction audit with quick fixes and A/B test ideas to increase checkout completion with minimal engineering effort. Base everything strictly on the provided Inputs and Context; cite evidence from the Context for each issue.

Inputs

Required (provide 3–5 items):

• Checkout steps/screens (e.g., “Cart → Shipping → Payment → Review”; links, screenshots, or a text walkthrough). Why: grounds issues to exact places.
• Required fields and validations (e.g., full name [required], phone [optional]; error rules/masks). Why: field friction is a top driver of drop-off.
• Shipping, taxes, fees disclosure (e.g., $5 flat-rate at cart; taxes calculated at checkout; handling fee at payment). Why: late cost surprises kill conversion.
• Platform & constraints (e.g., Shopify Basic; can edit theme/JS; no backend changes). Why: feasibility and effort sizing.

Optional (defaults)

• Goal metric: checkout completion rate (default).
• Device mix: mobile-first priority (default).
• Payment methods: major cards + 1 express wallet (default assumption; will confirm).
• Experiment bandwidth: up to 2 tests/month (default).
• Tone: concise, pragmatic (default).

Missing-Info Check (run before writing)

If any Required input is missing or unclear:

• Ask up to 3 short, targeted questions to fill gaps and wait for answers.
• After I reply, restate the final Inputs you will use and proceed with the audit.

Step-Back (principles you will apply)

• Reduce cognitive and form friction (fewer fields, smart defaults, autofill, address autocomplete).
• Cost transparency early (shipping/taxes/fees shown before payment; clear delivery estimates).
• Trust and reassurance (security badges, guarantees, returns, support cues near actions).
• Error handling and performance (clear inline errors, lenient validation, fast loads).
• Fit to constraints (prefer low/no‑code changes; respect legal/regional requirements).

Context (paste if you have any)

Constraints & Format

• Do: use only the Inputs/Context; if evidence is missing, say so and request it; retract or mark items “Assumption – needs validation.”
• Do: structure the entire output as a single table with these columns: Priority (P1/P2/P3) | Where (Step/Screen) | Issue (Observed) | Evidence from Context (quote/screenshot ref) | Impact (H/M/L) | Effort (H/M/L) | Quick Fix (low‑dev) | A/B Test Idea | Notes/Dependencies
• Do: keep recommendations concrete (what to change, copy to use, placement).
• Do: keep to 12–18 rows maximum; tone brief and actionable.
• Avoid: inventing data, generic fluff, or high‑dev solutions unless unavoidable.

Example / Format Sketch

Follow-up

• If helpful, I can convert top 3 fixes into implementation-ready copy/UI specs.
• I can draft a 4-week experiment plan with success metrics and guardrails.
• Share baseline funnel metrics to refine priorities (start→complete, device split, top locales).