In short
- A Shopify CRO audit should combine analytics data, session recordings and a hands-on walkthrough of the store.
- Fix tracking first, because every later finding depends on accurate conversion data.
- Audit on a mid-range Android phone on mobile data to see the store the way most Indian shoppers do.
- Score failed checks on impact, confidence and effort, then work on the top five before anything else.
- Ship clear fixes directly and save A/B tests for genuinely uncertain changes with enough traffic.
A Shopify CRO audit is a structured review of every step between a visitor landing on your store and completing an order, backed by your own analytics data. Done properly, it tells you exactly where shoppers drop off, why, and which fixes are worth doing first. Below are the 40 checks we run on every store, grouped by funnel stage, plus how to turn the findings into a prioritised plan.
What a Shopify CRO audit is (and is not)
A CRO audit is not a list of opinions about colours and fonts. It combines three inputs: quantitative data (Shopify Analytics, GA4, your ad platforms), qualitative evidence (session recordings, heatmaps, customer support tickets, reviews) and a heuristic walkthrough of the store on the devices your customers use.
The output should be a ranked backlog of problems, each tied to a funnel step and a metric. "The product page feels cluttered" is not a finding. "Only a small share of mobile product page visitors scroll past the image gallery, so the delivery and returns information is never seen" is a finding you can act on and measure.
Before you start: get the baseline numbers
Pull the last 60 to 90 days of data, split by device and traffic source. You need, at minimum:
- Sessions, conversion rate and average order value (AOV), split by mobile and desktop.
- The funnel: sessions with add to cart, sessions that reached checkout, sessions that converted. Shopify's conversion report shows this.
- Top landing pages by sessions and their conversion rate.
- For Indian stores, the COD share of orders and your return-to-origin (RTO) rate, because a "conversion" that comes back undelivered is not revenue.
With that baseline, you can see which stage leaks most. A store with a healthy add-to-cart rate but weak checkout completion needs a different audit emphasis from one where nobody adds to cart at all.
The 40 checks, stage by stage
Data and tracking (checks 1 to 5)
| # | Check | What good looks like |
|---|---|---|
| 1 | Shopify orders vs GA4 purchases | GA4 purchase count is within a reasonable gap of Shopify orders for the same period; big gaps are investigated. |
| 2 | Checkout and thank-you tracking | Pixels run through Shopify's customer events (app or custom pixels), not old Additional Scripts, which Shopify has retired on the new Thank you page. |
| 3 | Funnel events | view_item, add_to_cart, begin_checkout and purchase all fire once, with value and currency. |
| 4 | Duplicate pixels | Each ad platform pixel is installed once, not by both an app and hard-coded theme code. |
| 5 | Consent and UTM hygiene | Campaign links are tagged consistently so you can compare landing pages by source. |
Shopify confirms that 26 August 2026 was the deadline for non-Plus stores to move to the new Thank you and Order status pages, and that the Additional Scripts section has been view-only since August 2025 (Shopify Help Center). If your purchase tracking lived there, check it first.
Speed and technical health (checks 6 to 10)
| # | Check | What good looks like |
|---|---|---|
| 6 | Largest Contentful Paint (LCP) | 2.5 seconds or less at the 75th percentile of real mobile visits. |
| 7 | Interaction to Next Paint (INP) | 200 milliseconds or less, so taps on variant pickers and Add to cart feel instant. |
| 8 | Cumulative Layout Shift (CLS) | 0.1 or less; no buttons jumping when banners or reviews load. |
| 9 | App and script load | Every third-party script maps to an app you still use and value. |
| 10 | Broken pages and links | No 404s from ads, emails or navigation; sold-out products don't dead-end. |
The thresholds in checks 6 to 8 are Google's published Core Web Vitals targets (web.dev). Shopify's own web performance report shows your store's real-user figures in the admin (Shopify Help Center). For more depth, see our guide to Core Web Vitals in 2026.
Homepage and navigation (checks 11 to 15)
| # | Check | What good looks like |
|---|---|---|
| 11 | First-screen clarity | A new visitor can tell what you sell and why it is different within the first mobile screen. |
| 12 | Menu structure | Navigation mirrors how customers shop (by concern, occasion or category), not your internal SKU logic. |
| 13 | Search | Search is visible on mobile, handles misspellings and synonyms, and never returns an empty page without suggestions. |
| 14 | Announcement bar | One clear message (offer, shipping threshold or COD availability), not a rotating carousel. |
| 15 | Pop-ups | Email or WhatsApp capture waits for engagement and is easy to close on mobile. |
Collection pages (checks 16 to 20)
| # | Check | What good looks like |
|---|---|---|
| 16 | Filters | Relevant filters per collection (size, price, concern, colour), with a sticky filter button on mobile. |
| 17 | Default sort | Best sellers or a merchandised order first, sold-out items pushed down. |
| 18 | Product cards | Price, discount, rating and key variant info visible without opening the product. |
| 19 | Image consistency | Same crop and background across a collection so shoppers can compare. |
| 20 | Pagination | A "load more" or paginated grid that keeps scroll position when shoppers go back. |
Product pages (checks 21 to 28)
| # | Check | What good looks like |
|---|---|---|
| 21 | Above-the-fold essentials | Title, price, rating, variant picker and Add to cart visible on the first mobile screen or via a sticky bar. |
| 22 | Price presentation | MRP, selling price and saving shown clearly, with no surprise charges later. |
| 23 | Delivery promise | Pincode check or estimated delivery date near the button. |
| 24 | Payment reassurance | COD, UPI and EMI availability stated near the price, not only at checkout. |
| 25 | Images and video | Scale, texture and in-use shots; video for products where fit or feel matters. |
| 26 | Benefit-led copy | Three to five scannable benefits before long descriptions and ingredient lists. |
| 27 | Reviews | Photo reviews near the top, with the ability to filter by concern or size. |
| 28 | Returns and sizing | Return window and size guide one tap away from the variant picker. |
Cart (checks 29 to 32)
| # | Check | What good looks like |
|---|---|---|
| 29 | Cart format | Drawer or page chosen deliberately for your AOV and basket size. |
| 30 | Shipping threshold progress | A progress message that updates live as items are added. |
| 31 | Relevant add-ons | At most one or two complementary products, not a wall of upsells. |
| 32 | Discount field | Coupon handling doesn't send shoppers off-site hunting for codes. |
Checkout (checks 33 to 36)
| # | Check | What good looks like |
|---|---|---|
| 33 | Form friction | Phone-first login, address autocomplete, pincode-based city and state fill. |
| 34 | Payment options | UPI, cards, net banking, wallets and COD (if you offer it) all tested on mobile. |
| 35 | Cost transparency | Shipping and COD fees shown before the final step. |
| 36 | Test orders | A real test order on each payment method completes and triggers confirmation messages. |
Post-purchase and retention (checks 37 to 40)
| # | Check | What good looks like |
|---|---|---|
| 37 | Thank-you page | Clear next steps, order tracking and, where relevant, one relevant offer. |
| 38 | Confirmation messages | Email and WhatsApp confirmation arrive quickly with accurate delivery estimates. |
| 39 | COD confirmation | COD orders are confirmed (or nudged to prepaid) before dispatch to reduce RTO. |
| 40 | Abandonment flows | Browse, cart and checkout abandonment flows are live and segmented. |
How to run the audit in practice
- Walk the store as a customer. Use a mid-range Android phone on mobile data, not your office Wi-Fi and a flagship iPhone. Land from an Instagram ad link, then from a Google search, and try to buy.
- Watch 30 to 50 session recordings for your top landing pages. Note rage taps, repeated scrolling back to images and exits on specific sections.
- Read support tickets and reviews. Questions that repeat ("Is COD available?", "When will it arrive?") are content missing from your product page.
- Score every check as pass, partial or fail, and attach a screenshot and the metric it affects.
- Place test orders on each payment method and pincode type (metro and non-metro).
Turning 40 findings into a plan
Most stores fail somewhere between 10 and 20 checks. Fixing them all at once makes it impossible to know what worked. Score each failed check from 1 to 5 on three factors:
- Impact: how many sessions pass through that step, and how badly it is leaking.
- Confidence: how strong the evidence is (data plus recordings beats a hunch).
- Effort: developer and design time, scored so that easier work scores higher.
Multiply the three and sort. For example, a missing delivery date on product pages that receive most of your paid traffic might score 5 x 4 x 4 = 80, while redesigning the homepage hero scores 2 x 2 x 2 = 8. The first goes into this sprint; the second waits.
Ship high-confidence fixes (broken tracking, slow scripts, missing information) directly. Reserve A/B tests for changes where you genuinely don't know the answer and have enough traffic to detect a difference.
Get a second pair of eyes on your store
You can run this checklist yourself in a focused day or two. If you'd rather have a team that audits Shopify stores every week do it, with the findings scored and turned into a build plan, see our Shopify CRO services. For quick mobile wins in the meantime, our list of mobile CRO mistakes is a good place to start.
Frequently asked questions
A focused audit of a typical D2C store takes one to three working days. That covers pulling 60 to 90 days of data, watching session recordings, a device walkthrough, test orders and scoring every check. Larger catalogues, multiple markets or custom checkouts take longer, mainly because there are more templates and payment flows to test.
Yes. The checklist in this article is designed so a founder or ecommerce manager can run it. The hard parts are being honest about what you see and having enough data to back findings. An outside team helps when you are too close to the store, or when fixes need theme development you can't do in-house.
At minimum you need Shopify Analytics, GA4 with purchase tracking working, a session recording and heatmap tool such as Microsoft Clarity or Hotjar, and PageSpeed Insights or Shopify's web performance report. Access to support tickets and product reviews is just as valuable, because they reveal questions your pages are not answering.
A full audit once or twice a year works for most stores, with a lighter check after any theme change, new app install or major campaign. Tracking and speed checks are worth repeating monthly, because apps and scripts accumulate quietly and can break purchase tracking or slow the store without anyone noticing.
No. Broken tracking, slow scripts, missing delivery information or a checkout bug should simply be fixed. Testing makes sense for changes where the outcome is genuinely uncertain, such as a new product page layout, and only when you have enough traffic to detect a meaningful difference within a few weeks.
