The score Google already has of your site.
We run PageSpeed Insights against the pages that matter — home, product, checkout — on mobile and desktop, at the cadence you choose.
And we keep the history, because what drives sales is the trend, not today’s number.
Measured from the outside, no agent · mobile and desktop on every run · from Pro up
The four scores
Four independent scores, from 0 to 100.
Every analysis runs PageSpeed Insights against the URL, from the outside and with no agent. The result is four scores that measure different things — the numbers below are from a checkout.
Performance
How fast the page loads and becomes usable. This is where the Core Web Vitals live — LCP, CLS and company.
Accessibility
Contrast, form labels, keyboard navigation, image alt text, heading order. How well the site works for someone using a screen reader.
Best practices
HTTPS, libraries with no known vulnerability, console errors, deprecated APIs, images at the right resolution. Front-end technical hygiene.
SEO
The basics Google requires to index: meta tags, mobile viewport, crawlable links, robots. Not a content strategy — the foundation of one.
Performance is usually the lowest of the four — and it is the one that moves conversion. The other three rarely move sales, but they move indexing and process.
Lab vs. field
Lab and field, the two sides of the truth.
Lab is the test running in a controlled environment on every collection: repeatable, great for hunting regressions after a deploy.
Field is what Google actually saw on your users over the last 28 days. It is the side that counts for ranking — and the only one where INP exists.
Field data only shows up with enough real traffic — on a low-volume site, INP stays blank.
Noise-free alerting
One bad day does not wake you up.
Every page has a threshold, and the alert only fires after two consecutive collections below it — an isolated dip triggers nothing.
To count as recovered, it requires five points above the threshold. You do not get an on-off switch every collection: a real drop warns once, through the channels you already use.
Per page, not per site
Every page has its own target.
We measure URLs, not sites. Home, product and checkout come in as separate pages — each with its own threshold, cadence and history.
It makes sense: a blog at 60 is fine; a checkout at 60 is losing sales. No crawling the whole site measuring what does not matter.
The checkout is above 80, but below its own threshold — and it is the only one raising an alert.
Plans
Performance by plan.
| Free | Pro | Business | Agency | |
|---|---|---|---|---|
| Performance pages | — | 5 | 20 | 50 |
| Four scores from 0 to 100 | — | yes | yes | yes |
| Mobile and desktop every run | — | yes | yes | yes |
| Core Web Vitals: lab and field | — | yes | yes | yes |
| Drop alert with anti-flap | — | yes | yes | yes |
| Cadence configurable per page | — | yes | yes | yes |
Performance starts on Pro. The limits are on registered pages, not on analyses — each page runs at the cadence you choose, with no per-collection charge.
Where does the score come from?
From Google PageSpeed Insights, which runs the Lighthouse engine. It is the same score anyone sees when testing your URL — the difference is that we run it on our own, keep the history and warn you when it drops.
Does it measure on mobile or desktop?
Both, on every collection. Mobile is the default reading, because it is what Google uses for ranking and where the score tends to be worse.
What is the difference between lab and field?
Lab is a controlled, repeatable test, great for finding a regression after a deploy. Field is what your real users lived through over the last 28 days — the side Google counts for ranking.
Is this real-time monitoring?
No. Performance is measured by scheduled collection, because each analysis is expensive and slow. The one watching minute by minute is Uptime — the two work together.
Do you crawl the whole site?
No. You pick the URLs that matter. Crawling everything produces a big report and no decision; three right pages are worth more than three hundred.
Is the performance score the same as the security one?
They are separate things. Performance is 0 to 100 per page, from Lighthouse. Security is an A-to-F score per domain, calculated from the audit findings. One does not affect the other.
Why is my INP missing?
Because INP only exists in the field, and the field needs enough real traffic to form the p75. On a low-volume site Google simply does not publish the data — and we would rather leave it blank than invent a number.
Which plan is this on?
From Pro up, with 5 pages. Business gets 20 and Agency 50. The limit is on registered pages, not on analyses — the cadence is yours.
The full trio
Fast is only a third of it. Also up and secure — in the same dashboard.
A checkout that loads in 1.8s sells nothing while it is down, and a score of 100 does not protect anyone with an expiring certificate. The three modules live in the same account and the same invoice.
Start today
Google’s score, watched closely.
Add the home and the checkout, pick the cadence, and in the first week you already see a trend instead of a number on its own. No card to start.