Home Blog
Practical guides on speed, security, upgrades, SEO and growth for Magento 2 stores, written by the engineers who do the work.
How to audit Magento extensions before upgrading to 2.4.8 or 2.4.9: inventory, find unused modules, check PHP 8.4/8.5 compatibility and remove safely.
Same server, same catalogue, two frontends. We measured clean Hyvä against Luma on home, category and product pages, and explain what the difference really means.
Clean Hyvä pages reached a mobile LCP of 1.5 to 1.6 seconds in our benchmark. Here is what it takes to keep a real store under 2 seconds.
Magento rejects WebP uploads and Cloudflare’s free plan ignores Accept-header negotiation. Here is the cron job and small plugin we use to serve WebP safely.
A Lighthouse score is only as good as the way you measure it. This is the method we use on Hyvä stores, and the mistakes that produce misleading numbers.
We built an international checkout with four layout variants on our Hyvä demo store. Here is what we learned about addresses, payments, translations and CSP.
Once Hyvä removes Luma’s JavaScript weight, product images become the biggest factor in page speed. This is the image pipeline we use on Hyvä stores.
Seasonal campaigns, a new brand colour, a different look per store view: here is how we make Hyvä colours editable from the Magento admin.
Hyvä pages are easy to cache, but edge caching still needs clear rules. How we combine Magento’s full-page cache with Cloudflare without serving the wrong page.
Hyvä makes the frontend lighter, but production mode and a repeatable deploy still decide how fast and stable a store is. This is how we run and deploy Hyvä stores.
Hyvä uses Magento’s normal store views and translation files. Here is how we set up languages, translations and a flag switcher on a Hyvä store.
Hyvä gives search engines lean, server-rendered HTML, but it does not do your SEO for you. The markup, structured data and crawl points we check on Hyvä stores.
Ask us on WhatsApp. Good questions become new articles.
Tell us which sentence is wrong and what it should say. Thank you!
Thank you! We have received your report.
Something went wrong. Please try again or message us on WhatsApp.
Send your store details. We check speed, security and extensions, then reply with three quick wins within 3 working days.
Tell us about your store and we’ll reply within one working day. Prefer to chat? Say hello from WhatsApp
Step 1 of 4
You can change this per project later.
Choose one option to continue.
Step 2 of 4
So we know who we are talking to.
Please fill in your name, company and a valid email.
Step 3 of 4
Helps us prepare the first call.
What best describes you? *
Team size
Which platforms do you work with today?
Choose what best describes you.
Step 4 of 4
Check your details. You can go back to change anything.
Please tick the box to send your application.
Something went wrong. Please try again or message us on WhatsApp.
We have sent you a confirmation email. What happens next:
We usually reply within one business day.
English
German
Dutch
Turkish