Version & patch status
Which Magento or Adobe Commerce version you're on, whether it's still supported, and which security patches are missing. Read from what the store exposes publicly — we'll say so if we can't tell from the outside.
Magento Store Health Check
Most stores we look at have two or three things quietly costing them money — an unapplied security patch, a cache that isn't doing its job, a checkout step that takes four seconds. Send us the URL and we'll take a look, free, and tell you what we find.
Magento & Adobe Commerce engineering from Massachusetts, serving e-commerce businesses across the United States.
How it works
There's no automated tool behind this. Some of what we do uses public measurements — Lighthouse and Core Web Vitals field data for speed, the version fingerprint a Magento store gives away in its own markup, response headers that show whether the full-page cache is working. The rest is a Magento engineer opening the store, walking the catalog and the checkout, and noticing what's wrong.
That's slower than a scanner and considerably more useful. A scanner tells you a page scored 41. It doesn't tell you the score is 41 because a third-party review widget is loading synchronously in the head, which is a twenty-minute fix.
We don't need admin access or server credentials for the initial review, and we won't ask for them before we've spoken.
The checklist
Which Magento or Adobe Commerce version you're on, whether it's still supported, and which security patches are missing. Read from what the store exposes publicly — we'll say so if we can't tell from the outside.
Whether your PHP version is supported by your Magento version and still getting security fixes, and what an upgrade to a current one would involve.
Page speed on the homepage, a category page, and a product page, measured rather than guessed. Where Chrome has field data for your store, we use that too — it's what Google actually ranks on.
Whether the full-page cache and Varnish are hitting, whether Redis is configured the way Magento expects, and which pages are punching holes in the cache without needing to.
Indexer mode and whether anything looks stuck, plus OpenSearch or Elasticsearch configuration where we can see it. Some of this needs a look inside — we'll flag what we could only check with access.
We go through your checkout as a customer would, on a phone as well as a desktop, and note what's slow, broken, or asking for more than it needs to.
Missing patches, exposed admin paths, headers that should be set and aren't, and the front-end skimmer signatures that are visible from outside.
Indexability, canonical tags, structured data, sitemap and robots.txt, and the layered-navigation URL sprawl that Magento produces by default and quietly buries your category pages under.
Time to first byte, where the store is served from, CDN configuration, and whether the stack in front of Magento is helping or in the way.
Honest limits
Performance, caching behavior, checkout, security headers, SEO fundamentals and the version fingerprint are all visible from the public site, so those are the parts we can be confident about.
Indexer state, cron health, database size, log noise, third-party extension conflicts and anything inside the admin need access we don't have yet. We'll tell you which of our findings are firm and which are worth checking properly, instead of presenting a guess as a diagnosis.
Request a health check
The first four fields are all we need to get started. The rest help us aim the review, and you can skip any of them.
FAQ
Yes. We review your store and send you what we found. There is no charge and no obligation to hire us afterwards — if the answer is that your store is in good shape, that is what we will tell you.
The store URL is enough to start. Your Magento version, order volume, and hosting help us aim the review, but we can work them out from the outside if you would rather not share them yet. We do not need admin access, and we will not ask for it before we have spoken.
No. Some of it uses public tools — page speed measurements, Core Web Vitals field data, the version fingerprint a Magento store gives away in its markup. The rest is a Magento engineer reading the store and telling you what stands out. That is why it takes a couple of days rather than thirty seconds.
Not for the initial review. Everything in it comes from what the store shows publicly. Anything that needs a look inside — indexer state, cron health, database size, log noise — we would scope separately once you have decided you want it.
It goes to Emyrix and nowhere else. We use it to review your store and to reply to you. We do not sell it, share it, or add you to a mailing list. See our privacy page for the detail.
Both, and Mage-OS. The check is the same either way — the differences show up in the recommendations, not in what we look at.
Related