Phase 2, step 1 — find out what this device can actually do.
(no JavaScript at all)
Tap Run the test, then get as many fingers as you can on the + and − buttons at once — ideally six or seven, held down — for the full 15 seconds. This is the exact hot-path design the real app will use, so its numbers are the ones that matter.
This run is settling a specific question. The device advertises 5 touch points but a previous run registered 7 — meaning it either quietly supports more than it admits (fine) or presses are getting stuck (a real bug). Two things to do while the timer runs:
1. Put more than five fingers down at once and watch the
fingers counter — see how high it actually goes.
2. Lift every finger off with a few seconds still on the clock and
check that the counter drops back to 0. This is the part that
matters: if it sticks above zero once you're not touching the screen,
releases are being lost.
Rendered by React with real Tailwind v4 classes. check.js reads the computed styles off it — if this box is unstyled or invisible, Tailwind v4 does not work on this device.
Only needed if the send above failed.