You are standing in front of a screen you do not trust. Here is a browser, and here is what it can tell you.
Measured, not asked for. The refresh figure is what the browser is actually being given over about a second of frames — which is the honest number, because a display can report 60 and deliver 48.
These go full screen and are drawn at true device pixels, so the one-pixel checkerboard is genuinely one pixel. If it shimmers or turns grey, something between the browser and the glass is scaling.
Arrow keys cycle, Esc comes back. On a second screen,
drag this window there first.
It cannot see the cable. It does not know the sink's native resolution, only the box it has been handed; it cannot read the EDID, so it cannot tell you the panel is 1920×1200 while something upstream is sending 1080p. It cannot measure the latency between this screen and another one, and it will not report HDR honestly on every platform.
For those you need something photographed, or something on the wire. The downloadable cards carry a frame counter and a latency clock for exactly that, and where latency hides is the long version.
Because this is the same idea. Deckboy generates its patterns live at whatever raster and refresh the output is really running, rather than stretching a file at one — and a stretched test pattern tests the stretch. This page does that trick in a browser, for the ten minutes before doors when installing anything is not on the table.
Deckboy is a free, open-source cue player for live video. If the screen turns out to be fine and the problem is the playback, that is the part it is for.