Where Hyvä performance work pays back
How this platform fits the wider commerce estate.
Questions we get asked.
Will Hyvä give us perfect Core Web Vitals?
No. Hyvä helps when the rest of the stack co-operates. We measure honestly against real buying journeys and do not promise specific scores.
What is a realistic gain from Hyvä performance work?
It depends on the starting point, third-party scripts and hosting. We measure before and after; we will not put a fixed number on it up front.
Where do most Hyvä performance problems come from?
Usually third-party scripts, image weight, hosting and over-eager JavaScript. The Hyvä framework itself is rarely the bottleneck once the basics are right.
Can iWeb monitor performance after launch?
Yes. Real-user monitoring, synthetic checks and CI performance budgets covered under the wider Hyvä support runbook.
Do we need to be on Hyvä to benefit from this work?
No, but this page is about Hyvä-specific tuning. Magento Luma performance work is a different conversation; we will say which fits the brief.
How does iWeb choose between platforms?
Against operational shape: catalogue depth, trade complexity, ERP integration, multi-territory rules and five-year cost. The decision is written down with trade-offs, not assumed from a vendor demo.
Where does ERP integration sit in the platform decision?
It is a primary input. Some platforms make ERP integration straightforward, some make it expensive. iWeb names the trade-off rather than hiding it.
Does iWeb deliver headless or composable storefronts?
Where they earn their place. The trade-off between optionality and integration surface is named upfront; composable is not a default.
How is search handled on this platform?
Native search where the query mix supports it; specialist engines (Algolia, Constructor.io) where the catalogue, volume or merchandising appetite justify them. Relevance is a continuous activity.
Where does PIM sit relative to the commerce platform?
PIM owns catalogue truth (attributes, variants, assets, channel readiness). The commerce platform reads from PIM rather than re-modelling deep product data in the storefront.
Can iWeb take over an existing build on this platform?
Yes, where the brief fits. iWeb will give a senior, written read on what is working, what needs remediation and what is honestly fixable, and the first month on support stays deliberately conservative on change.
How does iWeb size a five-year total cost picture?
Licence, hosting, engineering and support across the lifecycle, including the integration surface and operational ownership. The headline year-one number is rarely the honest comparison.