Screen test & benchmark
Screen tests
55 checks · one click = fullscreen · Esc exits · all tests →Motion & measurement
each opens its own page with the tool up topPerformance benchmark
- 1—
- 2—
- 3—
- 4—
- 5—
- 6—
- 7—
- 8—
- 9—
- 10—
- you—run the benchmark — your score slots in here
This display
live| Resolution | — |
| Viewport | — |
| Pixel ratio | — |
| Refresh rate | — |
| Color depth | — |
| Color gamut | — |
| HDR | — |
| GPU | — |
| CPU cores | — |
| Memory | — |
| Platform | — |
| Browser | — |
| Form factor | — |
| Power | — |
How do I test my screen for dead pixels?
Run the dead pixel test. It fills the screen with nine solid colors, one at a time — a defective pixel shows up as a dot that doesn't match its background. Wipe the screen first (dust is the classic false alarm), check the corners, and give it a minute per panel. It works on monitors, laptops, phones and TVs.
Can a dead pixel be fixed?
A truly dead pixel — black on every color — almost never comes back. A stuck subpixel (red, green or blue dot) sometimes recovers after rapid color cycling on that spot, though the evidence is anecdotal. If it survives a few sessions over a couple of days, check the manufacturer's pixel policy: many panels qualify for warranty replacement.
What's the difference between dead, stuck, and hot pixels?
A dead pixel gets no signal and stays black on every bright color. A stuck pixel has one subpixel frozen on, so it glows red, green or blue against colors that should exclude it. A hot pixel has all three stuck on and shows white against black. Which test color reveals the defect tells you which kind you have — the test page has the full table.
What is screen banding, and is it a defect?
Banding is when a smooth gradient renders as visible stripes instead of a continuous sweep. Some banding is normal on 8-bit panels showing near-identical shades; heavy banding on gentle gradients points at the panel, a bad cable, or aggressive image processing. The gradient test above makes it easy to see — grayscale, viewed slowly, is the harshest judge.
What does the benchmark score mean?
The score is the heaviest particle workload your device holds at a steady frame rate, measured on frame-time percentiles and normalized per scene — higher is faster, and the tier (Entry / Balanced / Fast / Extreme) gives it a plain-language label. It's a browser workload score, honest about being one: your GPU, CPU, browser and thermals all count. The methodology is public.
Why does my benchmark score change between runs?
Because your device changes between runs. Thermal throttling, battery-saver modes, background apps and browser updates all move the result — a few percent of run-to-run noise is normal, and a big drop usually means heat. Plug in, close heavy apps, and let a warm machine cool down; the benchmark flags runs where it detects mid-run slowdown.
Does this site upload anything?
The screen tests run entirely on your device and send nothing. Finishing a scored benchmark can share one anonymous sample — score plus coarse hardware class — for the public hardware stats; the start card shows exactly what before anything runs, and one checkbox turns it off. Details in the privacy policy.
Does it work on phones, tablets and TVs?
Anything with a modern browser works. On touch screens, tap to advance and use a two-finger tap or the close button to exit fullscreen. For a TV, open the site in its built-in browser or mirror from a laptop — mirroring still exercises the TV's own pixels, so the dead pixel test remains valid. The scored benchmark needs WebGL2, which every current phone and desktop browser ships.
Articles
all →Changelog
all →- 2.15.0 — Twenty-one new shaders, sliders on every one, and a question before anything flashes2026-09-11
- 2.13.0 — A score history you can read, and articles that fill their page2026-09-10
- 2.14.0 — Five shaders join the gallery, and two of them are test patterns2026-09-10
- 2.10.0 — Every field, one click from the homepage2026-09-03