Quick answer
What this guide helps you determine
Learn why event frequency and movement sensitivity describe different parts of pointer behavior.
Begin with the observable browser result, repeat it under the same conditions, and change one connection, setting or application at a time. A browser result narrows likely causes but does not certify hardware or decide a repair.
Scope of this check
Polling rate and DPI describe different parts of pointer input. Polling rate concerns how often reports arrive; DPI describes sensor counts per inch of physical travel. Operating-system pointer speed and in-game sensitivity scale the resulting movement without changing the sensor’s physical DPI setting.
Step-by-step method
- Use the polling estimator with a steady motion to examine event intervals. Then compare pointer distance only after keeping the same physical movement, operating-system acceleration and application sensitivity.
- Change one device setting at a time in trusted vendor software. Raising DPI should increase cursor movement for the same physical distance; raising report rate should mainly alter update timing and load, not the distance itself.
- Return to a comfortable configuration and verify it in the actual application. A browser has no reliable physical ruler or access to every firmware value, so it cannot determine exact DPI without a measured travel reference.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Polling rate concerns timing
- DPI concerns movement resolution
- In-game sensitivity changes neither hardware setting
Open Mouse Polling Rate Estimator
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| Cursor travels farther after a DPI change | Sensor sensitivity or software scaling changed. | Confirm acceleration and application sensitivity stayed fixed. |
| Event intervals change but travel does not | Polling/report timing changed while sensitivity remained similar. | Evaluate stability in the target application. |
| Only in-game movement changes | Game sensitivity or raw-input behavior is responsible. | Review that game’s input settings. |
Common mistakes to avoid
- Do not call cursor speed a direct DPI measurement.
- Do not change DPI, acceleration and game sensitivity together.
- Do not assume the highest available settings are optimal for every system.
Build evidence another person can use
Write down the exact action, visible result and whether it repeats. Include the browser family, operating-system family, connection type and the single comparison that changed the result. Quote the observation directly—for example, “Cursor travels farther after a DPI change”—then add where it occurred and which comparison changed it.
Change one condition per comparison and return settings that have no effect. Follow model-specific manufacturer instructions before firmware changes, cleaning, disassembly or warranty action.
When to seek qualified support
If the same problem remains in multiple applications and on another compatible connection or computer, collect the repeatable observations and contact the manufacturer or a qualified technician. Stop using equipment that is physically damaged, unusually hot, wet, sparking or unsafe. Device Test Bench cannot inspect electrical condition or make a repair decision.
Privacy during testing
Our public tests process key events, pointer values, media streams and controller input locally. Do not send private recordings, complete typed text or device identifiers when asking for help. A short description of the behavior, browser and page URL is normally enough.
Questions readers ask
Can this site measure exact DPI?
No. Exact DPI needs reliable physical travel and controlled pointer scaling; the site explains and compares browser-visible behavior.
Does changing Windows pointer speed change hardware DPI?
No. It changes software scaling; the sensor’s configured DPI remains a separate setting.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.