Skip to content

Performance

Hyvä is designed to be fast. Compared to Luma it ships far less JavaScript and CSS, avoids render-blocking resources, and includes features like Speculation Rules and bfcache out of the box. That said, a well-performing store still requires deliberate decisions throughout the project.

This chapter covers how to measure performance accurately, how to improve Core Web Vitals, and how to apply Hyvä-specific optimizations.

What is in this chapter

These settings require no code changes and have the highest performance impact relative to the effort involved. They are the foundation for everything else in this chapter.

Enable Varnish full page cache

Magento's built-in full page cache works, but Varnish dramatically reduces Time to First Byte by serving cached responses without hitting PHP at all. On a warm cache, responses under 200ms are common.

Enable it in the Magento admin under Stores → Configuration → Advanced → System → Full Page Cache → Caching Application.

For cache tag invalidation and ESI support to work correctly, follow the Magento Varnish configuration guide.

Configure Redis for cache and session storage

File-based cache is the default and is fine for development, but Redis is significantly faster under production load. Configure it for both the default cache and session storage.

See the Magento Redis configuration guide for setup instructions.