The 248 CRO Audit Criteria We Check (and Why Most Audits Miss Half)

Last updated: July 2026 · By The CROBenchmark Team

CRO audit criteria are the individual, checkable rules an audit scores your store against, from headline clarity to the number of checkout fields, so a finding is a specific fault rather than a vague opinion. CROBenchmark evaluates every store against 248+ documented criteria across five page types, benchmarked across 7,000+ stores in 15+ industries, 8 eCommerce platforms, and 65 countries. Most free tools check fewer than 50 surface items and miss the criteria that most reliably predict conversion loss. You can see which criteria your store fails with a free CROBenchmark audit.

Why criteria count matters for audit quality

A checklist can only ever surface the issues it contains, so a 30-item audit has a hard ceiling of 30 possible findings, and your real conversion barrier is often outside that narrow scope. Depth is not a vanity number; it is the difference between an audit that finds your problem and one that structurally cannot.

Most shallow tools cluster around the same visible items: a headline, a hero image, a call-to-action color. They rarely reach the friction that actually loses the sale, such as a shipping cost revealed only at the final step, a forced account-creation wall, or a form that reflows badly on a mid-size phone. This is a common complaint in r/ecommerce threads asking what a thorough CRO checklist should cover: the free scanners agree the homepage looks fine while checkout quietly leaks revenue. Baymard Institute research puts average cart abandonment near 70%, and much of that is checkout friction a homepage-focused audit never inspects [Baymard Institute]. Coverage is what turns an audit from a design opinion into a diagnosis.

What categories the 248 criteria span

The criteria group into four categories that map to how a real shopper moves from landing to paid: page-level clarity, checkout flow, trust signals, and mobile experience. Every one of the 248+ items belongs to one of these, and each is scored per page type so nothing is assumed from one screen to another.

Page-level clarity covers headlines, imagery, and product information. Checkout flow covers field count, payment options, and guest checkout. Trust signals cover reviews, guarantees, and security badges. Mobile experience covers tap targets, mobile load speed, and form usability on small screens, checked as its own category rather than inferred from desktop. The table below shows how the criteria distribute across the five page types that carry a purchase decision, with a concrete example and the item most often missed by shallow audits.

Source: Omniconvert CROBenchmark analysis (248+ criteria across 5 page types, 2026)

Page type	Criteria checked	Example criterion	Most-missed item
Homepage	~45	Above-fold value proposition is legible in 5 seconds	Primary navigation hides key categories
Product listing (PLP)	~40	Filtering and sorting present and usable	Product cards lack price or rating at a glance
Product detail (PDP)	~55	Trust signals and reviews near the add-to-cart	Return and shipping policy not visible pre-cart
Cart	~40	Total cost, including shipping, shown before checkout	No abandonment or recovery trigger
Checkout	~68	Guest checkout offered without forced signup	Shipping cost disclosed only at the final step

Read the counts as emphasis, not arithmetic: checkout and PDP carry the most criteria because they carry the most revenue risk. A tool that gives every page the same handful of checks is telling you it does not know where money is actually lost.

How the 248 criteria were developed

The criteria set reflects 13 years of Omniconvert CRO research, refined through experiments run across thousands of eCommerce stores and 15+ industries, not an off-the-shelf generic checklist. That experience is separate from the CROBenchmark tool itself, which is a newer product that packages this accumulated method into an automated scan.

The distinction matters for how you should trust the output. Each criterion earned its place because a controlled test, or a repeated pattern across the dataset, showed it moves conversion. The set is refined rather than static, updated as new friction patterns emerge, for example the rise of mobile wallet expectations or AI-assisted product discovery. Established usability research supports the same direction: Nielsen Norman Group has long documented that unexpected costs and forced registration are among the strongest drivers of checkout abandonment [Nielsen Norman Group]. CROBenchmark encodes findings like these as checkable criteria so the same rigor is applied to every store automatically. You can read more about the underlying experimentation method behind these criteria on Omniconvert.

Why most audits miss half the criteria

Shallow audits miss criteria for a structural reason, not a lazy one: an unweighted list has no way to know which of its items matters, so tool builders keep the list short and visible. The result is an audit that inspects what is easy to see and skips what is hard to reach.

Three gaps recur. First, page coverage: many tools score the homepage and stop, leaving PDP, cart, and checkout, where most revenue is lost, unexamined. Second, no weighting: a flat checklist treats a missing favicon and a broken guest checkout as equal, so you cannot tell a cosmetic note from a revenue leak. Third, no mobile separation: assuming mobile mirrors desktop hides tap-target and form-reflow failures on the devices that now carry the majority of eCommerce traffic. CROBenchmark closes all three by scoring every page type, weighting each criterion by observed impact, and treating mobile as its own category. The point is not a bigger number for its own sake; it is that the missing half is where the fixable revenue usually sits.

The four criteria categories (the framework)

Reduced to a working framework, every audit criterion answers one of four questions, and a complete audit has to answer all four rather than over-index on the one it happens to check well.

1. Page-level clarity: can a shopper instantly understand what this is, what it costs, and why to buy it?
2. Checkout flow: can they pay with the fewest possible fields, steps, and surprises?
3. Trust signals: is there enough proof, guarantee, and security to remove hesitation at the decision point?
4. Mobile experience: does every one of the above hold up on a small screen, as its own scored category?

Use the four categories as a self-diagnosis before you run anything. If you cannot confidently answer all four for your PDP and your checkout, an audit will almost certainly find weighted criteria you are failing, and it will tell you which to fix first.

Example criteria a shallow audit never checks

The gap between a 30-item scan and a 248+ criteria audit is easiest to see in the specific, checkable items that only depth surfaces, the ones a store owner rarely notices from the inside because they see their own site every day.

On the PDP, a shallow tool confirms there is an image and a price; a deep audit checks whether the return policy and delivery estimate are visible before the shopper reaches the cart, whether reviews sit within the buying decision rather than three scrolls below it, and whether the add-to-cart stays reachable on a long mobile page. In the cart, it checks whether the full total, including shipping and tax, appears before the shopper commits to checkout, since a late cost reveal is one of the most consistent abandonment triggers in the dataset. At checkout, it separates required fields from optional ones, confirms that guest checkout exists and is not buried under a signup prompt, and verifies that error states are clear enough to recover from on a phone. None of these is exotic, and that is the point: they are ordinary, high-impact criteria that a narrow checklist has no slot for, so it reports a clean bill of health while the leak stays open. Weighting is what makes this actionable, because it tells you that a buried guest-checkout option outranks a cosmetic spacing note by an order of magnitude.

Limitations of a criteria-based audit

A criteria set is a rigorous starting point, not a verdict, and three honest limitations are worth stating before you act on any score.

First, criteria detect the presence of a best practice, not the size of its impact on your specific traffic; a live A/B test still confirms how much a fix is worth to you. Second, the set is point-in-time and evolving, so a score from today reflects both your site and the current criteria version, and a checkout change next month can reopen a criterion it cleared. Third, automated scoring reads structure well but cannot fully judge nuanced brand voice or a novel layout, which is where the weighting and the ranked report matter more than any single pass or fail. Treat the 248+ criteria as a prioritized map of where to look, then let testing size the opportunity.

Frequently asked questions

How many criteria does CROBenchmark check?

CROBenchmark evaluates stores against 248+ documented audit criteria spanning page-level, checkout, trust, and mobile experience factors.

What industries does CROBenchmark cover?

CROBenchmark benchmark data spans 15+ industries across 8 eCommerce platforms and 65 countries.

Are all 248 criteria weighted equally?

No. Criteria are weighted by their observed impact on conversion, and the audit report ranks findings by expected impact rather than listing every item with equal priority.

How is this criteria set different from a generic CRO checklist you would find online?

A generic checklist is typically a static list with no weighting or industry context. The CROBenchmark criteria set is derived from 13 years of Omniconvert CRO experiments and weighted by real observed impact on conversion.

Does CROBenchmark check mobile experience separately from desktop?

Yes, mobile-specific criteria (tap targets, mobile load speed, mobile form usability) are checked as a distinct category, not assumed to mirror desktop findings.