What can an automatic monitor test actually measure?

Before you start

An automatic monitor test can mean showing patterns in sequence or deciding that the hardware is healthy without observation. A web page can do the first, but not reliably diagnose every physical defect. The browser does not directly read which panel pixel fails to emit light or how bright a corner looks to you. MonitorTest’s quick checks and report tools therefore separate browser-derived values from human observations.

Controlled comparison

Reported display size, viewport size and pixel ratio can be affected by scaling and zoom. Animation timing provides an approximate refresh indicator; keep the tab in front, use the same screen and record heavy background load. Compare the estimate with the selected operating-system mode rather than presenting them as identical measurements. PPI needs a physical diagonal: viewport width cannot supply that measurement reliably.

How to interpret the result

Pixel defects, uneven illumination and ghosting require viewing a pattern and recording what is seen, not seen or uncertain. Screen-sharing permission does not remove this limitation: it captures display content, not a photograph of the physical panel’s light output. Clicking a colour-changing demo also does not measure total input lag. Instrumental brightness, colour-error and response-time results require suitable measurement equipment.

What to record

A useful result list labels its evidence: browser estimate, user observation, skipped check or inadequate conditions. “No symptom observed” is not a hardware health certificate. Include date, settings and repeat steps, plus the relevant guide. Flashing patterns should never start without the user’s informed choice. The value is a consistent record of checks, not an invented automatic health score.

Sources and scope

• MDN: requestAnimationFrame
• MDN: Screen Capture API