Skip to the tool

Touch Screen Test

Trace touches or pointer movement across the surface to find areas that do not register input consistently.

Touch Screen Test

Trace touches or pointer movement across the surface to find areas that do not register input consistently.

Why this test is useful

Draw slowly across the full test grid. A region that repeatedly fails to register in the same physical place deserves comparison in another app before blaming the digitizer. If the same touch area fails repeatedly in different apps and orientations, the digitizer becomes a more likely cause than the browser page.

Before you start

A reliable way to run the test

  1. Draw slowly across the full test grid. A region that repeatedly fails to register in the same physical place deserves comparison in another app before blaming the digitizer.
  2. Inspect the whole panel in an ordered path from one corner to the other rather than staring only at the center.
  3. When you notice a suspicious point or region, remember its exact position and repeat the same location with another pattern.
  4. If the same touch area fails repeatedly in different apps and orientations, the digitizer becomes a more likely cause than the browser page.

How to read the result

Draw slowly across the full test grid. A region that repeatedly fails to register in the same physical place deserves comparison in another app before blaming the digitizer. If the same touch area fails repeatedly in different apps and orientations, the digitizer becomes a more likely cause than the browser page. If a mark appears in a system screenshot, the cause may be software or rendered content rather than the physical panel. If it stays fixed on the panel but not in the screenshot, hardware becomes more plausible.

What to do next

What this test cannot prove

Do not make a hardware decision from one pattern alone. Repeat the observation with a second pattern or related test. If the same touch area fails repeatedly in different apps and orientations, the digitizer becomes a more likely cause than the browser page. The test itself runs in the browser. Hosting, analytics or advertising can still make ordinary network requests if the site owner enables them.