Multi-Touch Test
See how many simultaneous touch points your device reports, compared with navigator.maxTouchPoints.
Touch and drag here with one or more fingers.
Pressure and contact size are shown only where your device and browser expose them; many mice and trackpads report a fixed pressure of 0.5.
How this test works
Input tests listen to the browser’s standard event streams — KeyboardEvent for keys, PointerEvent for mouse, touch and stylus — while the test area has focus. Each event carries rich data such as key codes, button masks, coordinates, pressure and high-resolution timestamps.
Rate and timing tests measure the interval between events. Where the browser exposes them, we use pointerrawupdate and getCoalescedEvents to see events at a finer granularity than one per frame, then compute a distribution rather than a single number.
Events are captured only inside the test area, so your normal browser and operating-system shortcuts keep working everywhere else on the page.
How to use it
- Click or tap inside the test area to give it focus.
- Press keys, click buttons, scroll, or move/drag as the test instructs.
- Watch the live visualization highlight exactly what the browser received.
- For rate tests, move or click continuously so enough samples are collected.
- Use Reset to clear the state and start a fresh measurement.
What it detects
- Which keys, buttons, and touch points register in this browser session
- Scroll direction and wheel deltas, double-click intervals, and movement paths
- A browser-observed estimate of event rate (for polling-rate tests)
- The maximum number of simultaneous keys or touches the browser reports
What it can’t detect
- A device’s true hardware polling rate, DPI, or input latency
- Keys and shortcuts the operating system intercepts before the browser sees them
- Whether a fault is in the device, the driver, or OS settings like key repeat and acceleration
Troubleshooting
| Symptom | What to do |
|---|---|
| A key doesn’t register | Some media and system keys are handled by the OS and never reach the browser. Try another key or check your keyboard layout. |
| Scroll seems reversed | That’s an OS setting (natural scrolling); the test reports the direction the browser received. |
| Event rate reads low | Move continuously, keep the tab focused, and disable power saving — the browser observes events after OS processing. |
| Right-click menu appears | The context menu is only suppressed inside the dedicated test pad; use that area for button tests. |
FAQ
Why isn’t a key registering?
Certain keys (like some media or system keys) are handled by the OS and never reach the browser. Try a different key or check your layout.
Is my typing recorded?
No. Key and pointer events are processed locally to drive the visualization and never leave your device.
Does this work offline?
Yes, input tests work offline once the page has loaded.
Why is my 1000 Hz mouse showing less?
The browser observes events after the OS and compositor, so the measured rate can be lower than the mouse’s rated polling rate.
Can I test a keyboard’s full anti-ghosting?
Only what the browser reports in this session. Some combinations are limited by the browser or OS, so this isn’t a universal hardware certification.
Do these tests work with a trackpad or touchscreen?
Yes. Pointer events cover mouse, trackpad, touch and stylus, though exposed details like pressure vary by device.