Ecommerce Audit Template Checklist
A four-pillar ecommerce audit template covering UX, site speed and mobile, analytics hygiene, and CRO opportunities — the same structure agencies use during onboarding and quarterly reviews.
Ecommerce Audit Template
A structured checklist that reviews a store's UX, technical performance, analytics setup, and CRO opportunities in one pass.
An ecommerce audit template is a repeatable checklist that walks a store top-to-bottom across four pillars: user experience, technical performance (page speed and mobile), analytics and tracking hygiene, and conversion-rate optimisation opportunities. Agencies use it during client onboarding to surface quick wins; in-house teams run it quarterly as a health check.
The output is a prioritised list of issues and experiment ideas — not a report card. A good template forces you to look at the parts of the store you usually skip (checkout error states, GA4 event coverage, product-page schema) and produces a backlog you can actually act on.
Most store owners only audit when something breaks — a sudden drop in conversion rate, a Core Web Vitals warning in Search Console, or a campaign that underperformed. By then you're reacting. A template flips that: you run the same checklist every quarter, and trends show up before they become revenue problems.
The version below is the four-pillar structure agencies use during the first two weeks of a new engagement. It works for a Shopify apparel store doing €2M a year, a WooCommerce beauty brand on Klaviyo, or a Magento electronics catalogue with 5,000 SKUs — the categories don't change, only the depth you go to in each one.
Scope the audit before you start
A full four-pillar audit on a mid-size store takes 15-25 hours of focused work. If you try to fix issues as you find them, you'll spend three weeks and finish nothing. Audit first, prioritise second, fix third — and timebox each pillar to a half-day.
The four audit pillars
Pillar 1 — UX and merchandising. Walk the funnel as a first-time buyer on mobile: home → category → PDP → cart → checkout. Note friction at every step. Check that PDPs show price, stock status, shipping cost, and returns policy above the fold. Audit category filters (do they actually narrow inventory?), search results for the top 20 queries, and cart upsells. Screenshot every broken or confusing state — you'll forget half of them by the next day.
Pillar 2 — Technical: speed and mobile. Run PageSpeed Insights on the home page, a category page, a PDP, and the cart. Record LCP, CLS, and INP for each. Flag any third-party script over 50KB (chat widgets, review apps, and old analytics tools are usually the worst offenders). Check that the site renders correctly on a real mid-range Android, not just Chrome DevTools — touch targets, font sizes, sticky add-to-cart, and checkout form behaviour all break differently on actual hardware.
Pillar 3 — Analytics hygiene. This is where most audits find the biggest surprises. Verify GA4 is tracking purchase, add_to_cart, begin_checkout, view_item, and view_item_list with correct revenue and currency. Cross-check GA4 revenue against the Shopify or WooCommerce admin for the last 30 days — if they're more than 5% apart, your reporting is lying to you. Check that consent mode is wired, that UTMs aren't being stripped on redirect, and that the server-side feed (if any) isn't double-counting.
Pillar 4 — CRO opportunity assessment. With the first three pillars done, you now have evidence. Pull funnel drop-off by step, segment by device and traffic source, and identify the two or three steps with the steepest losses relative to benchmark. For each, write a one-line hypothesis ("PDP bounce on mobile is driven by hero image weight — compress and retest LCP") and a rough effort/impact score. The output of the audit is this backlog, not the audit itself.
Ecommerce audit template FAQ
Quarterly for the full four-pillar pass, plus a lightweight monthly check on analytics hygiene and Core Web Vitals. Anything more frequent and you won't have enough new data between audits; anything less and tracking drift accumulates silently.
Plan for 15-25 hours of focused work for a mid-size store with 100-1,000 SKUs. UX and CRO each take a full day; technical and analytics take a half-day each if you know the stack. Add time if the store has heavy third-party app sprawl.
No — the audit itself is observational, not implementational. You're documenting issues, not fixing them. Developers come in after the backlog is prioritised, when you've decided which 3-5 items are worth the engineering cost.
A CRO audit is one pillar of an ecommerce audit. CRO focuses purely on conversion-rate opportunities (PDP friction, checkout drop-off, copy testing). An ecommerce audit also covers technical performance, analytics setup, and merchandising — the upstream issues that cause conversion problems in the first place.
PageSpeed Insights or Lighthouse for performance, GA4 plus your platform admin for analytics cross-checks, a session-recording tool (Hotjar, Microsoft Clarity, or Metricuno) for UX, and a spreadsheet for the backlog. You don't need an enterprise audit suite for a store under €15M revenue.
Score each finding on effort (hours to fix) and impact (estimated revenue lift or risk reduction). Anything high-impact and low-effort goes to the top — usually that's broken tracking, slow hero images, or missing trust signals on the PDP. Save full redesigns for a separate roadmap.
You can audit configuration immediately, but spotting drift needs history. If you're inheriting a GA4 property with limited retention, import the historical data into a warehouse or a tool that backfills it before you start — otherwise you'll only catch issues that started after the audit.
Yes — the four pillars are platform-agnostic. The specifics change (Shopify's checkout is mostly locked; WooCommerce gives you more control but more ways to break tracking; Magento has deeper catalogue concerns) but the questions you ask are identical.
Share the prioritised backlog with the whole team and keep the raw findings document for leadership and the people implementing fixes. A 60-page audit landing in a marketing manager's inbox tends to be read once and never opened again — the backlog is the part that drives action.
Broken or incomplete event tracking. Roughly half of the stores in this revenue band are reporting GA4 revenue that's 10%+ off the platform admin, usually because of consent mode misconfiguration, missing server-side events, or duplicate purchase fires. Everything else you measure depends on this being right.
Get an AI expert review of your site
Paste your URL — Metricuno's AI runs the same heuristic checks a senior CRO consultant would, scoring your page and prioritising the fixes that'll move conversion fastest.