Hyvä - Guides

Your Hyvä Store Is Still Slow. Here Is Why.

July 1, 2026 - Alexandru-Manuel Carabus

You paid for Hyvä and the store is still sluggish. The theme is almost never the reason. Here is what actually causes it, and how one store went from PageSpeed 12 to 100 without changing platform.

A clean, minimal online store page sitting above a thin dividing line, with a dense tangle of dark server blocks, pipes and cables packed below it, illustrating how a fast Hyvä frontend can hide a slow Magento backend.

You did the sensible thing. You moved off Luma, paid for a Hyvä build, and waited for the numbers to move. They did not. The store still feels heavy, the mobile score is still embarrassing, and someone is now asking whether Hyvä was worth it.

It was. The theme is almost never the reason a Magento store is slow.

Hyvä does not guarantee performance. The implementation does.

Hyvä replaces the frontend. It gives you a lean template layer that scores 90 to 100 on mobile out of the box, and it makes development dramatically cheaper: a feature that costs 20 hours on Luma typically ships in 3 to 4 on Hyvä.

What it does not touch is everything that happens before the browser receives a single byte. If your server takes eight seconds to produce the HTML, the fastest theme in the ecosystem will still deliver a slow page. Hyvä fixed the part you could see. The part you could not see was never addressed.

What "still slow" almost always means

In the stores we take over, the cause is nearly always one of three things, and usually all three at once.

Third-party modules nobody audited. Every extension you installed to solve a small problem is still running on every request, including the ones you stopped using two years ago.
A database doing far more work than the page needs. Uncached queries multiply quietly. We have opened a single product page and counted 15 million database operations behind it, none of them coming from Magento itself.
A server tuned for the wrong thing. Redis, Varnish and the cache layers are usually present and usually misconfigured, so the store pays for infrastructure it is not actually using.

None of that is a Hyvä problem. All of it survives a re-theme untouched.

Same Magento, same Hyvä, a completely different store

Vitacom sells electronics across B2C, B2B and export, and has traded since 1991. When they came to us the store was already on Hyvä. It scored 12 on PageSpeed and took 15.8 seconds to return the first byte. By the usual logic, Hyvä had failed.

We did not change the platform and we did not replace the theme. We removed roughly 180 modules, rebuilt the data and caching layers, and hardened the server.

PageSpeed 12 to 100. Response time 15,814ms to 12ms. On a server eight times smaller than the one they were paying for.

Hyvä was never the problem. The partner was.

How to tell which problem you have

There is a quick diagnostic you can run yourself. Load a product page and look at time to first byte, not at the overall score. If TTFB is under 200ms and the score is still poor, the frontend is worth investigating. If TTFB is measured in seconds, no amount of frontend work will save you, and anyone proposing a re-theme is selling you the wrong thing.

That is the difference between a store that needs tuning and a store that needs a rescue.

What to do next

If the numbers above sound like your store, get the codebase and the server looked at properly before spending anything else on the frontend. Our deep code and server analysis costs 999 EUR and includes 30 days of support afterwards. The output is a recovery and modernisation plan that belongs to you and works with any agency, including the one you already have. There is no lock-in, and that is deliberate.

The technology was never the thing holding your store back. Find out what was.