Upgrading Magento 2 to Mage-OS 3.6 and Hyvä: speed, support and what it does for search and ads

Adobe ended support for Magento 2.4.6 on August 11, 2026, and for every older 2.4 release before that. A store still on one of those versions gets no more regular security patches, while new bugs keep being published. Upgrading to Mage-OS 3.6 with a Hyvä storefront puts it back on a supported, current platform, and on our own stores it made the storefront fast enough to score 98–100 on desktop.

Is your Magento 2 version still supported?

Adobe publishes an end date for every Magento 2.4 release line. After it, the line gets no more regular releases or security patches.

Unsupported is not a paperwork problem. When a critical flaw is published, supported versions get a fix and unsupported ones do not. We went through exactly that with our own server’s operating system: read how we patched 18 live sites in two days when a 9.8 Critical Linux flaw had no fix for the old version.

What changes when you move to Mage-OS and Hyvä

• Mage-OS is Magento, kept current by its community. It is a free, open-source distribution of Magento Open Source. Your products, customers and orders stay in the same database, and Magento extensions keep working.
• Hyvä replaces the old Luma storefront. Luma ships jQuery, Knockout and RequireJS to every visitor. Hyvä uses Tailwind CSS and Alpine.js instead, so pages carry far less code.
• No licence fees. Mage-OS is free, and the Hyvä theme has been free and open source since November 10, 2025 (OSL 3.0 and AFL 3.0, the same licences as Magento Open Source).
• Easier to change later. A Hyvä theme is plain templates and Tailwind classes, so small design changes are quicker and cheaper than in Luma.

Our six stores, measured

We run six live sites on Mage-OS and Hyvä: TGL Direct (vintage and collectibles), Wallpaper-Inc, Import Wholesales (garden and hardware), Chillicothe Market, AerialMG (aerial photography) and Beth Gerber, ERA Real Estate. On 2026-11-02 we measured every homepage with Google’s Lighthouse.

Desktop: all six now score 98–100. Four of them already did before any tuning; the other two were held back by oversized images.

Phones were a different story. Phones get a slower connection and processor, and every store had a few heavy images that desktop hid. So we tuned each one and measured again, the same way before and after:

What made the difference was rarely code. It was:

• Oversized images. Two homepages carried a 2.4–2.7 MB PNG as their main image. As WebP sized for phones, the same picture is 22–50 KB, and the main image now appears in about 1.6–2.7 seconds instead of 15–16.
• The right size for each screen. One image file for every device means phones download desktop pictures. Responsive images send each screen the size it shows.
• Loading the first screen first. Images in the first screen load at once; the rest wait until the visitor scrolls.
• No jumping layout. Space is reserved for banners and bars that appear late, so the page doesn’t shift under the visitor’s thumb.
• Scripts only where they are used. Payment scripts and styles load on cart and checkout, not on every page.

We apply the same tuning when we finish an upgrade.

What speed does for Google search and ads

We will not promise a ranking or an ad price, and nobody honest can. Here is what Google itself says:

• Search: “Core Web Vitals are used by our ranking systems.” Relevance still comes first, so speed helps most where several pages answer the same search equally well.
• Ads: Google Ads ranks ads using, among other things, “the quality of your ads and landing page”, and says that with relevant keywords and ads “you can still win a higher position at a lower price”. A fast, useful landing page is part of that quality.
• Sales: in a study of 37 brands commissioned by Google, Deloitte found that a 0.1-second faster mobile site went with 8.4% more retail conversions.

In short: a faster store gives Google one more reason to rank and price you well, and gives shoppers one less reason to leave.

How the upgrade works

1. Assessment. We review your Magento version, extensions, theme customisations and integrations, and give a fixed price before any work starts.
2. Staging copy. We upgrade a copy of your store, not the live one. Your database is upgraded in place, so products, customers and order history stay.
3. Extensions. Up to three third-party extensions are replaced with our own maintained ones, so future upgrades stop breaking on other vendors’ code.
4. Hyvä storefront. Your branding on a Hyvä theme, then tuned for phones as described above.
5. Your sign-off. You test the staging store. Nothing goes live until you approve it.
6. Cutover and 30 days of fixes. We switch the live store over in a short maintenance window and fix any bug you find in the first 30 days.

Is it right for your store?

• Your store runs Magento 2.4.6 or older, or 2.4.7 and you don’t want to repeat this in seven months.
• Your Luma storefront feels slow, especially on phones.
• Upgrades keep breaking because several vendors’ extensions fall behind.
• You want one accountable developer for the upgrade, the theme and the cutover.

The upgrade starts at $699.99 as a fixed package: see Magento 2 to Mage-OS + Hyvä Upgrade. Still on Magento 1? See the Magento 1 to Mage-OS + Hyvä migration. Want us to keep it fast and patched afterwards? See our managed hosting plans, or tell us about your store.

How we measured: Lighthouse 12.8.2, homepage only, mobile and desktop, several runs each with the median shown, from our own server, on 2026-11-02. Lab scores vary between runs and differ from Google PageSpeed Insights, which tests from Google’s servers. Sources: Adobe Commerce released versions, Google Search Central: page experience, Google Ads Help: Ad Rank, Milliseconds make millions (web.dev).