Free tool

Online store speed test for Magento, WooCommerce and more

See how fast your store's server answers, whether the full page cache works, how heavy the home page is and what slows it down, with clear next steps.

Free, no signup. We only open public pages, like a visitor would.

What makes an online store fast

Speed starts at the server

Before the browser can draw anything, the server has to build the page. That wait is the time to first byte (TTFB). For a store, under 200 ms is very good, under 600 ms is fine, and over one second means pages do not come from a cache or the server is short of resources.

The test asks for the page twice. When the second answer is much faster, the full page cache works. When both are slow, every visitor waits for PHP and the database.

The numbers Google looks at

  • LCP (Largest Contentful Paint): when the main image or heading appears. Aim for under 2.5 seconds.
  • INP (Interaction to Next Paint): how quickly the page reacts to a tap or click. Aim for under 200 ms.
  • CLS (Cumulative Layout Shift): how much the layout jumps while it loads. Aim for under 0.1.
  • TTFB: not a ranking signal on its own, but a slow server delays everything that comes after it.

When Google's data is available, the report shows the PageSpeed mobile score next to our own measurements.

What slows most stores down

  • No full page cache, or a cache that a cookie or a module keeps bypassing.
  • Heavy JavaScript: the Luma RequireJS bundle, chat widgets, trackers and pixels.
  • Large images in old formats, without lazy loading below the fold.
  • No compression, no HTTP/2 and no CDN for visitors far from the server.
  • A small server: too few PHP workers, no Redis or Valkey, a database without enough memory.

How to speed up a Magento or WooCommerce store

Fix the server first: Varnish for Magento or a page cache for WooCommerce, Redis or Valkey, a current PHP with OPcache and enough memory for the database. Then trim the front-end: modern image formats, fewer third-party scripts and, on Magento, Hyvä.

Our hosting comes set up this way for Magento, WooCommerce and PrestaShop, and we move your store for free.

What the speed test measures

  • Server response

    Time to first byte on a first and a repeat visit, which shows whether pages come from a cache.

  • Delivery

    Compression, HTTP/2, a CDN and the size of the page on the wire.

  • Front-end

    Scripts and style sheets, scripts that block the first paint, lazy-loaded and modern-format images, and RequireJS against Hyvä on Magento.

Frequently asked questions

ShopWhizzy

ShopWhizzy support Magento since 2008

Talk to us

PageSpeed simulates a slow phone. We measure the server and the page itself, which is where most store slowness starts. Both are useful.

From our servers in Central Europe. Visitors far away will see slower times unless a CDN is in front of the store.

A working full page cache (Varnish), Redis or Valkey, OpenSearch, enough PHP workers, and a light front-end like Hyvä. Our Magento hosting comes set up this way.

Yes. Core Web Vitals are part of Google's ranking signals, and slow pages lose shoppers at every step, most of all on mobile.

The first request may have to build the page or fill a cache. The second shows what most visitors get when the cache works.

Both. The tool tests the address you enter, so run it on a category and a product page as well.

Want this fixed for you?

We host and look after Magento and Hyvä stores: fast servers, full page cache, nightly malware scans and security patches applied for you.