Up to 70% off

    9d 17h 46m 23s

    Get it
    E-commerce
    Adobe Commerce Audit: Speed, UX and Checkout Checklist
    EyeCaptain

    Adobe Commerce Audit: Speed, UX and Checkout Checklist

    A practical Adobe Commerce and Magento audit checklist: version, extensions, caching, speed, search, product pages, checkout and GA4 tracking.

    Dimitris Andreadakis

    6 min read
    44 views
    adobe commerce auditmagento auditmagento conversion optimizationmagento checkout optimizationecommerce cro audit

    An Adobe Commerce store (still called Magento by most of the people who run one) can lose sales in places a general website audit never looks: an outdated release, a full page cache that stopped working after an extension update, indexers that lock the database at peak hours, or a checkout that was customised years ago and never revisited. This checklist walks through an Adobe Commerce audit in the order that usually pays off, starting with the platform and finishing with the pages where buyers decide.

    It works for Adobe Commerce and Magento Open Source 2.4 stores alike. You do not need to be a developer to run most of it, but you will want someone with admin and server access for the first two sections.

    1. Platform health: version, extensions and errors

    Start with the things that quietly affect everything else.

    Check your release against the support calendar

    Find your exact version in the admin footer or with bin/magento --version, then compare it with the Adobe Commerce lifecycle policy. A release that is out of support stops receiving security patches, and an unpatched store is a risk to payment data and to your reputation. If an upgrade is due, plan it before any conversion work, because a version jump can change templates, checkout behaviour and extension compatibility.

    List every third-party extension

    Most Magento stores collect extensions over the years. For each one, note what it does, whether it loads code on the storefront, and whether anyone still needs it. Extensions that add JavaScript to every page, rewrite core checkout classes or add observers to cart events are the usual suspects when a store feels slow or a checkout breaks after an update. Disable what nobody uses on a staging copy and measure the difference.

    Read the logs

    Open var/log/exception.log and system.log and look for repeating errors, especially around quote, payment and shipping methods. A checkout error that only hits one payment method or one country will not show up in your own test orders, but it shows up in the logs.

    2. Caching, indexing and server configuration

    Adobe's own guidance is clear on the big items. Its performance configuration best practices say to activate all caches when the store goes live, "highly recommend using Varnish" as the production page cache, and recommend setting indexers to "Update on Schedule" for performance. Check each of these:

    • Cache Management: every cache type should show as enabled. An invalidated cache that nobody refreshed means pages are rebuilt for each visitor.
    • Full page cache: confirm Varnish (or Fastly on cloud) is actually serving pages. Request a category page twice and check the response headers for a cache hit. A single extension that marks a common block as uncacheable can disable full page caching for the whole page.
    • Indexers: run bin/magento indexer:status. Indexers on "Update on Save" can slow the admin and the storefront during busy periods, and any index marked "Reindex required" means customers may see stale prices or stock.
    • Cron: scheduled indexing, emails and cache cleaning all depend on cron. Check that it runs and that cron_schedule is not full of missed or errored jobs.
    • Deploy mode: the live store should run in production mode, with static content deployed, not in developer or default mode.

    3. Front-end speed on real templates

    Once the server side is sound, measure the pages customers actually use: the home page, two or three category pages, a simple product, a configurable product with options, the cart and the checkout. Test on mobile first, because that is where heavy Luma-based themes struggle most.

    • Look at Largest Contentful Paint on product pages, where the main image is usually the largest element. Our guide to improving LCP on product pages covers image sizing, preloading and lazy loading in detail.
    • Count the JavaScript files and their total size. RequireJS stores often load hundreds of small files. Adobe's own documentation notes that its built-in bundling is not optimal and suggests third-party tools or HTTP/2 instead.
    • Check interaction delay on swatches, add to cart and the mini cart. Slow responses here feel like a broken button, and shoppers tap again or leave.
    • Watch for layout shift when price blocks, reviews widgets or promo banners load late.

    4. Search, navigation and category pages

    Many Adobe Commerce stores have large catalogues, so how people find products matters as much as the product page itself.

    • Search for your ten best-selling products using the words customers use, including misspellings and plural forms. Note every search that returns nothing or the wrong product first.
    • Check layered navigation: are the filters the ones shoppers care about (size, price, compatibility), or the attributes that happened to be set as filterable years ago? Filters with one option, or options that return zero products, add noise.
    • Review default sorting. "Position" sorting that nobody maintains often puts out-of-stock or low-margin items at the top.

    5. Product pages

    Configurable products are where Magento stores most often confuse buyers. Check that:

    EyeCaptainEyeCaptain
    97%
    Conversions Booster

    Your visitors leave without converting

    Most websites lose 97% of their traffic without a single conversion. Our AI scans 200+ CRO elements to find exactly where visitors drop off.

    Form friction detected

    • The price updates clearly when an option is chosen, and the selected option is obvious.
    • Out-of-stock options are marked before the buyer selects them, not after they click add to cart.
    • Delivery time, shipping cost and the returns policy are visible near the buy button, not hidden in a tab.
    • Reviews, ratings and trust details sit where the buyer is deciding, not at the bottom of a long page.
    • Error messages (missing size, quantity limits) appear next to the field that caused them.

    Our checklist of product page UX audit mistakes goes through these issues one by one.

    6. Cart and checkout

    This is where most of the money is. Baymard Institute puts the average documented cart abandonment rate at 70.22%, and estimates that the average large ecommerce site could gain a 35.26% increase in conversion rate through better checkout design alone. In the same research, 19% of shoppers who abandoned said they did not trust the site with their card details, 18% left because the site wanted them to create an account, and 17% because the checkout was too long or complicated.

    On an Adobe Commerce checkout, check these points:

    1. Guest checkout: confirm it is enabled for every product type you sell. Some stores disable it for downloadable or configurable items without anyone noticing. See our comparison of guest checkout and forced registration.
    2. Form fields: the default checkout asks for more than most stores need. Remove or make optional the fields you never use, such as company, fax or a second street line.
    3. Shipping costs: show the shipping estimate in the cart, before the buyer enters an address, so the final total is not a surprise.
    4. Payment methods: test every method on mobile, including wallets, with a real card on a staging or live test order. Check the order confirmation page and email too.
    5. Errors: enter a wrong postcode, an expired card and an invalid coupon. Each error should explain what to fix, in plain words, next to the field.
    6. Coupon field: a large, empty coupon box sends some shoppers off to search for codes. Consider a collapsed link instead.

    For the psychology behind these choices, read our piece on checkout psychology, payment and shipping options.

    7. Tracking you can trust

    An audit only helps if you can measure the fixes. Check that GA4 receives the standard ecommerce events (view_item, add_to_cart, begin_checkout, add_shipping_info, add_payment_info, purchase) with correct values and currency, and that purchase is not fired twice when a customer reloads the success page. Compare GA4 purchases with orders in the Magento admin for the same week; a gap of more than a few percent means the data needs fixing before you trust any funnel report.

    Once the events are clean, a funnel report shows exactly which checkout step loses the most people. Our guide to finding conversion leaks with GA4 funnel exploration explains how to build one.

    How to prioritise what you find

    A full Adobe Commerce audit usually produces a long list. Sort it into three groups:

    GroupExamplesWhen to act
    Broken or riskyUnsupported version, checkout errors in logs, caches disabled, purchase events missingNow, before any testing
    Friction on money pagesHidden shipping costs, forced registration, slow product images, confusing optionsNext, ranked by traffic to the page
    Improvements to testLayout changes, copy, trust badges, cross-sellsThrough A/B tests once tracking is reliable

    Fix the first group without testing; nobody needs an experiment to prove that a broken checkout loses orders. Test the third group, because the result depends on your customers.

    If you want a quick outside view of one key page before you start, run a free CRO audit on your product or category page and use the findings as a starting list for the checks above.

    Enjoyed this article?

    One short email a week with practical CRO and UX tips

    No spam. Unsubscribe anytime.

    Find what stops your visitors from converting

    EyeCaptain is an AI-powered CRO & UX audit tool that automatically scans your pages, identifies UX issues, and gives you actionable optimization suggestions to increase conversions. Try it for free, no card, no commitment.

    Free Website Audit
    Share this article
    LinkedIn X

    About the author

    Founder of EyeCaptain. Writes about conversion rate optimization, UX analysis and the neuromarketing behind pages that actually sell.

    More articles by Dimitris Andreadakis