Overview
The Mobile CRO audit reviews your site the way a visitor on a phone experiences it and reports what stops those visitors understanding the offer, trusting the business, finding their way around, and taking the action you want: a call, a booking, an inquiry, a purchase.
It's a conversion audit. Rankings bring visitors; this audit is about what happens to the visitors who arrive.
When to use this
Run it when the site gets traffic that doesn't convert and most of that traffic is mobile, which for local and consumer businesses is the usual case. If your problem is getting traffic at all, run the Technical SEO audit first.
How it works
- It crawls. It reads your homepage plus up to 10 more pages by default, or 25 or 50 if you choose. Service and other commercial pages come ahead of blog and archive pages, one page per template. Each page goes through about 15 measured checks.
- It measures on a phone. It renders your homepage and one other template at 390 by 844 pixels and measures tap-target sizes, font sizes, contrast and horizontal overflow. Core Web Vitals come from Google PageSpeed Insights, using real-user data when Google has it.
- It screenshots your key pages. Up to 8 pages (service or product, contact or booking, pricing, location, a blog post where they exist) are captured in up to 12 screenshots at phone widths from 320 to 414 pixels, with the mobile menu open.
- An AI analyst reads the screenshots against the measurements and writes the report. Every finding has to point at a screenshot or a measured check; a claim with no evidence behind it is dropped.
If the site refuses the crawler, the report is built from public data instead (PageSpeed Insights and the Chrome UX Report) and lists the checks it could not do.
Steps
To run a Mobile CRO audit:
- Open your website, then Deep Audits under Site Audit, and pick the Mobile CRO tab.
- Under Pages to read, choose 10 pages, 25 pages or 50 pages. The run button shows the price of your choice.
- Select Run Mobile CRO Audit. A run takes up to 8 minutes.
- The report saves to the tab when it finishes. View full report (PDF) opens the PDF.
From Tools, the audit also takes an optional business name, industry, primary goal and audience, which decide the action it treats as the primary one.
Understand the results
The score is out of 100: the average mark of eight areas (Above-the-Fold UX, Navigation, CTA Visibility, Forms, Trust Signals, Mobile Readability, Touch UX, Performance), each out of 10. A High issue caps its area at 6, and Performance is scored only from a measurement.
Issues are rated Critical, High, Medium or Low by their effect on the conversion path. Confirmed issues count; possible problems it could not confirm are listed under Needs verification and never count toward the score.
In the app, Top issues, Issues by category and Pages inspected sit above Audit findings. Open a finding for the Recommended fix, For your developer or designer, Why it matters and What we measured.
The PDF has an Executive Summary, a Mobile Experience Scorecard, a Page-by-Page Review with the problem marked on each screenshot, the Confirmed Issues, Needs Verification, an Action Plan table, and a closing section on how the audit was done and what it could not verify.
Sample output
This is an example on a made-up website, not a real report:
Mobile CRO score 58/100 · 1 Critical, 3 High, 4 Medium
Touch UX 5/10 · CTA Visibility 4/10 · Forms 6/10
Critical · Booking button sits below three screens of text on /services/
Where: Service page, hero (screenshot S03)
Why it matters: a phone visitor scrolls past 2,100px before the first way
to book.
Recommended fix: move "Book a visit" into the hero, under the H1.
For your developer or designer: add a sticky bottom bar with the same
button below 768px.
New since the previous audit
What to do with the results
To work through a Mobile CRO audit:
- Open Top issues and start with the Critical and High ones.
- Open each finding and apply the Recommended fix, or hand For your developer or designer and the marked screenshot to whoever builds the site.
- For a Needs verification item, do its What to check on a phone step before building anything.
- When the changes are live, select Re-run audit.
- Compare: Compared to previous audit shows the change in points, Score trend shows the runs over time, and each finding says whether it is New since the previous audit or was seen before. View history opens every saved run.
Limits and usage
- 10 pages cost 5 credits, 25 pages 12 credits and 50 pages 23 credits. A run that fails is not charged. See plans and credits.
- A run stops at 8 minutes. On a slow site the crawl stops early, and the run says how many pages it reached.
- The AI analyst sees up to 12 screenshots and 60 per-page findings, whatever the number of pages crawled; the scorecard reads every crawled page.
- It reviews the mobile rendering. It doesn't read your analytics or measure your conversion rate.
Troubleshooting
No screenshots could be captured
The site blocked the browser or timed out, so the run stops rather than describing what the site "probably" looks like. Retry, or check whether the site refuses automated visitors.
A finding references an element you can't find
Open the page in your browser's device mode at 375 pixels wide. The screenshot in the report shows where it is, often in the mobile menu or footer.