Monitoring · in development

Know when your site slows down or goes offline

One new script, a heavier hero image or a release can take a page’s score down, and nothing tells you when it happens. We’re planning monitoring that does. It isn’t running yet: tell us what you would use, we’ll build what people ask for first and write to everyone who asked.

Request monitoring Check a page today

What we plan to watch

Tick what you would use. It decides what gets built first.

Speed of your main pages. The home page and the sections you name, measured on a schedule, with a message when a number really moves. Site going down. A message when your site stops answering or starts returning server errors. Slow pages found for you. The pages that score below 50 or from 50 to 89, judged on several runs, so you know where to start. Fast offered on slow pages. We measure those pages through WebSpeed Fast and show both numbers. You decide, and nothing switches on by itself. Fixes in page code. Schema, sitemap, canonical, hreflang, redirects. Done by hand, for sites served through WebSpeed on their own domain.

Anything else you’d want watched or fixed? (optional)

Your name Email or Telegram

Site URL

A request commits you to nothing. There is no launch date or price yet.

Why one bad score shouldn’t set off an alert

PageSpeed scores move on their own. We took 8,265 pairs of consecutive measurements of the same page from our audits, keeping only pairs where the page weight stayed within 5%. In 97.5% of them, a score of 90 or above moved by 6 points or less, a score from 50 to 89 by 25 or less, and a score below 50 by 30 or less.

So an alert should clear those limits and hold on a repeat run before it reaches you. These are sites we audited up to 2 October 2026, not a random sample of the web. More in why the score changes between runs.

What a request means today

Nothing is running yet. Until we write to you, your site isn’t being watched and no alert will come.
We answer the first requests ourselves. We expect to watch those sites by hand at first: one measurement a week and a letter from us.
We’ll tell you either way. If we decide not to build what you asked for, we’ll write and say so.
Results stay private. The free speed test publishes its report at a public address. Monitoring results won’t be published.
Public pages only. PageSpeed Insights can’t open a page behind a login, so we can’t measure one.

Want the numbers now? The website speed test compares a page with its Fast version for free. If you’re considering Fast itself, see how we connect a site.