⚡MageSpeedTestMagento performance benchmarking

Speed test

Benchmark your Magento storefront.

Submit your storefront URL. We run two backends in parallel: Google PageSpeed Insights for the Lighthouse mobile-performance score and the four Core Web Vitals, plus a custom Magento probe that inspects the response headers and HTML to detect full-page-cache state, Varnish or CDN presence, theme (Hyvä vs Luma), compression, and HSTS. Each finding links to the relevant optimisation guide.

Combines Google PageSpeed Insights (mobile, performance category) with a server-side Magento probe. Test takes 20–60 seconds.

What the metrics mean

  • LCP — Largest Contentful Paint. When the largest content element finishes rendering. Target: under 2.5 seconds.
  • INP — Interaction to Next Paint. Worst-case latency between a user interaction and the next paint. Target: under 200 ms.
  • CLS — Cumulative Layout Shift. Visual stability during load. Target: under 0.1.
  • TTFB — Time to First Byte. Server response time. Target: under 800 ms; the Magento-specific number to chase is under 300 ms.

What the Magento probe checks

  • Full-page cache state. Reads the X-Magento-Cache-Debug header to see whether the page was served from cache (HIT) or rendered from scratch (MISS).
  • Varnish / CDN presence. Inspects the Via, Age, CF-Ray, and X-Served-By headers to identify cache layers between the visitor and the origin.
  • Theme detection. Scans the HTML for Hyvä-specific markers (Alpine.js, the /static/frontend/Hyva/ path) versus Luma-specific markers (RequireJS, mage/cookies.js).
  • Compression. Checks the Content-Encoding header for brotli, gzip, or no compression.
  • HSTS. Checks the Strict-Transport-Security header.

For the underlying optimisation playbook, see all guides or jump straight to Why Magento Stores Are Slow for the foundational overview.