INPUT CHECK / 01
Mouse test.
Get a clear result from one basic mouse check.
Use this online mouse tester to check movement, mouse buttons and both wheel directions. We show whether the browser check meets our rule, which signal is missing, and what to try next.
MOUSE TEST AREA ↘
Start the online mouse test
Nothing is being recorded yet.
WHAT THE BROWSER SEES
Live signals
Press Start mouse test first. Then move, press and scroll inside the test area. Try Back and Forward there too, if your mouse has them. Only mouse-type input is counted.
Side-button result: no Back or Forward page event yet.
The + and − signs describe browser events, not physical wheel ticks or the direction page content moves.
Wheel direction feels irregular? Run the two-direction scroll wheel test.
Waiting. Press Start mouse test above.
See your result ↓Not checked enough yet
Try the basic actions in the test area above.
The page updates this answer as browser signals arrive.
Our basic rule: movement, main and secondary presses, and wheel events in both vertical directions must reach this browser. How this check works.P press · R release · 2 double-click · + / − wheel sign · M move · D drag
View exact events and times
- No input recorded yet. Try a mouse action in the test area.
A COMPLETE FIRST CHECK
Run the mouse button test and basic input check
Movement, main and secondary presses, and wheel events in both directions decide the basic result. The other controls are optional. If you tried an action inside the panel and its row stayed unchanged, mark “Tried, no signal.”
An untouched control has not failed; it has not been checked here yet.
Move and hold
- Pointer movementMove through the test area.Not tried
- Hold and dragHold the main button, move, then release here.Not tried
- Browser double-clickTry two quick, intentional main-button clicks.Not tried
Buttons
- Main buttonUsually left; follows your system mapping.Not tried
- Secondary buttonUsually right.Not tried
- Middle buttonPress the wheel, if your mouse has one.Not tried
Wheel signals
- Vertical +Roll one way over the test area.Not tried
- Vertical −Roll the other way.Not tried
- Horizontal wheelOptional; available on some devices.Not tried
“Observed” means an event reached this tab. “Tried, no signal” is your report that you attempted the action inside the panel. A normal result means this round met the published browser-input rule; repeat intermittent problems under the same conditions.
READ THE RESULT
How to read your mouse test result
The counters describe browser input, not the parts inside your mouse. Read the event order and the state of each control together.
Two events, one action
- 1PRESSMain button
- 2RELEASEMain button
One deliberate click can create both lines. Two lines alone are not evidence of an accidental double-click.
A zero needs a next step
A zero says this page has not received that signal in the current round. If you actually tried that control, repeat inside the test area, check mappings and compare another app or connection before blaming the mouse.
Plus and minus are event signs
Rolling in both directions should give you two kinds of vertical wheel event. A sign is not a physical notch count or a guarantee about the direction a page scrolls.
RETEST WITH ONE CHANGE
Keep two rounds side by side.
Test the same actions twice. Between rounds, change only one condition such as the browser, connection or mouse. Note the change so the two sets of browser observations mean something.
Copy and download use saved rounds when present; otherwise they use the current live round.
Nothing is saved yet. Your two rounds stay in this open page; reloading clears them.
WHEN SOMETHING LOOKS WRONG
Start with the simplest check.
One browser session can show an input pattern. Compare another context before deciding why it happened.
Nothing changes when I use the test area
Move and click inside the dotted area, then check whether the pointer position or any button count changes. If everything stays empty, try the same mouse in another app and check the cable, receiver or battery. If another app responds but this page does not, try a current browser.
One button stays at zero
Press that button inside the test area a few times. Check whether your mouse actually has it and whether system or mouse software has remapped it. Reset and repeat in another browser or with a second mouse. A zero in one tab does not identify a broken switch.
One press seems to cause two actions
Try slow, separate single presses first; the PRESS and RELEASE lines of one action are expected. If an extra press appears, use the deliberate double-click test and then the cause checklist to compare another setting or connection.
Dragging stops before I release
Hold the main button, move across the test area and release inside it. Watch the HELD state: a focus change or release outside this panel interrupts this round. If it also drops in another app, repeat with a different connection or mouse and note what changed.
Scrolling jumps or changes direction
First roll steadily one way inside this panel. For a meaningful direction comparison, use the two-direction scroll wheel test; it records event order and units. The troubleshooting guide walks through settings, app and connection checks.
The pointer feels uneven or slow
Move within this panel to confirm that movement events arrive. Its path is only a browser preview. If your question is how often movement samples reach this browser, use the timed movement-rate test. For the DPI setting, find the active mouse DPI in the device's settings.
CHOOSE YOUR NEXT TASK
Use the test that answers your question.
The basic check above looks for input presence. Each deeper page has a different result.
Make separate presses; inspect their spacing and browser double-click events.
Double-click testCompare both directions in separate phases and review any opposite-sign events.
Scroll wheel testFind the mouse setting and distinguish it from system pointer speed.
Find mouse DPIRun a timed browser movement check; see the sample mode and limits.
Movement-rate testCalculate a hip-fire starting value for CS2, VALORANT or Apex using known DPI.
Sensitivity converterUnderstand which measurement can answer that question; a click counter cannot.
Choose a latency methodBEFORE YOU DECIDE
Your setup changes what this page can see.
No side buttons? The basic check does not require them. Back and Forward are browser controls and are excluded from the checklist.
Left and right swapped? The main and secondary labels follow the button roles reported by your system, which may differ from the physical side you press.
Using a touchpad? Touchpads and other devices can send wheel-like input. This page cannot identify the physical device behind an event.
MEASUREMENT BOUNDARY
These are browser observations.
The test cannot inspect a switch or sensor, identify a hardware cause, measure physical DPI or certify click-to-display latency. A clean round does not rule out an intermittent problem. For the exact inputs and rules each test uses, see how the tests work.