Click Test
Click as fast as you can: the score is clicks per second over the last five seconds, and your best is remembered.
What CPS actually measures
Clicks per second is the count in a rolling five-second window. Short bursts inflate it, which is why the window is fixed and the number settles instead of spiking on the first click.
A mouse is usually good for six to ten clicks a second; a touchscreen or a trackpad with a light switch can go higher. Anything above twenty is almost always a macro or a double-clicking switch, not a human.
The double-click problem
A worn switch registers one press as two, and a CPS test is where that shows up as an impossible score. If your number is much higher than your clicking feels, try the mouse test and watch whether one press counts twice.
The best score is stored in this browser so it survives a reload; the tally in the window resets whenever you press again after a pause.
Reading the number fairly
The window is fixed at five seconds so a fast start does not dominate the score. If you stop clicking, the number decays as old clicks fall out of the window, which is why it settles rather than freezing.
Compare like with like: a mouse, a trackpad and a touchscreen produce very different numbers, and a phone held in one hand is not the same test as a desktop with a wired mouse.
How Click Test works
Measure clicks per second over a five-second window, keep your best score, and see the total in the window. The method behind Click Test is the single-purpose logic inside wave51.js, and this page shows the result with its assumptions in the open.
- Open Click Test and provide click test — the page accepts it in the field it shows.
- For Click Test, browser APIs and, where stated, one public endpoint do the work.
- The Click Test output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.
A worked example for Click Test
A typical run of Click Test starts with click test and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.
Repeat the check on a second network: a result that changes with the network is a routing fact, not a fault in your device. That check applies directly to Click Test with click test.
When to use Click Test — and when not to
Reasonable uses: Diagnosing a connection; Checking DNS or registration data; Testing hardware in the browser. Click Test is deliberately narrow: it does one job and states its assumptions instead of hiding them.
Diagnostic apps and terminal tools go deeper but need installs or shell access. For a quick lookup or a device test, a page is the lower-friction path. The honest ceiling for Click Test: for Click Test, results reflect your network and device.
- Best case for Click Test: Diagnosing a connection
- Also fine with Click Test: Checking DNS or registration data
- Not what Click Test is for: for Click Test, results reflect your network and device.
Reading the Click Test result
The output of Click Test is a function of the inputs alone — no hidden state and no server.
Accuracy and limits of Click Test
The method is the single-purpose logic inside wave51.js. Click Test prints results at the precision its inputs justify, and the limits below are the honest ones:
- Click Test: For Click Test, results reflect your network and device.
- For Click Test, pages that call an endpoint say so and call it only on your click.
Privacy and speed on the Click Test page
The Click Test page is a static file plus wave51.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.
Speed follows the build: Click Test loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.
What you get from Click Test
The output of Click Test appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the web work finishes the moment the numbers are in.
Because Click Test is built from wave51.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.
Questions
What does Click Test do?
Measure clicks per second over a five-second window, keep your best score, and see the total in the window. Everything runs in your browser; nothing is uploaded.
How accurate is Click Test?
The method is the single-purpose logic inside wave51.js. For Click Test, results reflect your network and device.
What are the limits of Click Test?
For Click Test, pages that call an endpoint say so and call it only on your click.
Is anything uploaded when I use Click Test?
No. Click Test runs entirely in the browser tab; nothing is uploaded, stored or logged.
Can I use Click Test offline?
Yes — Click Test keeps working offline once the page has loaded; the whole tool is a local script.
Keep going
More web tools
Mouse Test
Check left, right and middle buttons, count wheel ticks, and see a rough movement rate. Catches a double-clicking switch.
Open toolSpeaker Test
Play a tone on the left, the right or both, check individual frequencies, and run a sweep to hear rattles or a dead cone.
Open toolGamepad Tester
See every button press, both sticks and the axes of a connected controller, with the mapping the browser reports.
Open toolWebcam Test
Open the camera in the page, see the resolution and frame rate it reports, switch between cameras, and stop it cleanly.
Open toolMy Location
Show my exact latitude, longitude and accuracy on one page. The location comes from your browser and stays in your browser.
Open toolScreen Resolution
Your screen resolution, available screen area, browser viewport and device pixel ratio — shown live and updated as you resize.
Open tool