Expedio

Why we built it

A page reaches a shopper in two halves. Modern themes fixed the second half. Expedio fixes the first.

Two halves of every page

1 · Time to first byte

The server produces the HTML

Where Magento is still slow, and the half Expedio takes on.

2 · First byte to largest paint

The browser draws the page

Largely solved by modern Magento themes such as Hyvä.

Hyvä shortened the time between the first byte and the largest paint, and on stores running it we see good largest-paint times once the HTML arrives. The time to the first byte is where Magento is still slow, and that is the half Expedio takes on.

Magento's slowness is measurable

Share of sites that meet Google's “good” time to first byte of 800 ms. Chrome real-user data, HTTP Archive, August 2026.

Magento
22%
Shopify
82 to 92%

It matches what we see across the Magento stores we run: a typical page takes around a second before the browser receives anything.

Stock Magento is already fast here

Much of Magento's slowness is hosting: CPU speed, storage, and how its services are configured. The benchmark ran on ReadyMage, scandiweb's Magento hosting, with high-frequency CPUs, low-latency storage, and the database, search, and cache on the same machine. That is the baseline Expedio is measured against.

Visit ReadyMage
70 to 472ms
Unmodified Magento on ReadyMage, no page cache
Already better than most Magento stores