Monitor Test

Eight patterns — solid colours, gradients and a text sample — one click away, Esc to exit.

Checked in a browser on 2026-11-19 · how these tools are tested · runs on your device

How Monitor Test works

Full-screen colour patterns to check for dead pixels, banding, backlight bleed and colour uniformity. The method behind Monitor Test is the single-purpose logic inside leader-test2.js, and this page shows the result with its assumptions in the open.

  • Click Start and the page goes full-screen through eight patterns.
  • Solid red/green/blue reveal stuck pixels; black and white reveal dust and backlight bleed; the grey gradient shows banding.
  • Click or press any key to advance, Esc to exit.

A worked example for Monitor Test

A stuck pixel shows as a bright dot on the black screen; a dead pixel stays black on white. Cleaning the screen first avoids most false alarms.

Repeat the check on a second network: a result that changes with the network is a routing fact, not a fault in your device. That check applies directly to Monitor Test with monitor test.

    When to use Monitor Test — and when not to

    Reasonable uses: Diagnosing a connection; Checking DNS or registration data; Testing hardware in the browser. Monitor Test is deliberately narrow: it does one job and states its assumptions instead of hiding them.

    Diagnostic apps and terminal tools go deeper but need installs or shell access. For a quick lookup or a device test, a page is the lower-friction path. The honest ceiling for Monitor Test: compression artefacts from screen-sharing are not panel faults.

    • Best case for Monitor Test: Diagnosing a connection
    • Also fine with Monitor Test: Checking DNS or registration data
    • Not what Monitor Test is for: compression artefacts from screen-sharing are not panel faults.

    Reading the Monitor Test result

    The output of Monitor Test is a function of the inputs alone — no hidden state and no server.

      Accuracy and limits of Monitor Test

      The method is the single-purpose logic inside leader-test2.js. Monitor Test prints results at the precision its inputs justify, and the limits below are the honest ones:

      • Monitor Test: Compression artefacts from screen-sharing are not panel faults.
      • Phone screens need the same test at native resolution.
      • Pure CSS — no images download.

      Privacy and speed on the Monitor Test page

      The Monitor Test page is a static file plus leader-test2.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.

      Speed follows the build: Monitor Test loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.

        What you get from Monitor Test

        The output of Monitor Test appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the web work finishes the moment the numbers are in.

        Because Monitor Test is built from leader-test2.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.

          Practical notes for Monitor Test

          Judge the panel from your normal viewing distance, not with your nose against the glass: every LCD shows some backlight bleed up close, and most of it is invisible from where you actually sit. Clean the screen with a dry microfibre cloth first — dust is the most common false "dead pixel". Test at native resolution; a scaled resolution can hide or invent artefacts that belong to the scaler, not the panel.

            Questions

            How do I spot a dead pixel?

            On the black screen a dead pixel stays black — it hides; on white or red it shows as a dot. Stuck pixels glow on black.

            What is banding?

            Visible steps instead of a smooth gradient — a panel or colour-depth issue. The grey gradient makes it obvious.

            How accurate is Monitor Test?

            The method is the single-purpose logic inside leader-test2.js. Compression artefacts from screen-sharing are not panel faults.

            What are the limits of Monitor Test?

            Phone screens need the same test at native resolution.

            Is anything uploaded when I use Monitor Test?

            No. Monitor Test runs entirely in the browser tab; nothing is uploaded, stored or logged.

            Can I use Monitor Test offline?

            Yes — Monitor Test keeps working offline once the page has loaded; the whole tool is a local script.

            Device tests

            Keep going

            More web tools