About

This is a small tool built by Jose Pollman. It runs on Google’s PageSpeed Insights and Chrome UX Report APIs, which are the same sources PageSpeed Insights itself uses.

Why it exists

Every speed testing tool opens with a score out of 100. Watch what happens next: people try to raise the score. They chase whichever audit looks easiest, ship changes that move the number without moving the experience, and come away believing performance work is arbitrary — because from where they are standing, it is.

The measurements were never the problem. The presentation was. So this tool puts the same data in a different order: the one change that recovers the most load time, then what that time is plausibly worth, and then all the numbers underneath as supporting detail. The Lighthouse score is still there. It is at the bottom, which is where a number that tells you nothing actionable belongs.

How it makes money, and what that does not buy

There is an affiliate link to a hosting provider, and it appears under one condition: your measured server response time is over 600ms. That is the point at which the server is genuinely a meaningful part of your problem.

If your bottleneck is images, JavaScript, third-party scripts or layout shift, no hosting product is mentioned anywhere in your result. Not lower down, not in a sidebar, not rephrased as a suggestion. This is a rule in the code, not a policy someone remembers to follow, and the server guide tells you to try caching and a CDN first because those are free and usually sufficient.

The reason to be strict about this is straightforward. A speed tool that recommends hosting to everyone is not a speed tool, and the communities this thing needs on its side can spot one instantly.

What it is not

It is not a monitoring service, it has no accounts, it does not save your history, and it tests mobile only. If you want a request waterfall, use GTmetrix. If you want the full Lighthouse report including accessibility and SEO, use PageSpeed Insights. Both of those pages are honest about where those tools beat this one.

Corrections

If a result looks wrong, it might be. PageSpeed Insights is the source of truth — if we disagree with it, believe it, and the bug is ours. The privacy page sets out exactly what is stored, which is very little.