Rehearse peak season before it happens
Hyvä makes a Magento store fast. Evaluat checks that it is still fast when everyone turns up at once. Today, Evaluat joins the Hyvä Technology Partner Program.
One of the requirements for every Hyvä agency partner tier is that a minimum share of your live Hyvä projects pass Google's Core web vitals, and the bar rises with each tier. Those vitals come from real shoppers, and real shoppers do not arrive one at a time. They arrive in crowds, in the week of a campaign, on the evening a sale opens.
A storefront that passes on a quiet Tuesday is not the same storefront your tier score is measured on. Evaluat exists to measure that gap, which is why we are here.
Hyvä removed most of the JavaScript that made the Luma frontend slow. The question every merchant asks next is whether the store still holds up once the crowd arrives. We built Evaluat to answer that in real browsers, with the evidence recorded on videos.
Hyvä and Evaluat were built around the same conviction: what matters is what the shopper's browser actually does, not what a server log says. Hyvä acts on that in how a storefront is built. Evaluat acts on it in how a storefront is tested.
What is Evaluat?
Evaluat is a real-browser performance testing platform, founded in the United Kingdom in 2022. Every virtual user runs in its own isolated browser instance, with its own cache, cookies and cart, so a load test does what a shopper does: opens the homepage, searches, browses a category, adds to cart and goes through checkout.
While the store is busy, Evaluat captures Core Web Vitals (LCP, INP, CLS) per page and per session, alongside FCP, TTFB and Navigation Timing, plus an Apdex satisfaction score for the run as a whole. It keeps session video, network logs and console logs for every virtual user, so when something slows down, you can open that session and watch the moment it happened.
Journeys are assembled in a visual step editor rather than written in code, so there is no test suite to rewrite every time the storefront changes. Build the journey once and run it before every campaign.
How does Evaluat work with a Hyvä store?
It works with Hyvä as it is. No module, no compatibility layer to maintain, nothing to break when Hyvä ships its next release. Evaluat drives the storefront from the outside, in the browser, the way a customer would, so there is nothing to integrate and nothing to keep in step with a release.
Testing from the outside is also why the numbers differ from a traditional load test. Protocol-level tools replay HTTP requests. They never execute JavaScript, never load third-party tags and never render a page, which on a modern storefront is where most of the time goes. A protocol-level suite can therefore pass while checkout is unusable under load, and nothing in the results says so. Evaluat sits above that layer rather than in place of it, so your API and backend capacity testing stays where it is.
For a Hyvä store, the interesting part is where the bottleneck moves. Hyvä ships far less JavaScript than Luma, so the frontend stops being the limit. What remains is Magento's own work. Cart, checkout, login and every block marked cacheable="false" hit PHP, the database and your third-party integrations on every request, and the full page cache never touches them. That holds on Magento Open Source and Adobe Commerce alike. Those are the pages shoppers pile onto the moment a sale starts, which is why they are worth rehearsing, and the same holds for a headless storefront sitting on Magento APIs.
What this means for merchants and agencies
For merchants. You find out in a quiet week what your store does in the busiest one, while there is still time to fix it rather than explain it. A test runs at the concurrency you forecast for your biggest day, from the region closest to your customers, and shows which pages slow down, where checkout gives way and at what level of traffic. You can generate an Executive Summary, a plain-language verdict with findings ranked by severity, so the people who own the revenue can read the result without a performance engineer in the room.
For agencies. Evidence you can hand to a client: every virtual user leaves a video and logs behind, so you can show exactly what slowed down, on which step, at which level of traffic, and prove the fix on the next run. Then there is the tier score itself. A test before peak is the cheapest way to check that a storefront passing Core Web Vitals today still passes in the week that counts, which is the week the field data behind your tier comes from.
For developers. No scripts to maintain. Journeys are built step by step in the editor, with CSS selectors for the elements that matter, and verified with a preview run before any load test. Because the test drives the rendered page rather than the code behind it, a Hyvä upgrade does not mean rewriting a test suite, only checking that the steps still land.
Evaluat in action
Auping, the Dutch bed manufacturer, runs Hyvä Checkout and tests with Evaluat before campaign traffic arrives.

Evaluat helps us prepare our website, including Hyvä Checkout, for peak campaign traffic. Its real-browser load tests and clear reports uncover potential bottlenecks early, so we can improve performance before launch and deliver a smooth experience for our visitors.
Hyvä helps Magento and Adobe Commerce merchants build faster, better-performing storefronts. Technology partners like Evaluat complement this by helping merchants understand how their stores perform under real-world conditions and identify opportunities to improve!
Evaluat x Hyvä, in short
It is a good fit. Hyvä builds storefronts light enough to be fast. Evaluat runs them at sale traffic in advance and reports what shoppers would have seen. For Magento and Adobe merchants and the agencies behind them, the busiest day of the year becomes a rehearsal rather than a reveal.
Using Hyvä? Curious about Evaluat?
If you are running a Hyvä store, or building them for clients, book a short demo at evaluat.com/demo. They run a live test on your own store during the call, and you keep the report whether or not you take it further. There is more on the Magento specifics at evaluat.com/solutions/magento-performance-testing.

