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.
free visitor simulation · no account
Find what breaks when a real visitor uses your site.
Paste a public page. A real browser will open it, scroll it, and safely interact with it — then show you the dead controls, failed requests, stuck loading states, and browser errors a speed score misses.
✓ No account✓ Read-only✓ Report by email
3found
visitor check completeOne thing needs attention now
high
Checkout button did nothingNo request, navigation, or visible change after click.
button#checkoutmedium
API request failedThe visitor received a 500 from /api/cart.
1.8scontext
Page weight is mostly JavaScript1.4 MB across 19 requests.
67%Beyond a page-speed score
The problems visitors feel — and dashboards miss
The things a page-speed score does not measure, because they need somebody to interact with the page rather than just load it.
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.
The free check is the first frame
A snapshot finds the bug. Sixty finds the moment it began.
Run the outside check now. If it finds something worth watching, the agent connects it to real visitors, backend work, database queries, and the exact deploy that changed them.
Run my free checkbeforeEverything looks normalrelease 9d3f01e
deployCheckout handler replacedrelease b84ca22
afterDead clicks appearSixty names the release
What it cannot tell you Read the boundaries
- 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.
No account. No card. A real result.
Ready to see your site through a visitor’s eyes?
Give the browser a public page. We’ll give you the evidence.
Run my free check