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:




