Tools
Display test
Fullscreen colours for dead and stuck pixels, gradients for banding, gray fields for backlight uniformity, and a live refresh-rate reading taken from your browser's frame timing.
Display test
Pick a pattern, open it fullscreen, and look for dead or stuck pixels, banding and uneven backlight. The refresh rate below is measured from browser frame timing while this tab is open.
Solid colours
Gradients and banding
Uniformity
Black: Look for bright dots (stuck pixels) and backlight glow at the edges.
Fullscreen keys: →/Space next, ← previous, H hide the label, Esc exit. On touch screens, tap to go to the next pattern.
Refresh rate
Browser measurement—Hz
Live, last 2 s
- Median frame time
- —
- Jitter (std dev)
- —
- 99th pct frame
- —
- Average incl. misses
- —
- Missed frames
- —
- Pacing score
- —
· relative / uncalibrated
Last 240 frame times. Dashed line = median, red = missed refresh.
Keep the mouse still and this tab in front. The browser can cap or throttle animation frames (battery saver, background tabs, some multi-monitor setups), so treat this as what the browser delivers, not a certified panel spec.
Screen (reported by browser)
Reading…
How to run a dead pixel check
- Wipe the screen first. Dust and smudges look a lot like a bad pixel on a white field.
- Pick Black and press Open fullscreen. Lit dots on black are stuck pixels.
- Step through White, Red, Green and Blue with the arrow keys or a tap. A dot that stays dark on white is a dead pixel; a dot that is wrong on only one colour points to a single bad subpixel.
- Scan in sections (corners, edges, centre) from a normal sitting distance. On a 27-inch 1440p panel a single pixel is tiny, so a slow, deliberate pass beats a quick glance.
- Found a dot? Use Custom to recheck it on the exact colour where it showed, and take a close-up photo before you contact the seller. Return and warranty rules for pixel faults differ by brand and shop.
Found a stuck (lit) pixel rather than a dead (black) one? The Stuck Pixel Fixer flashes a movable patch over it on a timer. It sometimes frees a stuck subpixel, with no guarantee, and it cannot revive a dead pixel.
Reading the refresh-rate numbers
Browsers usually run animation callbacks once per screen refresh, so timing those callbacks gives a good estimate of the rate your display is running at for this browser window. The big number averages only the frame intervals close to the median, which keeps it stable on fast panels. A healthy 240 Hz monitor should read close to 240, and a 155 Hz panel close to 155. The extra rows tell you how clean the timing was:
- Median frame time — the typical gap between frames (about 4.17 ms at 240 Hz, 6.45 ms at 155 Hz).
- Jitter — how much the gaps vary. Small values are normal; browsers and compositors add some noise.
- Average incl. misses — total frames divided by total time. It drops below the main number when refreshes are missed.
- Missed frames — gaps of 1.5× the median or longer, drawn in red on the chart.
If the reading is lower than the rate you paid for, check the OS setting first (our guide to setting a monitor to 144 Hz covers Windows and the common cable limits), then make sure battery saver is off and the tab is in front. Variable refresh can also change how the desktop is paced; see what VRR and G-Sync are and what VSync actually does.
Banding and uniformity
An 8-bit signal has 256 levels per colour channel, so a full-width black-to-white ramp on a 2560-pixel-wide screen gives each level about ten pixels. Faint steps are normal; thick stripes or colour tints inside a gray ramp are not. The 32 steps pattern checks the other end: every block should be distinct, and if the darkest blocks on the left merge into black, your brightness, gamma or black-level setting is crushing shadows.
Gray 10% in a dim room shows backlight bleed and glow at the edges and corners, which is common on IPS and VA panels to some degree. Gray 50% shows clouding and the dirty-screen effect. For what is typical per panel type, read IPS vs VA for gaming and what an OLED gaming monitor is.
Common questions
What is the difference between a dead pixel and a stuck pixel?
A dead pixel does not light up, so it shows as a black dot on every colour, most clearly on white. A stuck pixel has one or more subpixels stuck on, so it shows as a red, green, blue or white dot, most clearly on black. Stuck pixels sometimes recover; dead pixels usually do not.
How is the refresh rate measured?
The page counts requestAnimationFrame callbacks, which browsers normally run once per display refresh. It averages the frame intervals near the median over the last 2 seconds (or over a 10 second run), so a few missed frames do not drag the number down. It is a browser measurement, not a reading from the monitor itself.
Why does it show 60 Hz on my 144 Hz or 240 Hz monitor?
Usually the monitor is still set to 60 Hz in the operating system, the cable or port cannot carry the higher rate, or the browser is capping animation frames (battery saver, power saving, or a background tab). Check the refresh rate in your display settings first, then retest with the tab in front.
What does the pacing score mean?
It is a relative, uncalibrated 0 to 100 number for how even the frame intervals were in this tab. 100 means every frame arrived on the median interval. Jitter and missed refreshes lower it. It says nothing about panel quality, response time or input lag.
I have two monitors with different refresh rates. Which one is measured?
The browser decides which display drives its frame timing. Move the browser window fully onto the monitor you want to test, reload the page and measure again. If the result still matches the other monitor, test with only one display enabled.
What is banding and how do I spot it?
Banding is when a smooth gradient shows visible stripes instead of a smooth blend. Open the gray ramp fullscreen. A few faint steps are normal on many 8-bit panels; strong, wide stripes point to low bit depth, an aggressive picture mode, or video compression in the signal chain.
Does this page store anything?
No. Patterns are drawn with CSS and the refresh numbers are calculated in your browser. Nothing about your screen is uploaded.
Related tools and guides
- Sensitivity converter — Convert sensitivity between Overwatch, Valorant, CS2, and other titles using documented yaw values.
- cm/360 calculator — Turn mouse DPI and in-game sensitivity into centimeters per 360° turn.
- eDPI calculator — Multiply mouse DPI by in-game sensitivity for a same-game comparison number.
- FOV converter — Convert horizontal and vertical FOV across 4:3, 16:9, 16:10, and 21:9. Includes Overwatch, CS2, and Valorant.
- Frame-time and Hz calculator — Convert FPS to milliseconds, compare that wait to the monitor refresh, and read a 1% low as a frame time.
- Mouse polling-rate tester — Measure how often the browser sees pointer events. Average and max Hz.
- Mouse raw input test — See every mouse report as a dot, spot sensor skips, and check jitter, swipe speed, and acceleration.
- Mouse test — Check mouse buttons, the scroll wheel, double-click chatter, and a pointermove polling-rate reading in the browser.
- Keyboard test — Press keys on a US QWERTY board, then time your typing on real sentences or random letter strings.
- Gamepad test — See every controller button, analog trigger and stick live, check stick drift with a suggested deadzone, and test vibration.
- Stuck pixel fixer — Flash a movable patch over a stuck pixel on a timer.
- Graphics test / What's my GPU — Detect your GPU and run a WebGL2 benchmark.
- Frame-time and Hz calculator — Convert FPS and Hz to milliseconds.
- PPI and viewing-distance calculator — Pixel density from size and resolution.
- Input-lag budget calculator — Frame time, refresh and polling waits added up.
- What a 1440p 240 Hz monitor is for — When the extra refresh helps.
- What monitor response time is — Pixel transitions vs refresh rate.
- Best gaming monitor — Panels and refresh rates worth buying.
Comments
No comments yet. Be the first to share what you think.