Skip to content
DeviceBench

Free right-click speed test

Right click CPS test with the menu held back

While a run is live, the browser’s context menu is canceled inside the test pad and nowhere else, so a burst of right clicks reaches the end of the timer instead of stopping at the first pop-up. The suppression is scoped twice — to the pad, and to the run — and the banner above it always states which of the two states you are in, so nothing stays intercepted after the timer stops. Only presses reporting the second mouse button are scored; a left press, a wheel press or a macOS Ctrl-click is named on screen and kept out of the figure.

  • 100% free
  • No signup
  • Menu suppressed on the pad
  • 5 or 10 seconds
  • Nothing stored
Right-click menu behaves normally everywhere
0Arm the pad first — otherwise a right press opens the menu.
LeftWheelRight
Right clicks per second
Best single second
Menus intercepted
0
Left presses ignored
0

A touchscreen has no second button at all — a long press raises the same menu, but through a timer rather than a switch, so there is nothing here for a phone to measure. A trackpad works if secondary click is switched on, though a one-piece clickpad has a single hinge under the whole surface and cannot report the two sides independently.

How to score a right button without the menu getting in the way

Three steps. The first exists because a right button cannot be counted while the menu keeps opening.

  1. Arm the pad, and watch the banner change

    Nothing is intercepted until you press Arm. The banner above the pad states which of the two states you are in, and while it is amber the browser's own menu is canceled inside the pad and nowhere else — the rest of the page, and every other tab, behaves exactly as it always did.

  2. Press the right button; the first press starts the clock

    Choose a 5 or a 10 second run first, then work the right button. The three lamps under the counter read the buttons currently held rather than the last one pressed, so if a lamp stays lit after your finger has come off, that button is physically stuck and the score is the least interesting thing on the screen.

  3. Check what the pad refused to count

    Two figures under the pad exist to keep the score honest: menus intercepted, which is how many times the browser would have opened one, and left presses ignored, which is how many times you hit the wrong button. If the second number is not zero your hand is drifting back to the button it knows, and the score is lower than your right button deserves.

Technical specifications

Presses countedpointerdown reporting button 2, and nothing else — a wheel or side-button press is not scored
Menu suppressionCanceled on the pad element only, and only between arming and the end of the run
Menus interceptedCounted and shown, so you can see how many times the run would otherwise have been broken
Platform behaviorWindows raises the menu on button release; macOS and most Linux desktops raise it on press
Ctrl-click handlingA button-0 press with Ctrl held is identified as a macOS secondary click and excluded from the score
Run lengths5 and 10 seconds only — a right-button sprint longer than that measures your wrist, not the switch
Held-button lampsRead from event.buttons rather than the last press, so a button stuck down stays lit
What is storedNothing at all — no best run, no local storage entry, no counter that survives a reload

Frequently asked questions

Why do other click tests open a menu when I use the right button?

Because they never cancel the context menu, or they cancel it for the whole page and forget to give it back. A right press raises a menu by default, the menu takes the pointer, and the run is over — which is the entire reason this page has an armed state instead of just counting clicks. Suppression here is scoped twice over: to the pad, and to the period between arming and the end of the run.

Does the menu stay blocked after I finish?

No. The pad disarms itself the instant the timer runs out, the banner goes back to gray, and a right press inside the pad opens the menu again like anywhere else. You can also hand it back mid-run with the same button you armed it with. A page that quietly kept the menu suppressed would be changing how your browser behaves in a region you might click by accident an hour later.

Why is my right-click score lower than my left?

Almost always training rather than hardware. The index finger is the one with thousands of hours on it, and it is also the only finger with a muscle dedicated to it alone — extensor indicis, which no other finger has an equivalent of — so it starts and stops more crisply than the middle finger doing the same job. A gap of a couple of clicks per second between your two buttons is ordinary; a gap that appears suddenly on a mouse you have used for years is not.

Does the menu open when I press the button or when I let go?

It depends on the operating system, and the difference matters at speed. Windows raises the context menu on the release of the right button, macOS and most Linux desktops raise it on the press. That means an unarmed run on Windows can get several clicks in before the first menu appears, while on a Mac the very first press ends the run — so a test that works passably on one machine can look completely broken on the other.

My trackpad does not register a right click at all.

Check that secondary click is switched on in your system settings before blaming the hardware, because several laptops ship with it off. Beyond that, a modern one-piece clickpad has a single hinge and one switch under the whole surface, so the right side is a region the driver recognizes rather than a second button — it can report a secondary click, but it cannot report one on each side at once, and it will never sustain the rate a two-switch mouse will.

I held Ctrl and clicked, and the page said that was not the right button.

It was not: on macOS, Ctrl with a left click is a secondary click, and the menu it produces is genuine, but the switch closing underneath is the left one. The page detects that combination — a press reporting button 0 with the Ctrl modifier set — and says so rather than scoring it, because the whole point of this run is the right switch. If you are testing a trackpad, turn secondary click on and use two fingers instead.

Can a right button start double-clicking on its own the way a left one does?

Yes, and it is much rarer for a reason worth knowing: both buttons usually have the identical micro-switch under them, but the left one absorbs the overwhelming majority of a mouse's lifetime actuations. A right button that has begun to chatter has either been used unusually hard — some games map primary fire to it — or has a manufacturing fault rather than wear, which makes it a much stronger warranty case than a worn left button of the same age.

About the context menu, and why the right button behaves differently

The right mouse button has carried a menu since Windows 95 made it the standard gesture for “tell me about this thing”, and the browser inherits that: a right press on any element raises a context menu unless the page explicitly cancels the event. That single default is why right-click speed tests are rare and why most of the ones that exist do not work. A page can cancel the menu, but doing so is a real intrusion — it is taking away Open in new tab, Inspect, Copy image and Back — so the cancellation here is bounded on both axes: it applies to one element on one page, and it applies only while a run is actually being timed.

Two hardware realities set the ceiling on what you will score. The first is that on almost every mouse both main buttons sit on identical micro-switches, but they have lived completely different lives — the left button collects the overwhelming share of a mouse’s actuations over its life, so the right switch is typically the crisper of the two and the one far less likely to have started chattering. The second is that a laptop clickpad is not two buttons at all. It is one hinged surface over a single switch, with the right-hand region interpreted by the driver, which is why a clickpad can report a secondary click but cannot hold a fast right-button run and cannot report both sides at once. If the lamps under the pad suggest a button is registering when it should not, the mouse test walks every button in one pass.

What a browser can see here stops at the event. A press arrives labeled button 2, and that label is all there is — it does not say whether a physical right switch closed, a trackpad driver decided a two-finger tap counted, or a side button was remapped to secondary click in vendor software, and all three produce an identical event. So treat this figure as a measure of the whole path from your finger to the tab, and compare it with your own left-button number from the CPS test rather than with a stranger’s. If your right-button figure is unexpectedly high, check what your hand is actually doing on the jitter, butterfly and drag click test, which measures each of the three named methods separately.

What the pad keeps when you leave

Every number on this page is worked out by JavaScript running in the tab you are reading it in. Nothing you type, paste or open is uploaded, logged or kept, which is also why the tools carry on working after you disconnect from the network.

Nothing on this page outlives the tab. There is no best run, no stored figure and no local storage entry — reload and the counter is back at zero and the pad is disarmed, which is also the fastest way to be certain the context menu has been handed back.