KlyveroTouch Screen Test
Map touched display regions.
Map touched display regions.
Preparing the test workspace…
Browser-reported contacts/events only; no digitizer diagnosis or physical latency
How to use this test
- Visit each grid cell with a finger while capture is active.
- Move your fingers inside the surface and try the requested gestures.
- Review only the contacts and browser events observed; press Stop when finished.
Checks included in this tool
Multi-Touch Test
Observe simultaneous browser-reported touch contacts. The observed peak is a lower bound for contacts delivered to this page. Browser gestures, OS behavior and contact placement can limit the number.
- Place two or more fingers on the active surface and compare the reported peak.
- Move your fingers inside the surface and try the requested gestures.
- Review only the contacts and browser events observed; press Stop when finished.
Observed concurrent contacts are a lower bound, not hardware maximum
Touch Response Test
Inspect browser touch response feedback. This interval starts at the browser event timestamp. It does not include all sensor, operating-system or display latency and cannot certify physical touch response.
- Tap and drag inside the active surface while reading dispatch-to-handler timing.
- Move your fingers inside the surface and try the requested gestures.
- Review only the contacts and browser events observed; press Stop when finished.
Browser event-handler to next animation-callback interval only; cannot measure physical touch latency or render completion
Swipe Test
Exercise swipe tap and long press behavior. Gesture labels use documented movement and duration thresholds. A gesture interpretation is not a claim about hardware accuracy.
- Try a short tap, a long press and a directional swipe inside the surface.
- Move your fingers inside the surface and try the requested gestures.
- Review only the contacts and browser events observed; press Stop when finished.
Browser-reported contacts/events only; no digitizer diagnosis or physical latency
Touch Drawing Test
Inspect continuous contact paths and gaps. Gaps may reflect browser sampling, pointer cancellation or contact loss. The drawing does not automatically identify a digitizer fault.
- Draw continuous lines across the surface and inspect the actual received path.
- Move your fingers inside the surface and try the requested gestures.
- Review only the contacts and browser events observed; press Stop when finished.
Visible discontinuities can reflect browser sampling; no digitizer fault diagnosis
How it works & what results mean
How the test works
Map touched display regions. It uses Pointer Events; Touch Events fallback after verification. The workspace shows observations from this browser or asks for your own confirmation.
Understanding your result
Visited cells show delivered contact locations. An unvisited cell is unassessed, not automatically a broken touchscreen region. Browser-reported contacts/events only; no digitizer diagnosis or physical latency Missing data, blocked permission and an operation that could not run are shown separately. None establishes a hardware fault.
What you can inspect
Touch Screen Test
Browser-reported contacts/events only; no digitizer diagnosis or physical latency
Touch Grid Test
Browser-reported contacts/events only; no digitizer diagnosis or physical latency
Keep checking
Related tests
About this test & common questions
how to test touch screen dead zones online?
This touch screen test lets you draw over a grid and inspect touch points. The multi touch test shows simultaneous contacts received by the browser.
can a browser test every touch sensor?
Coverage reflects the touch events this page receives; operating system gestures and browser limits can hide contacts.