megs / Magento Speed Scanner
Free · Coming soon

Find out what slows your Magento store down.

Enter your store URL and get a speed diagnosis in Magento terms: what's slow, why, and the fixes ranked by impact. No login, no install, nothing touches your store.

Preview · the scanner isn't live yet. Join the waitlist to get it first.

example-store.commobile
Example report
Slow on mobile. Pages are rebuilt on every visit.Full page cache isn't serving pages
LCP
4.8 s
TTFB
1.9 s
INP
310 ms
CLS
0.04

Your Magento setup

Magento 2 · Luma Varnish: not detected JS bundling: off Images: JPEG only CDN: Cloudflare
#1
Turn on full page cache with VarnishEvery page is built from scratch, so the server takes 1.9 s to respond before anything loads.

How a scan works

Under a minute, from URL to diagnosis.

01

Fetch your store

We load your public homepage once, like a single visitor would.

02

Run Lighthouse

Core Web Vitals on mobile and desktop, plus real-user data when Google has it.

03

Check the Magento setup

Theme, full page cache, Varnish, JS bundling, CDN and images, read from public signals.

04

Write the diagnosis

What's slow and why, in plain language, with the fixes ranked by impact.

What it checks

The things generic speed tests don't understand.

theme

Luma, Hyvä or custom

The theme decides how much JavaScript every page ships. We detect it and read your numbers in that light.

cache

Full page cache & Varnish

Whether pages come from cache or are rebuilt on every visit, the biggest single cause of slow Magento stores.

frontend

JS bundling & requests

Dozens of small RequireJS files, render-blocking CSS and heavy third-party scripts.

delivery

CDN, compression, HTTP/2

How your assets travel: CDN, Brotli or gzip, cache headers and protocol.

images

Formats & sizes

WebP or AVIF, oversized product images, lazy loading and missing dimensions.

vitals

Core Web Vitals

LCP, INP and CLS from Lighthouse, and from real Chrome users when the data exists.

Example report · top problems

Ranked by impact. Honest about what we can't see.

01

Full page cache isn't serving pages

No cache hits on repeat requests and a 1.9 s server response: pages are rebuilt for every visitor.

FIXEnable Varnish as the full page cache and check that category and product pages are cacheable.

detectedyour developer
02

142 JavaScript files load before the page is usable

Luma with RequireJS and no bundling: the browser fetches files one by one.

FIXBundle JavaScript, or plan a move to a lighter theme such as Hyvä.

detectedyour developer
03

Product images are 4× larger than shown

JPEGs up to 2400 px wide in a 600 px slot, and no WebP.

FIXServe resized WebP images and add width and height to stop layout shifts.

likelyyour developer

FAQ

Questions

Is it free?

Yes. The scan and the report are free. We may later offer paid monitoring for stores that want to know the moment they slow down, but the scanner stays free.

Does it touch my store?

No. It reads only what any visitor's browser sees: your public homepage, its assets and response headers, plus Google PageSpeed data. No logins, no admin pages, no load testing.

Which Magento versions does it support?

Magento 2 and Adobe Commerce, with Luma-based, Hyvä and custom themes. Magento 1 stores are detected and get the general speed results.

What if my store isn't on Magento?

You still get the standard speed results, with a clear note that the Magento-specific diagnosis doesn't apply.

When does it launch?

We don't promise dates. Join the waitlist and we'll email you once when it's ready.

Waitlist

Be the first to scan your store.

One email when the scanner launches. No dates promised, no spam.

By joining, you agree to get one email when the scanner launches. Unsubscribe anytime. See our privacy policy.