A CRO audit is a structured review of a website’s analytics, technical health, user experience and messaging to find what stops visitors from converting, and to rank those problems by how much fixing them is worth. It is the research step that comes before A/B testing. Done well, it turns “our conversion rate is low” into a prioritized list of specific problems, each with the evidence behind it.
This guide covers the six-part audit process CXL teaches, a checklist you can copy, how to prioritize what you find and the mistakes that make audits useless.
Key takeaways
- An audit is research, not opinions. Every finding should point to data: an analytics drop-off, a recording, a survey answer or a usability test.
- Check tracking first. If analytics is wrong, every conclusion built on it is wrong too.
- Combine quantitative and qualitative data. Analytics shows where people leave; recordings, surveys and user tests show why.
- Prioritize by impact and evidence. A short list of well-evidenced problems on high-traffic pages beats a 200-item spreadsheet.
- Fix obvious bugs immediately. Only test changes where the right answer is genuinely uncertain.
What does a CRO audit cover?
CXL’s ResearchXL model splits conversion research into six areas. Each answers a different question:
| Area | Question it answers | Main sources |
|---|---|---|
| 1. Technical analysis | Is anything broken, slow or missing on certain browsers and devices? | Conversion rate by browser and device, page speed reports, QA on real devices |
| 2. Heuristic analysis | Is each key page clear, relevant and easy to act on? | Structured expert review of each page against a framework |
| 3. Digital analytics | Where in the funnel do visitors leave, and which segments convert worse? | GA4 or product analytics, funnel and segment reports |
| 4. Mouse tracking and recordings | What do visitors actually do on the page? | Session recordings, heatmaps, form analytics |
| 5. Qualitative surveys | Why do visitors hesitate, and what nearly stopped buyers? | On-page polls, customer surveys, sales and support conversations |
| 6. User testing | Can people from the target audience understand the page and complete the task? | Moderated or unmoderated usability tests |
For the method behind step 2, see how to do a heuristic analysis. For step 3, start with an analytics audit.
How to do a CRO audit, step by step
- Define the conversion and the funnel. Write down the primary conversion (demo request, trial, purchase), the micro-conversions leading to it and the pages in between. An audit without a defined goal turns into a list of design preferences.
- Verify tracking. Confirm every step of the funnel fires correctly, that conversions match your CRM or order system within a reasonable margin, and that internal and bot traffic are filtered out.
- Find the leaks with analytics. Build the funnel report and segment it by device, browser, traffic source, new versus returning, and country. Look for the steps and segments that convert far below the rest.
- Run the technical check. Compare conversion rates by browser and device version. Test the funnel on the worst performers. Check page speed on mobile for the highest-traffic templates.
- Review key pages heuristically. Assess each page in the funnel for clarity of the value proposition, relevance to the traffic source, friction, distraction and anxiety. Note every issue with a screenshot.
- Collect qualitative evidence. Watch at least 50 to 100 session recordings of visitors who dropped off, run an exit poll on the leakiest page, survey recent customers about what nearly stopped them, and run five or more user tests with your target audience.
- Synthesize and prioritize. Group findings into problems, attach the evidence to each, and score them (see below). Fix bugs right away, and turn the uncertain, high-impact problems into test hypotheses.
CRO audit checklist template
Copy this into a spreadsheet. Add a column for status, evidence and owner.
| Area | Check |
|---|---|
| Tracking | Primary conversion tracked and matches back-end data |
| Tracking | Each funnel step tracked as an event |
| Tracking | Internal, staging and bot traffic excluded |
| Tracking | Campaign UTMs consistent so traffic sources can be trusted |
| Technical | Conversion rate by browser and device reviewed; outliers tested by hand |
| Technical | Mobile page speed checked on top landing pages |
| Technical | Forms validate correctly and show helpful error messages |
| Technical | No broken links, images or scripts on funnel pages |
| Analytics | Funnel drop-off by step identified |
| Analytics | Conversion rate by traffic source, device and new versus returning compared |
| Analytics | Top landing pages ranked by traffic and conversion rate |
| Analytics | Internal site search terms reviewed for unmet needs |
| Messaging | Value proposition clear within five seconds on key pages |
| Messaging | Headlines match the promise of the ads and emails that drive traffic |
| Messaging | Pricing and plan differences easy to understand |
| Messaging | Proof (logos, numbers, reviews, case studies) placed next to claims |
| UX | One clear primary call to action per page |
| UX | Forms ask only for what is needed at this stage |
| UX | Navigation lets visitors find pricing, product and proof quickly |
| UX | Mobile layout keeps the call to action visible and tappable |
| Behavior | Recordings of drop-offs reviewed on the leakiest pages |
| Behavior | Heatmaps reviewed for ignored content and false clickable elements |
| Behavior | Form analytics reviewed for fields that cause abandonment |
| Voice of customer | Exit or on-page poll running on the leakiest page |
| Voice of customer | Recent customers surveyed on hesitations and alternatives considered |
| Voice of customer | Sales and support asked for the most common objections |
| User testing | At least five target users tested on the core task |
| Prioritization | Every finding has evidence, a page and an estimated impact |
| Prioritization | Bugs and clear fixes separated from test hypotheses |
How to prioritize CRO audit findings
Use a scoring model that rewards evidence and traffic, not enthusiasm. CXL’s PXL framework asks yes-or-no questions such as: is the change above the fold, is it noticeable within five seconds, is it supported by user testing, qualitative feedback or analytics, and how easy is it to build. Binary questions make scores harder to inflate than 1 to 10 ratings. See how PXL works.
Then sort findings into three buckets:
- Fix now: bugs, broken tracking and clear usability failures. Testing them wastes traffic.
- Test: high-impact changes where the right answer is uncertain, on pages with enough traffic. Check with the A/B test calculator.
- Research further: problems you can see but not yet explain.
Common CRO audit mistakes
- Auditing opinions instead of evidence. “The button should be green” is not a finding. “62% of mobile visitors never scroll to the button” is.
- Skipping tracking validation. Teams regularly discover that a funnel step was never tracked, after weeks of analysis.
- Treating every page equally. Start with the pages that carry the most traffic and revenue.
- Delivering a list nobody acts on. An audit is finished when its top findings are fixed or in a test, not when the report is sent.
When a CRO audit is not the right next step
- The site gets very little traffic. With a few hundred visitors a month, talk to customers and fix positioning first. Funnel analytics will not have enough data to show patterns.
- The offer is the problem. If buyers don’t want what you sell at that price, page changes won’t fix it. Customer research comes first.
- You are about to rebuild the site. Run the research parts of the audit to inform the rebuild, but skip page-level fixes on pages that are going away.
CRO audit FAQ
What is a CRO audit?
A CRO audit is a structured review of a website’s tracking, technical health, user experience and messaging to find what stops visitors from converting, backed by analytics, behavior data and customer research, and ranked by potential impact.
How long does a CRO audit take?
For a typical B2B or ecommerce site, two to four weeks: about a week for tracking and analytics, a week for heuristic review and recordings, and time for surveys and user tests to collect responses.
What is the difference between a CRO audit and a UX audit?
A UX audit focuses on usability. A CRO audit includes usability but also covers tracking, traffic-source fit, messaging, offer and prioritization by business impact, and it feeds directly into an A/B testing roadmap.
Can I do a CRO audit myself?
Yes, with free tools: GA4 for analytics, Microsoft Clarity for recordings and heatmaps, a free survey tool and a handful of user tests. The hard part is not the tools but judging the evidence without bias, which is a learnable skill.
Learn to run CRO research properly
CXL is a B2B marketing training company focused on AI and conversion optimization. The audit process above is the foundation of CXL’s CRO course and certification. For the full picture of the discipline, read the conversion rate optimization guide, and for the tools, see the best CRO tools.


