Know exactly what state your Magento store is in
Magento stores tend to degrade in the same places: a patch level nobody has checked, extensions that override each other, and a full page cache that is quietly disabled on half the catalog. None of it shows until peak traffic or the next security bulletin.
What you get
A written health check covering security patch level, extension conflicts and code overrides, full page cache and performance, indexer and cron health, and an upgrade path with effort estimated per step. Delivered before any build work is quoted.
- Magento, Shopify, BigCommerce and Salesforce Commerce Cloud in-house
- Founder-led. The person reviewing your store is the person who would fix it
- One business day response, guaranteed
What you actually receive
A written report, not a call summary. This is the structure every health check follows, with example values in place of your data.
| Checked | Example finding | Rating |
|---|---|---|
| Version and security patch level | 3 security patches behindCritical | Critical |
| Third-party extensions installed | 46, of which 9 unusedMedium | Medium |
| Conflicting class rewrites | 2, both on checkoutHigh | High |
| Full page cache hit rate | 38%, uncacheable block in layoutCritical | Critical |
| Indexers running on schedule | 7 of 9Medium | Medium |
| Cron last successful run | within the hourIncluded | Included |
| Upgrade path to current release | 3 steps, estimated per stepIncluded | Included |
plus the full extension inventory and the step-by-step upgrade plan
Example values shown. Your report contains findings from your own environment.
What we look at
Security patch level and exposure
The exact Magento or Adobe Commerce version, which security patches are missing, and whether any installed extension appears in a published advisory. Unpatched stores are the ones card-skimming scripts target, so this comes first.
Extensions, overrides and conflicts
Every third-party module, what it rewrites, and where two modules override the same class or add plugins to the same method. This is where most "random" checkout and indexing bugs actually come from.
Performance where customers feel it
Full page cache hit rate, Varnish configuration, and server response time on category and product pages. One block marked uncacheable in a shared layout switches full page cache off for every page that uses that layout.
Indexers, cron and the upgrade path
Whether indexers run on schedule, whether cron is actually executing, and what it takes to reach the current supported release, broken into steps with the effort for each.
Common questions
Do you need admin or server access for a Magento health check?
Some of it can start without any access. The Magento version, response headers, cache behavior and page speed on your real templates are all visible from outside, so we begin there while access is arranged. The deeper checks need three things: a restricted admin user so we can read configuration and indexer status, read access to the code repository so we can inventory extensions and overrides, and either a staging environment or read-only server access for cron, logs and Varnish configuration. We never need production write access for the health check, and we do not need customer data. If your store is hosted by an agency or a managed host that controls the server, a short list of commands for them to run works just as well. The report states which checks were done with which level of access, so nothing is presented as verified when it was inferred.
Should we upgrade Magento or move to another platform?
It depends on what your store actually does, and the health check is designed to answer that with evidence rather than preference. If your business relies on things Magento and Adobe Commerce do well, such as complex B2B pricing, customer-specific catalogs, multiple store views, or deep ERP integration, staying and upgrading is usually cheaper than rebuilding those features elsewhere. If your store is a standard catalog and checkout, and most of your development budget goes on keeping Magento patched and running, a hosted platform like Shopify or BigCommerce can remove that cost entirely. We build on all of these platforms, so we have no reason to push you toward one. The report includes the upgrade path either way, so you can compare the cost of staying against a migration estimate on equal terms.
How long does the health check take, and what happens after it?
Expect one to two weeks from the point access is in place. Stores with a long extension list, several store views or a heavily customized checkout sit at the longer end. You receive the written report and a walkthrough call where we go through the findings in order of risk, and explain what each one means for the business rather than only for the codebase. After that the report is yours. You can hand it to your in-house team, give it to another agency, or ask us to quote for the fixes. Many findings are small configuration or patching tasks that any competent Magento developer can do from the report alone. The larger items, such as untangling conflicting extensions or planning a version upgrade, come with effort estimates so you can budget before committing to anything.
Want the full service details?
This page covers one specific engagement. The service page has the complete scope, process and technology list.