
1.8 million domains checked, 28,708 Magento stores verified
Original Research
In November 2026 we checked more than 1.8 million domains and verified 28,708 live Magento and Adobe Commerce stores among them. This is what they run: which release, which storefront, how fast it is for real shoppers, and how many are on software Adobe no longer patches. And for each finding, what a store in that position can do next.
See the FindingsThe Short Version
28,708 stores18.6% on Magento 118.5% on Hyvä
Most numbers quoted about Magento come from a vendor's own customers or from a count nobody can check. This report comes from the stores themselves. We found them, confirmed each one runs Magento, and read what any browser can read: the homepage, the static files and the version the store announces.
Three things stand out. Magento 1 is far from gone: 5,328 of the stores still run it, more than six years after Adobe ended support. Add the Magento 2 stores on lines 2.0 to 2.4.3 and at least 30.5% of the sample is on software with no vendor patches coming.
Hyvä has moved from a specialist choice to a mainstream one in Europe, and much less so in the United States, where 12.2% of Magento 2 stores use it against 34.7% in the Netherlands. Across the whole sample it carries 18.5% of Magento 2 stores, and the Luma stack it replaces still carries 77.7%, so most of the move is still ahead.
And the storefront decides the speed. Hyvä stores pass Core Web Vitals at 68.7%, level with Shopify stores in the same database. Stores on the Luma stack pass at 43.5%.
Key Findings
31%
At least 30.5% of stores run Magento 1 or a Magento 2 line Adobe stopped patching in 2022 or earlier. A floor, since many stores hide their version.

69%
68.7% of Hyvä stores pass all three measures for real shoppers on phones. On the Luma stack the figure is 43.5%.

19%
18.5% of Magento 2 stores run Hyvä. Belgium leads at 41.4% and the United States stands at 12.2%.
What to Do Next
Each group in this report has a different next step. Pick the one that describes your store.
There is no upgrade path, only a move: to Magento 2, or to another platform if the store has outgrown the need for one. We plan the data, the URLs and the search rankings before anything is switched.
Plan the MigrationThese lines have had no security fixes from Adobe since 2022, and the PHP versions under them are out of support too. The jump to a current release is larger than a routine upgrade, and it is still one project.
See the Upgrade ServiceSecurity fixes still arrive, and the clock is running: these lines leave support in 2027. Answer a few questions about your store and see what an upgrade from your release involves.
Open the Upgrade CalculatorHyvä stores pass at 68.7% against 43.5% on the Luma stack. A rebuild on Hyvä replaces the front end and keeps your catalog, your orders and your back office where they are.
See Hyvä DevelopmentThe line is only the start. Adobe ships security releases inside each line several times a year, and a store that skips them is exposed on a supported version. We apply them on a schedule and test before each release.
See Security PatchingThe free Magento audit reads your store from outside, the way this scan did, and reports its speed, checkout, search visibility and security signals with the fixes ranked by impact.
Audit My Magento StoreMethodology
The scan read public pages only, one request at a time per store, under a user agent that names ZestIQ. It never touched a cart, a checkout, a customer account or an admin panel, and it sent no request built to test a vulnerability.
| Finding | How it was read | What it cannot show |
|---|---|---|
| The sample | Candidate domains came from public web crawl indexes, certificate logs and traffic rankings, more than 1.8 million in all. Each was fetched and kept only when its own pages proved it runs Magento. | This is a sample, not a census. Stores whose firewall refused the scanner are not in it, so heavily protected stores are under-counted. |
| Release line | The minor line a store announces on its version page, and the hashes of up to twelve public static files compared against every release tagged since 2.3.0. | Security releases that changed no public file look alike from outside, and an isolated patch or hotfix leaves no trace at all. No store is called patched or vulnerable. |
| Support status | Each line was set against Adobe's published lifecycle dates for Adobe Commerce, as they stood in November 2026. | Some stores on old lines apply community or third-party fixes, and some Magento 1 stores run a maintained fork. Unsupported by Adobe is all the figure says. |
| Storefront | Technical fingerprints in the page source: Hyvä's own markers, the RequireJS and Knockout stack of Luma, Breeze and PWA Studio signatures. | A headless store that hides its back end entirely may not be recognised as Magento at all. |
| Core Web Vitals | Google's Chrome UX Report for each store's origin: the 75th percentile on phones over 28 days, passing at 2.5 seconds, 200 milliseconds and 0.1. | Google publishes data only for sites with enough Chrome traffic, so small stores are missing. The comparison describes stores as they are built, not the theme alone. |
| Country | A country domain, or for .com stores the address, currency and language the store itself publishes. | A store selling into several countries is counted once, where its own pages place it. |
Keep reading



FAQ
Tell us about your store and we will come back with straight answers.
Talk to an Engineer28,708 live stores that we verified as Magento or Adobe Commerce from their own pages: 23,380 on Magento 2 and 5,328 on Magento 1. Every one was rechecked in November 2026. To find them we checked more than 1.8 million domains and set the rest aside because they run another platform, were offline, or refused the scanner.
Magento 2.4.9, released in May 2026 and supported by Adobe until May 2029. In this scan 10.8% of the Magento 2 stores with a readable release already run it. The most common line is 2.4.8 at 29.3%, followed by 2.4.7 at 23.1%.
As of November 2026, lines 2.4.7, 2.4.8 and 2.4.9 are in full support, to May 2027, May 2028 and May 2029. Lines 2.4.4 and 2.4.5 receive security fixes only, and 2.4.6 is on extended support. Everything from 2.0 to 2.4.3 has been unsupported since 2022, and Magento 1 since June 2020.
18.5% of the Magento 2 stores in this scan, 4,329 stores. The share depends heavily on the country: 41.4% in Belgium, 34.7% in the Netherlands, 25.9% in Germany, 17.7% in the United Kingdom and 12.2% in the United States.
No. It names no store, and it does not claim that any store is patched or vulnerable. From outside, a store can be placed on a release line and sometimes within a band of security releases, but an isolated patch or a hotfix changes nothing a visitor can see. What the report does count is stores on lines Adobe no longer patches at all.
No. The scan requested only what a browser requests: the homepage, the version page and a few static files. It sent nothing designed to trigger or confirm a vulnerability, and it never touched a cart, checkout, customer account or admin URL.
By what the page loads. A Luma-stack store loads RequireJS and Knockout and carries Magento's script initialisation blocks. A Hyvä store carries Hyvä's own markers and Alpine.js in their place. The scan reads those technical fingerprints and ignores words in the copy.
Because a store is counted here only after its own pages proved the platform and it answered in November 2026. Counts built on a single technology signature run higher, and they include parked and dead domains. Stores whose firewall refused the scanner are also missing here, so this is a verified sample and not a census.
Hyvä replaces the Luma front end, which ships a large JavaScript bundle to every page, with a much lighter one. Less script means faster loading and fewer layout shifts. The figures compare stores as they are actually built, so better-funded teams choosing Hyvä is part of the gap, and the theme is not the whole of it.
It runs software Adobe no longer writes security fixes for, so every vulnerability found since support ended is open unless someone else has fixed it. Some stores apply community patches or run a maintained fork of Magento 1, which the scan cannot see. For a store owner the practical point is that the cost of an upgrade or a move grows with each year it waits.
It depends on what the store needs. A store that uses Magento's catalog depth, B2B features or custom integrations usually does best upgrading, often with a move to Hyvä in the same project. A small catalog with simple needs may be cheaper to run elsewhere. We do both kinds of project, so the advice does not lean either way. Start with the free Magento audit or tell us about the store through the form below.
Yes. Quote any figure with a link to this page and the month of the scan, November 2026. If you need a cut that is not shown, such as a country or an industry, ask through the form below and we will run it where the sample is large enough.
Yes. The scan is repeatable, and the stores are rechecked on a rolling basis, so the same measures can be compared over time. This page will carry the newest edition and state the month of its data.
Send the domain through the form below and it is removed from the scan list. The report only ever publishes counts and shares, so no single store appears in it either way.
Let’s build something great together!
Tell us your store's address. An engineer reads its release, patches, storefront and speed from the inside, where the real answers are, and replies within one business day.