Reads the day
Every page that got traffic, split by phone and desktop, because a page can be fine on a laptop and broken on a phone.
Most sites do not have a traffic problem. They have a leak — the phone visitor who taps your price box because it looks like a button, the form nobody finishes, the error that quietly kills the booking button on iOS. This watches your real visitors, names the leak in one sentence, and ranks it by how many people it costs you.
The demo below is not a mock-up: it runs the same scoring code as the live engine, and we prove it — 300 generated cases, 4,597 finding-by-finding comparisons, 0 differences. The tracker itself is live on this site, recording into our own database (verified end to end on 2026-09-09), with no analytics vendor in the middle.
On the left is a pricing page with three deliberate traps. Click around it like a customer would — tap the price, tap it three times fast, start the email field and walk away, scroll or refuse to. On the right, the engine names what you just did and what it would cost. Nothing leaves your browser, and the stand-in visitors are generated here, not borrowed from a client.
Board-certified team, 12 years in practice, same-week appointments.
30-day guarantee… the rest of the page continues down here, which is exactly the problem: the offer sits below where most phones ever reach. Scroll to the bottom and the engine will stop calling it a scroll wall.
Every page that got traffic, split by phone and desktop, because a page can be fine on a laptop and broken on a phone.
One plain sentence per problem — what happened, how many people it happened to, and the fix. No dashboard to interpret.
Dead buttons, broken links and code errors get fixed and the live page is re-checked to prove it took. Words, prices and offers come to you first.
Every leak is logged. When it stops appearing after a fix, it is closed with a date — so “we fixed it” is a record, not a feeling.
How real people use your page: how far they get, what they tap, where they tap something that is not a button, where they tap the same spot three times because nothing happened, which forms get started and never sent, and whether the page threw a code error while they were on it. No names, no emails, no recordings of a person — behaviour only.
A heatmap tool shows you pretty pictures and leaves the conclusion to you. This one names the leak in a sentence you can act on, ranks the leaks by how many people they cost you, and keeps a ledger so a leak that disappears after a fix is marked fixed. It also runs on your own domain, so the data is yours and there is no daily export limit.
No. It is one small script that loads after your page, listens quietly, and sends one tiny message when the visitor leaves. Nothing is loaded from a third party, and if it ever fails it fails silently — your page cannot break because of it.
It fixes the mechanical things without asking — a button that does nothing, a link that 404s, an error in the code — and re-checks the live page to prove the fix took. Anything that changes your words, prices or offer comes to you as a one-line recommendation first. A site that rewrites its own offer overnight off a noisy Tuesday is a liability, not an asset.
As soon as a page has been seen a handful of times. Under that, it says WATCHING and shows the raw counts instead of inflating two visits into a percentage.
It is part of what we run for clients — the tracking, the nightly read, and the fixes. There is no separate analytics bill, because it runs on your own site.
Want this watching your site — and the leaks fixed for you? Text Rudy and say LEAK.
Text Rudy: LEAK