Touch Screen Test
Choose the coverage grid
Tap or drag through every square. A denser grid can reveal a smaller missed area, but takes longer to complete.
Your touch path stays in this browser tab
Grid settings, visited squares and sampled pointer paths are handled locally in this browser tab. They are not sent through Livewire, placed in URLs or shared with external APIs. Normal page requests still occur between funnel steps.
Use this touch screen test to check whether your browser receives pointer events across a grid of screen areas. Select a 5 × 5, 7 × 7 or 9 × 9 grid, then tap or drag through every square. The test records which grid areas received an event, the highest number of simultaneous touches it observed and any squares still missed. The diagnostic stays in the current browser tab and does not upload your touch path.
How to test a touch screen
-
1
Choose a grid
Use a coarse grid for a quick check, or a denser 9 × 9 grid when you want to narrow down a missed area.
-
2
Tap and drag
Tap separate squares and draw slowly across rows and columns. Try two fingers at once if you want to observe multi-touch input.
-
3
Review the result
Check coverage and the list of missed squares, then repeat the test before deciding that there is a device problem.
What this browser test measures
The grid listens for Pointer Events, the browser event model that can represent a finger, pen or mouse. When an input passes through a grid square, that square changes colour. The result is simple: a visited square received an event during this browser session; an unvisited square did not.
The multi-touch number is the highest count of active pointers the page observed at once. It can help confirm that a browser saw two or more fingers together, but it is not a formal device specification or a benchmark of maximum touch capacity.
| Result | What it means | Sensible next step |
|---|---|---|
| Every square visited | The page received events across this test grid | Repeat a few strokes if you need more confidence |
| One or more missed squares | This browser session did not receive an event there | Clean and dry the screen, then repeat slowly |
| Low multi-touch count | The page observed fewer simultaneous pointers than expected | Retry with bare fingers and no palm contact |
| No Pointer Events support | The current browser cannot run this check | Try a current browser on the device you want to test |
Use the result carefully
A grid is not a hardware diagnosis. A square can be missed because a finger moved too quickly, the page was scrolled, a screen protector affected contact, the browser handled a gesture, or the device has a genuine input issue. Repeat the same area several times, use the device in its normal orientation and compare the result with another app before contacting support.
This test cannot measure display pixels, touch pressure, stylus calibration, operating-system gesture settings, input latency or faults outside the browser. It also does not identify the physical location of a damaged component. It is a practical first check for browser-visible touch coverage, not a replacement for the manufacturer’s diagnostic tools.
Good testing habits
- Clean and dry the display. Moisture, debris and some gloves can alter touch recognition.
- Use deliberate strokes. Tap isolated squares first, then trace horizontal and vertical paths without rushing.
- Try more than one contact. Two fingers together can reveal whether the browser receives concurrent pointer events.
- Test edges in full screen. The full-screen option stretches the grid over the whole display, so squares along the edges and corners are easier to reach.
- Retest a missed area. A repeated pattern matters more than one missed square on a fast pass.
- Protect your privacy. The grid and sampled path are kept only in the current browser tab; no account, location, image or touch data is uploaded.
If a clear area remains consistently missed in this page and other apps, record the device model, operating-system version and the repeatable behaviour before asking the manufacturer, retailer or repair provider for help.
Frequently Asked Questions
No. It only shows whether this browser received Pointer Events in each grid square during this session. Repeat the area slowly and compare with another app before treating it as a hardware issue.
Yes. Touch the grid with two or more fingers at once. The page reports the highest number of active pointers it observed, which can differ from the device’s advertised maximum.
The pointer may have moved too fast, passed between squares, been interpreted as a browser gesture or not reached the page. Clean and dry the screen, then retry that area with a slow tap and drag.
No. The grid, visited squares and sampled pointer path stay in browser storage for the current tab so the multi-step flow can continue. They are not sent through Livewire, placed in the URL or shared with external APIs.
Modern browsers use Pointer Events for touch, pen and mouse input. A mouse or pen can verify that the page is receiving pointer input, but it does not substitute for testing the device with a finger.
Related Tools
Mouse Tester
Test your mouse buttons, wheel scrolling, pointer movement and double-click timing in the browser. See event logs and movement samples without uploads.
Competition Bracket Maker
Build a seeded or shuffled single-elimination bracket for 2–32 teams or players, assign automatic byes, advance winners, copy and print it.
Fancy Serial Number Checker
Check US-style currency serial numbers for fancy patterns like radars, ladders, repeaters, low numbers and star notes.
Metronome
Practice with a precise online metronome. Set BPM, meter, accent and subdivisions, then play a steady browser click locally.
Guitar Tuner
Tune a guitar in your browser with microphone pitch detection, cents offset, standard and alternate tunings, and no audio upload.
Baby Name Generator
Generate baby name ideas filtered by gender, origin, first letter, length and style. Fresh lists every click; save favourites to compare.