About clicktest.pro
Who built these tools, and how the measurements work.
The short version
clicktest.pro is built and run by deedy, one person, as a set of free browser tools. Half of it measures how fast you click. The other half — the half that matters — tells you whether your mouse is broken. Nothing you click is uploaded, and there is nothing to sign up for.
Why it exists
Click-speed testers are everywhere, and most of them are the same counter wrapped in advertising. The interesting problem is the one underneath: a mouse that has started sending two clicks when you pressed once, and an owner who cannot tell whether the fault is the hardware or their own hand.
That question has a real answer, and a browser can measure it. So the CPS tools are the front door — they are what people search for — and the diagnostic tools are the reason the site is worth keeping. If you arrived to compare your CPS with a friend, that is fine. If you arrived because something feels wrong with your mouse, that is what this was built for.
How the measurements actually work
Every tool here reads the input events your browser hands to the page and the timestamps attached to them. A click is counted the moment the event fires; the clock starts on your first click rather than on page load, so reaction time never counts against your score.
The trace under each tool is the part worth understanding. Each tick is the gap between one click and the next, drawn on a logarithmic scale and inverted so that faster reads as taller. On a speed test that shape is your rhythm — even bars mean steady clicking, ragged bars mean you are burst-clicking. On a diagnostic test the same shape is the evidence.
This is a browser, not an oscilloscope. Timing is deliberately coarsened for security reasons, and polling rate, wireless links, drivers and background load all sit between your finger and the number. Run a test twice before you trust it.
Where the 70ms threshold comes from
The double-click and key-chatter tools flag any gap under 70 milliseconds. That number is not a house style — it is the point below which a human explanation runs out.
The fastest deliberate double-click a person can produce lands around 100ms between presses, and sustained clicking sits far slower than that. Below roughly 70ms you are past what a finger can do twice, so an interval that short did not come from you. It came from the switch: the contacts bounced on a single press and the mouse reported two. That is the fault, and the trace is where you see it happen.
The threshold is drawn as a line on the diagnostic tools for exactly that reason — a tick crossing it is the diagnosis. It is deliberately absent from the speed tests, where a 66ms gap means a fast clicker rather than a broken switch. Treat a crossing as strong evidence, not a verdict; the terms say the same thing in more careful language.
How it is built
The tests run entirely in your browser. There is no account, no leaderboard and no saved history, because all three would mean collecting your results, and the privacy policy promises the opposite: no cookies, no analytics, no advertising, no third-party requests. That claim is checkable — open the Network tab and reload any page.
The site is also deliberately fast and still. Every page is static, the layout reserves space for a result before there is one so nothing jumps as you use it, and the tool you came for is in the first screen on every page.
Who is behind it
deedy builds and maintains clicktest.pro. GitHub is the best place to see what else I work on.
If a reading looks wrong, if a tool misbehaves on your hardware, or if you disagree with the 70ms figure and can show why, I want to hear about it — that is the kind of message that changes the site. The contact page reaches me directly.