One fixed coordinate
A dark, bright, or colored point that stays at one panel coordinate belongs in the solid-field and RGB-channel sequence. If it moves with a window or reflection, investigate the source before calling it a panel defect.
Choose the condition of the monitor, open each real tool in order, then return here to mark observations complete. A check mark records progress only; it is not a pass score.
Use this sequence before you settle into calibration or game-specific settings. It begins with point defects, confirms browser-reported geometry, then moves from static panel areas to motion.
Solid black, white, RGB, and grey fields make isolated pixel-sized marks easier to compare.
Run it: Use fullscreen and scan the panel in narrow rows from a centered position. Follow the same coordinate as colors change.
Look for: Note whether the point stays dark, stays bright, changes color, or disappears on a particular channel.
Keep in mind: The browser presents fields; it cannot identify or count physical pixel failures.
Use this follow-up only when a suspect point remains colored instead of consistently dark.
Run it: Compare red, green, blue, cyan, magenta, yellow, white, and black while keeping the coordinate fixed.
Look for: A channel-specific response may be more consistent with a stuck or abnormal subpixel than a fully inactive pixel.
Viewport, Screen API dimensions, and device pixel ratio provide useful context for scaling and test rendering.
Run it: Record the CSS viewport, reported screen size, DPR, orientation, and fullscreen viewport. Compare them with operating-system settings.
Look for: Unexpected CSS dimensions may indicate browser zoom or OS scaling, not a different physical panel resolution.
Keep in mind: These are browser-reported values and derivations, not a direct EDID or panel-native-resolution reading.
This matters for backlit LCD monitors; OLED monitors do not have LCD backlight bleed.
Run it: At a realistic brightness, compare black and near-black from your normal position, then move slightly to test angle dependence.
Look for: A fixed bright edge area behaves differently from IPS glow that changes with viewing angle.
Keep in mind: Camera exposure can exaggerate dark-field brightness, so judge the panel directly.
Neutral steps and ramps expose obvious clipping, tint shifts, and visible tone discontinuities.
Run it: Compare the step grid, smooth ramp, mid-grey field, and focused endpoint ranges without changing settings between patterns.
Look for: Look for missing adjacent steps, colored grey, abrupt bands, or a broad area that differs from the rest.
Keep in mind: A visual pattern cannot measure gamma, Delta E, bit depth, or calibrated color accuracy.
A bounded requestAnimationFrame sample helps check whether browser delivery is near the expected refresh setting.
Run it: Keep the tab visible, let the estimator warm up, and compare its median and recent range with the selected expectation.
Look for: A stable cadence near the expected value is useful browser evidence; large variation may come from load, power policy, or compositing.
Keep in mind: The estimate does not query the monitor electronics or certify variable-refresh operation.
Adjustable light and dark transitions help reveal visible trailing or inverse-looking overshoot.
Run it: Start at a moderate speed and compare original, text, line, dark-on-mid, and light-on-mid patterns.
Look for: Follow the leading and trailing edges for persistent smears, bright coronas, or dark trails.
Keep in mind: This is a visual motion comparison, not a millisecond response-time measurement.
Moving bars, grids, and checkerboards provide a reference for discontinuities during browser animation.
Run it: Compare patterns with the frame marker on and off, then repeat in the content or game where the symptom occurred.
Look for: A horizontal discontinuity may be visible, but browser compositing can synchronize the test and hide it.
Keep in mind: A clean pass cannot certify V-Sync, VRR, or an operating range.
This shorter triage sequence emphasizes persistent marks and age-related panel behavior before fine tone or motion work. Choose LCD- or OLED-specific follow-ups based on the actual panel technology.
A concise color cycle checks for fixed dark, bright, and colored points.
Run it: Scan black, white, red, green, blue, and mid-grey, watching any suspect coordinate across every field.
Look for: Separate a panel-coordinate mark from dust, reflections, or content that moves with the page.
Grey and RGB fields can expose broad non-uniform areas that busy desktop content conceals.
Run it: Compare low, middle, and bright greys from the normal viewing position before changing angle.
Look for: Watch for fixed bands, clouds, edge falloff, or color tint that remains in the same panel area.
Used OLED and backlit LCD panels need different dark-field and persistence checks.
Run it: Confirm the panel technology from reliable model documentation, then open the matching OLED or LCD workflow.
Look for: OLED image retention and differential aging are not LCD edge bleed; do not label one as the other.
Browser dimensions help catch zoom or scaling that could soften patterns during a quick inspection.
Run it: Compare viewport, reported screen dimensions, and DPR with the connected-computer settings.
Look for: Treat mismatches as configuration clues rather than proof of a replaced or incorrect panel.
A smooth browser gradient makes abrupt stripes or processing artifacts easier to notice.
Run it: Compare neutral and colored gradients in the same browser and monitor mode you plan to use.
Look for: Separate stable bands from temporal noise, compression in other content, and deliberate stepped mode.
A short light/dark edge comparison can reveal distracting trails before purchase or handoff.
Run it: Use the advertised refresh setting if available and compare two speeds without chasing an artificial score.
Look for: Look for trails that remain conspicuous at your normal viewing distance.
Keep in mind: Overdrive settings and temperature can change the appearance.
Desktop display workflow
This monitor screen test connects pixel fields, browser display information, panel-area patterns, and motion tools in a deliberate order. The new-monitor route is broader; the used monitor route emphasizes persistent defects and wear before optional fine checks.
Choose evidence by symptom
Do not convert every visible irregularity into a “dead pixel.” Its size and behavior determine the next useful check.
A dark, bright, or colored point that stays at one panel coordinate belongs in the solid-field and RGB-channel sequence. If it moves with a window or reflection, investigate the source before calling it a panel defect.
Broad non-uniformity needs black and grey fields plus a stable viewing position. LCD edge bleed, angle-dependent IPS glow, OLED low-grey variation, and Mini LED zone behavior are not interchangeable.
Use moving edges after confirming the expected operating-system refresh setting. Browser cadence, LCD transitions, overdrive, OLED sample-and-hold blur, sync, and game rendering can produce different symptoms.
New versus used
Establish a baseline before calibration and application-specific modes. Finish the full pixel, geometry, uniformity, tone, cadence, and moving-edge sequence, then repeat only the suspicious pattern under normal working conditions.
If you need to discuss an observation with a retailer or manufacturer, record the model settings, input path, brightness, room light, field, and panel coordinate. Warranty policies vary; this site does not set a universal acceptable-pixel or uniformity threshold.
Begin with the faults that busy content can hide: fixed points, broad grey variation, persistent shapes, and fixed dark-field areas. Confirm whether the display is LCD, OLED, or a local-dimming LCD before naming a symptom or choosing a follow-up.
Resolution information is configuration context, not evidence that a panel is original. The browser cannot authenticate a replacement panel, read operating hours, or inspect compensation-cycle history.
Panel-aware interpretation
A backlit LCD passes light through a liquid-crystal layer. IPS, VA, and TN implementations differ in viewing-angle and transition behavior, so change your head position before treating a corner glow as fixed bleed. Mini LED is an LCD backlight system with many controllable areas; bright objects on black can reveal blooming or zone transitions, but a browser pattern cannot count physical zones.
OLED pixels emit their own light. That removes LCD backlight bleed, but introduces a different reason to inspect low grey, retention-like outlines, and tint. Temporary image retention and permanent differential aging may look similar in one monitor screen test session, and the site cannot read the panel’s maintenance or compensation status.
Record the pattern, location, viewing distance, brightness, picture mode, input, and whether the mark changes with angle. A useful note says “fixed pale area in the lower-left corner on 5% and 10% grey from the centered position.” A single percentage score would hide those distinctions and imply measurement the browser did not make.