Mouse Drift Test
Place your mouse on a stable surface and take your hand off completely. The test runs for 15 seconds and counts every pointer movement the browser reports — sensor noise, surface vibration, or background processes moving the cursor. The browser cannot distinguish the cause; it only reports what it observed. Runs locally, no data leaves your device.
Run the test
Place your mouse on a stable surface and take your hand off completely. The test counts any pointer movement the browser reports over 15 seconds — sensor noise, surface vibration, or background processes. A browser cannot distinguish the cause; it only reports what it observed.
Keep the mouse still. Do not touch it, the desk, or the mousepad during the test.
Hand off the mouse. Test runs for 15 seconds.
Hand off the mouse. Do not bump the desk.
What this measures
- Total movement events the browser reported while the mouse was untouched.
- Total absolute movement in pixels (sum of |dx| + |dy| across all events, including coalesced events where available).
- Largest single-event movement in pixels.
- Movement events per second (average rate over the 15-second window).
What this cannot measure
- Whether movement comes from sensor fault, surface vibration, or OS/background processes moving the cursor — the browser cannot tell which.
- Any movement that occurs while the mouse is being touched — this test only measures the untouched state.
- Absolute sensor quality or hardware defect classification — elevated counts are a signal to investigate, not a verdict.
- Drift on a specific axis separately — the test sums absolute X and Y movement.
How to get a steady reading
- Place the mouse on a clean, stable surface and remove your hand completely.
- Do not bump the desk, mousepad, or mouse during the 15-second run.
- Close unnecessary background applications that might move the cursor programmatically.
- Wait for the full 15 seconds — the test auto-stops and shows results.
- Repeat on a different surface (mousepad, desk, paper) to compare — surface texture is a common cause of elevated counts.
How to read the results
| Metric | What it means |
|---|---|
| Events counted | Total pointermove events the browser delivered (including coalesced events where supported). Each event represents a reported movement sample. |
| Total movement (px) | Sum of absolute X and Y movement across all events. A single event moving 3 px right and 2 px down adds 5 px to this total. |
| Largest single event (px) | The maximum |dx| + |dy| in any one reported event. Helps distinguish constant jitter from occasional jumps. |
| Events per second | Average event rate over the 15-second test. Higher rates with low total px suggest high-frequency jitter; lower rates with high px suggest occasional large jumps. |
What drift readings mean — honestly
A perfect mouse on a perfectly stable surface would report zero events. In practice, almost every mouse reports some movement when untouched. Tiny counts (under 10 events in 15 seconds) are normal sensor noise — the sensor detects microscopic vibration or thermal noise.
Elevated counts do not automatically mean a faulty sensor. Common causes include: a slightly uneven or vibrating desk, a textured mousepad that amplifies micro-vibration, a wireless receiver too close to other 2.4 GHz devices, or a background process (accessibility software, remote desktop, macro tool) that programmatically moves the cursor. The browser reports the movement; it has no access to the cause.
If you see elevated counts, the first step is to repeat the test on a different surface. A glass desk, a hard mousepad, a piece of paper — each changes the vibration coupling. If the count drops dramatically, the surface was the culprit. If it stays high across surfaces, try a different USB port, disable background utilities, or test the mouse on another computer.
Surfaces and sensor noise
Optical and laser sensors illuminate the surface and track pattern displacement. A highly reflective or perfectly uniform surface (glass, glossy plastic) can cause the sensor to lose tracking or report phantom movement. A heavily textured surface (cloth pad with deep weave) can make the sensor report vibration from desk resonance.
Hard pads with a fine, consistent texture usually give the lowest drift counts. Soft cloth pads vary — some are excellent, others amplify micro-movement. If you game on a cloth pad and see elevated drift, test on a hard surface for comparison.
Wireless mice add receiver placement to the equation. A receiver behind the monitor or near a USB 3.0 hub can pick up interference that manifests as cursor drift. Moving the receiver to a front USB port or a USB extension cable often helps.
When to worry — gently
Under 10 events / 15 s: Normal. Typical sensor noise floor.
10–50 events / 15 s: Low. Likely surface vibration or minor interference. Try another surface first.
50–200 events / 15 s: Elevated. Check surface, receiver placement, and background software. If persistent across surfaces and computers, the sensor may be degrading.
Over 200 events / 15 s: High. Strong indicator of a surface issue, significant interference, or a sensor problem. The cursor may visibly drift on screen.
This test does not declare your mouse "good" or "bad." It gives you a number and the context to interpret it. A mouse with 200 events on a glass desk may be perfect on a cloth pad.
Privacy
This test runs entirely in your browser tab. No movement data is sent anywhere. No history is stored. Refreshing the page clears the session. You can verify this in DevTools: open the Network tab, run the test, and confirm no requests fire.
Frequently asked questions
What is a mouse drift test?
A drift test measures how much the cursor moves on its own when you are not touching the mouse. You place the mouse on a stable surface, take your hand off, and the test counts every pointer movement the browser reports for 15 seconds. It reveals sensor noise, surface vibration, or background processes moving the cursor.
My mouse reports movement while untouched — is it broken?
Not necessarily. Tiny counts (under 10 events in 15 seconds) are normal sensor noise. Higher counts often come from surface vibration (desk resonance, textured pad), wireless interference (receiver near USB 3.0 devices), or background software (accessibility tools, remote desktop, macro apps) moving the cursor. Test on a different surface first — if the count drops, the surface was the cause. If it stays high across surfaces and computers, the sensor may be degrading.
Does the test work on any surface?
Yes, but the surface affects the result. Glass and glossy surfaces can cause tracking loss or phantom movement. Hard pads with fine texture usually give the lowest counts. Soft cloth pads vary. For a fair comparison, test the same mouse on different surfaces — the difference tells you how much the surface contributes.
Does it store anything?
No. The test runs entirely in your browser tab. No data is sent to any server. No history is saved. Refreshing the page clears the session completely.
Related tests
Mouse Polling Rate Test
Live Hz, stability graph, and variation — browser-observed, not a hardware measurement.
Mouse Click & Double-Click Test
Five-button registration, press counts, and possible-bounce detection — no fault verdict.
Mouse Scroll Test
Wheel direction, delta values, step totals, and deltaMode unit — compare like with like.
Mouse Tests Hub
Overview of all mouse tests: polling rate, click/double-click, scroll, drift, and reaction time.
Last reviewed 2026-10-12