CRO Audit
Find the points on a page or flow where visitors lose clarity, trust, interest, or momentum.
Inspect The Page
Use the provided URL, screenshot, copy, or code. If the surface is live, inspect desktop and mobile when possible.
Capture:
- Visitor source and intent.
- Main promise above the fold.
- CTA text, count, and location.
- Form or checkout effort.
- Proof and trust elements.
- Objections addressed or ignored.
- Visual hierarchy and reading order.
- Mobile readability and tap targets.
- Load or rendering issues that affect the decision.
Analyze Friction
Classify each issue:
- Message friction: reader cannot tell what it is, who it is for, or why it matters.
- Trust friction: claim is bigger than proof.
- Choice friction: too many actions or unclear next step.
- Effort friction: form, onboarding, or checkout asks too much too early.
- Timing friction: the ask appears before the reader has enough confidence.
- Mismatch friction: page does not match the traffic promise.
- Technical friction: speed, layout, accessibility, broken states.
Follow The Visitor Decision
Map the page as a decision path:
- Seeing: does the visitor immediately know what this is?
- Believing: does the promise match their intent and feel specific?
- Trusting: is the proof strong enough for the ask?
- Acting: is the next step obvious, low-friction, and appropriately timed?
For each fix, note whether it is reversible. Prefer reversible copy, layout, and proof changes before deep product or pricing changes unless the evidence is strong.
Recommend Changes
Prioritize by likely impact and effort. Include concrete replacement copy or layout changes when useful.
Avoid pretending all pages need the same pattern. A pricing page, waitlist, checkout, and enterprise demo page have different jobs.
Output
Page friction read:
[one paragraph]
Conversion path:
Visitor intent -> Page promise -> Proof -> Action
Hesitation sequence:
Seeing -> Believing -> Trusting -> Acting
Friction log:
| Step | Problem | Evidence | Fix | Reversible | Impact | Effort |
Highest-leverage changes:
1. [change]
2. [change]
3. [change]
Copy replacements:
- Current: [text]
Replace with: [text]
Test next:
- [experiment or measurement]
1---2name: cro-audit3description: Use when reviewing a landing page, homepage, signup page, pricing page, checkout, form, onboarding screen, popup, or paywall for conversion blockers.4---56# CRO Audit78Find the points on a page or flow where visitors lose clarity, trust, interest, or momentum.910## Inspect The Page1112Use the provided URL, screenshot, copy, or code. If the surface is live, inspect desktop and mobile when possible.1314Capture:1516- Visitor source and intent.17- Main promise above the fold.18- CTA text, count, and location.19- Form or checkout effort.20- Proof and trust elements.21- Objections addressed or ignored.22- Visual hierarchy and reading order.23- Mobile readability and tap targets.24- Load or rendering issues that affect the decision.2526## Analyze Friction2728Classify each issue:2930- **Message friction:** reader cannot tell what it is, who it is for, or why it matters.31- **Trust friction:** claim is bigger than proof.32- **Choice friction:** too many actions or unclear next step.33- **Effort friction:** form, onboarding, or checkout asks too much too early.34- **Timing friction:** the ask appears before the reader has enough confidence.35- **Mismatch friction:** page does not match the traffic promise.36- **Technical friction:** speed, layout, accessibility, broken states.3738## Follow The Visitor Decision3940Map the page as a decision path:4142- Seeing: does the visitor immediately know what this is?43- Believing: does the promise match their intent and feel specific?44- Trusting: is the proof strong enough for the ask?45- Acting: is the next step obvious, low-friction, and appropriately timed?4647For each fix, note whether it is reversible. Prefer reversible copy, layout, and proof changes before deep product or pricing changes unless the evidence is strong.4849## Recommend Changes5051Prioritize by likely impact and effort. Include concrete replacement copy or layout changes when useful.5253Avoid pretending all pages need the same pattern. A pricing page, waitlist, checkout, and enterprise demo page have different jobs.5455## Output5657```text58Page friction read:59[one paragraph]6061Conversion path:62Visitor intent -> Page promise -> Proof -> Action6364Hesitation sequence:65Seeing -> Believing -> Trusting -> Acting6667Friction log:68| Step | Problem | Evidence | Fix | Reversible | Impact | Effort |6970Highest-leverage changes:711. [change]722. [change]733. [change]7475Copy replacements:76- Current: [text]77 Replace with: [text]7879Test next:80- [experiment or measurement]81```
Infinite-Labs-AI