Right-click CPS: how to test your right and middle mouse buttons

Short answer: your CPS score is a left-click measurement. The CPS test counts the primary button only, so pressing the right or middle button adds nothing to it — there is no separate “right-click CPS” number, and a page that shows one is not reading those buttons the way it reads a left click. To check that your right and middle buttons work, use the mouse test, which lights up each button as you press it. Here is how, whether you can gauge their speed, and where the browser stops.

Why the CPS score is left-click only

The CPS test counts the primary (left) button and ignores the rest on purpose, so the number means one consistent thing across mice and browsers. Under the hood it only accepts a trusted, primary pointer press with button 0 (left); a right press (button 2) or a middle press (button 1) is dropped, and the right button’s context menu is suppressed so it does not interrupt you. That is why hammering the right button does nothing to your CPS: the counter never sees it.

How to test your right and middle buttons

Open the mouse test and press each button in turn:

• Right — registers as Right (the browser sees button 2, usually through the contextmenu event).
• Middle — press straight down on the wheel until it clicks; it registers as Middle (button 1, an auxclick).
• Left — registers as Left (button 0, the ordinary click).

If a button never lights up while the others do, that is the one to look at. The full button-by-button walkthrough is in test every mouse button, and a button that fires nowhere is covered in which button is not registering.

Can you measure right- or middle-click CPS?

Not as a calibrated score. The CPS test will not count those buttons, and the browser handles them differently enough that a per-second “right-click CPS” is not something a web page can measure reliably:

• The right button is tied to the context menu. A page can suppress the menu, but rapid right-clicking still competes with the operating system’s own handling, so the timing is noisy.
• The middle button arrives as auxclick, which fires less consistently under fast repeated presses than a left click does.

So you can confirm your right and middle buttons work and watch them register in the mouse test, but treat any single “right-click CPS” figure with suspicion — it is not the same controlled measurement the left-click test gives you. If what you want is your click speed, test it with the left button on the CPS test; if you want to know a specific button is healthy, the mouse test is the honest check.

Why left, right and middle look different to the browser

Only a left click fires the ordinary click event. Middle and right presses come through as auxclick and contextmenu, which is exactly why a page that listens only for click can look like it is ignoring your other buttons when they are working fine. The fixed button numbering — 0 left, 1 middle, 2 right — and the spec quirks behind it are laid out in test every mouse button.

What no browser can tell you

Whatever you are testing, a web page cannot read your mouse’s polling rate, DPI, or latency — those live in the device and the operating system, below anything a browser can see (see what a browser reports when you think it is measuring polling rate). A click test tells you a button fired and, for the left button, how many times per second — not the millisecond mechanics underneath.

If you came looking for “right-click CPS,” the honest version is this: measure click speed with the left button, and use the mouse test to confirm the right and middle buttons register. That pair answers the real question without pretending the browser can do something it cannot.