free, no account needed
What does your page actually do?
A real browser opens it, scrolls, clicks what is safe to click, and reports what it found — the dead controls, the failed requests, the loading states that never resolve, and the errors nobody told you about. We will ask where to send it on the next screen.
What it looks for
The things a page-speed score does not measure, because they need somebody to interact with the page rather than just load it.
Controls that do nothing
Clicked, and no DOM change, no request, no navigation. A handler that was never wired up, or was wired to an element that got replaced. Nothing throws and nothing is slow.
Requests that failed or crawled
5xx and 4xx seen from the page rather than from your logs, calls that never completed at all, and p95 timings that include DNS, TLS and the network — the number the visitor actually waits.
Loading states that never end
A spinner still turning when the page was left. Nothing errored, because the work that would have been slow never finished — which is why every server-side metric reports this as healthy.
Errors, with a place to look
Grouped by where in the code they happen rather than by their message. On a site whose scripts are not minified, that is a file and a line you can open.
What it cannot tell you
Worth saying before you read the report, not after.
- One session is not drift. This is a snapshot of what is broken now. Which deploy broke it needs the agent installed and two releases of real traffic — that is the product, and this is not it.
- The timings are one machine on one connection. Treat them as context. The dead clicks and failed requests are facts about your page; the LCP is a fact about our server.
- Only what gets clicked is checked. Nothing inside a form is touched, nothing that navigates, and nothing labelled as doing something — buying, deleting, subscribing. A page made entirely of links comes back quiet because nothing was safe to try.