CROMagnet vs Google PageSpeed Insights: what each one tells you
Based on public information as of October 2026
In short
Google PageSpeed Insights tests how fast a single page loads and reports Core Web Vitals. CROMagnet reads the same Google data for your store, then adds checks on conversion, trust, tracking and discovery and explains each finding with its evidence. They are not rivals: one is a speed tool and the other uses it as part of a wider audit.
PageSpeed Insights and CROMagnet, side by side
| PageSpeed Insights | CROMagnet | |
|---|---|---|
| What it measures | Loading performance of one URL, plus accessibility, best practices and basic SEO | Speed plus conversion, trust, tracking and discovery, scored together |
| Real-visitor data | Yes, from the Chrome UX Report when the page has enough traffic | Yes, read from the same source and preferred over lab data when available |
| Pages covered | One URL per test | Several key pages for speed, plus cart and checkout where reachable |
| Result | Scores and a list of opportunities | A 0 to 100 Store Health Score, findings ranked by severity and fix steps for the platform |
| History and reports | Each test stands alone | Runs are compared, with fixed, new and regressed findings, and reports can be shared or white-labelled |
| Price | Free | Free first audit, plans from $19 a month |
What PageSpeed Insights does well
- Free and made by Google, so its numbers are the reference everyone else is measured against
- Shows real-visitor Core Web Vitals pass or fail for pages with enough traffic
- Quick for a one-off check of any single URL
- Detailed technical opportunities that developers can act on
What CROMagnet adds
- Reads PageSpeed data on more than the home page, so a slow template shows up apart from a slow site
- Names the element behind a layout shift or slow Largest Contentful Paint, and the theme file, plugin or app that owns it where it recognises it
- Covers what speed tools do not: the buy button on the phone screen, tracking that fires, policy pages, product data
- Keeps history, so you can see whether a change helped and whether a fix has come undone
Use PageSpeed Insights when
- You want a quick, free read on one page
- A developer needs the full technical diagnostics
- You only care about Core Web Vitals
Use CROMagnet when
- You want to know what is costing sales across the store, not only what is slow
- You need findings ranked and explained for a non-developer
- You report to clients or want to track progress over time
Using them together. Use PageSpeed Insights when a developer needs the deep diagnostic on one URL. Use the audit to decide which URLs and which problems are worth their time.
Common questions
001Does the audit use PageSpeed Insights?
Yes. Speed checks read Google PageSpeed Insights data, so the speed numbers agree with what you see when you test a page yourself.
002Why is my Store Health Score different from my PageSpeed score?
PageSpeed scores loading only. The Store Health Score weighs speed alongside conversion, trust, tracking and discovery.
See the difference on your own store.
Free, and every finding shows its evidence.