Mouse Jitter Test

Draw a deliberate straight or curved path, then review distance, straight-line efficiency, average turn, sample cadence, and a browser-local trace without uploading pointer data.

Press and draw a deliberate path

A straight line is useful for repeatability checks.

0Samples

0 pxPath distance

—Straight-line efficiency

—Avg direction change

—Median event Hz

—P10–P90 Hz

—Endpoint distance

—Pointer type

How to read the trace

Straight-line efficiency compares endpoint distance with the full travelled path. A deliberate straight sweep closer to 100% is straighter, but your hand motion and OS processing matter.

Average direction change summarizes how sharply successive segments turn. It is not a direct sensor-jitter percentage.

Event cadence is included so you can tell whether an uneven trace coincided with sparse browser pointer events.

Use repeated passes under the same conditions before comparing setups. This browser trace cannot isolate sensor noise from hand movement, acceleration, smoothing, display scaling, or event coalescing.

What the browser can measure

Start with a functional check, measure only what the browser can actually expose, then retest after one change.

ConnectChoose the actual browser-visible device or grant permission when required.

TestConfirm basic signal, input, output, preview or display behavior.

MeasureUse browser-exposed levels, timing, resolution, FPS, axes or event data.

DiagnoseCompare the symptom with the specific diagnostic instead of relying on one number.

RetestRepeat after changing the device, cable, permission, browser or system setting.

Pre-call Mic Webcam Keyboard Mouse Gamepad Display Permissions

Browser boundary
These tools observe browser APIs and local media/event streams. They cannot certify hardware condition, bypass denied permissions, or expose measurements the browser/OS does not provide.

Browser-local does not mean laboratory measurement

These pages can report Web API data such as events, stream settings, frame timing and audio samples. They do not certify hardware condition or bypass browser and operating-system limits.

Pointer-path repeatability gains line-deviation and event-delivery diagnostics

Alongside path efficiency and direction change, v258 reports RMS/max deviation from the start-to-end chord and browser event timing. The result still cannot isolate sensor noise from hand movement or OS processing.

Browser-observed input is not raw hardware telemetry

Mouse Jitter Test measures events after they have passed through the device firmware, operating system, browser, event loop, and page. Sampling rate, background load, power-saving behavior, accessibility settings, acceleration, browser coalescing, and display refresh can therefore influence what the page observes.

How to make the test more useful

Repeat the same action several times, close heavy background work, keep the browser focused, and compare patterns rather than treating one sample as a hardware specification. A missing event can indicate rollover or browser behavior without proving an electrical keyboard fault; timing variation can indicate scheduling noise without proving sensor jitter. For warranty, competitive-latency, or hardware diagnostics, confirm findings with the device vendor’s tools or a lower-level measurement method.