Dice roller
Dice in XdY notation, with modifiers, keep-highest, advantage and disadvantage, and the evening's history.
en / tools / click-test
Click and reaction test
How many clicks per second you can manage, and how long you take to react to a signal, averaged over five attempts.
Free, in the browser, no account
What to test
Best this session
— CPS
It lives in memory only: reload the page and it is gone. A record that persists is a leaderboard, and this is a test.
With the mouse or with the space bar. They do the same thing.
The green comes between one and a half and four seconds, at random: any sooner and you could count it.
An attempt is void if the click lands before the green, and also if it lands less than a tenth of a second after: below that threshold it is not a reaction, it is an early guess that paid off. The signal has to cross the retina, the optic nerve and the cortex before the finger even decides.
Void attempts stay out of the average but are counted. Simply discarding them would mean you could guess until a good number came out.
The time comes from performance.now(), which is monotonic and does not jump when the system clock is adjusted. What remains is the delay of your screen and of your mouse, which everyone has and which cannot be removed from here.
Everything happens in your browser: no data is sent anywhere.
How it works
- Choose whether to test clicks per second or reaction time.
- Hit the large panel: with the mouse or with the space bar, it makes no difference.
- On the reaction test it takes five valid attempts before the average says anything.
Why it exists
Because it is the first thing you check when a new mouse feels slow, when you change your setup, or when somebody quotes a number and you want to see it for yourself. And because doing it on a page that declares how it measures is not the same as doing it on one that only shows the result.
About early clicks
An attempt is void if the click lands before the green. So far, obvious. It is also void if it lands less than a tenth of a second after, and that is the part worth saying.
Below a hundred milliseconds it is not a reaction: it is an early guess that happened to pay off. The signal has to cross the retina, the optic nerve and the visual cortex before the order to move a finger is even issued, and that path takes a length of time nobody shortens. Without that threshold, the way to get a good score would be to guess, and the average would end up rewarding whoever is not reacting at all.
Void attempts stay out of the average, but they are counted and shown. Simply discarding them would mean you could guess until a number you liked came out, and show the average of someone who missed three times as if they had never missed.
About the wait
The green arrives between one and a half and four seconds, drawn afresh each time. The window starts at one and a half seconds because below that you can count it out: if the wait were always around half a second, what you would be measuring is not a reaction but the ability to anticipate a rhythm.
About what is really being measured
The stopwatch is performance.now(), which is monotonic: it does not jump backwards when the system
adjusts the time on its own, something a normal clock does and which would hand a negative time to
somebody who did nothing wrong.
What stays inside the number, and cannot be removed from here, is the delay of your screen and of your mouse. On a 60 Hz panel one frame lasts sixteen milliseconds, and the green cannot appear before the next frame. That applies to everyone equally, so comparing your own attempts stays meaningful; comparing yourself with somebody else’s number on somebody else’s screen, rather less.
And for the same reason the colour changes instantly, with no fade: a tenth of a second of transition would land inside everybody’s reaction time.
About your data
Everything happens in your browser. The record stays in memory until you reload the page: it is not saved anywhere, and there is no leaderboard — a record that persists is a competition, and this is a test.
From here you also go here
Webcam and microphone test
Check that your camera and microphone work, with the detected resolution and a live audio level. Nothing is recorded.
Keyboard test
Press a key and watch it light up on the drawing. Shows the key code, how many you are holding at once, and which ones you have already tried.