Frame Skipping Test

How to use

1. Move the entire browser window onto the monitor you want to inspect.
2. Run the full five-second browser timing preflight with this tab visible and focused.
3. Review the estimated presentation rate, raw P95/P99, long frames, severe stalls, samples, and stability. Repeat if browser timing was irregular.
4. Switch to Photo sequence.
5. Choose the Dark or Light background for the next attempt.
6. Optionally enter Fullscreen before Start so the final sequence geometry can be measured first.
7. Review the current slot count, sequence repeat period, and calculated non-wrap camera exposure window.
8. Set and stabilize a physical phone or camera. A screenshot cannot capture the across-frame sequence.
9. Start the photo sequence.
10. Capture the screen without resizing, rotating, or touching the browser window.
11. Stop the sequence; fullscreen Stop also exits fullscreen.
12. Inspect the photograph yourself and record a current-session observation for the last attempt.

What the result means

• The full browser preflight describes requestAnimationFrame timing in this window. It is context for the photo workflow, not physical panel telemetry or a hardware verdict.
• The sequence lights one fixed slot per browser animation frame and repeats after the displayed number of slots. Exposure longer than one repeat can overlay later cycles onto the same positions.
• The calculated exposure window spans several browser frames but remains below 75% of the estimated sequence repeat. That margin is DeviceMetrik workflow guidance, not a camera or display standard.
• No visible gap means only that no gap was reproduced in this photograph under the captured browser, geometry, display, and camera conditions.
• A possible gap is repeat evidence, not a diagnosis. Confirm a full preflight, keep the same display mode and geometry, and repeat inside the shown exposure range.

Limitations

• Browser timing mode measures rAF presentation intervals, not physical panel refreshes or guaranteed drop counts.
• The camera-assisted sequence is an observation aid; visual gaps may come from the display, OS, browser compositor, camera, or exposure—not a hardware verdict.
• The sequence repeat period is calculated from the browser preflight and current slot geometry; actual display and camera timing can differ.
• Camera rolling shutter, focus, motion, exposure, brightness, and sensor processing can change the photograph.
• The browser cannot inspect the photograph. This page provides no hardware fault identification or guaranteed frame-skip count.
• The page never requests camera permission, reads a file, uploads media, or stores an observation history.

Troubleshooting

The browser preflight stutters or is interrupted

Keep the tab visible and focused, avoid switching windows, close heavy background work, and repeat the five-second preflight.

The photo has too few slots or is too blurred

Use a steady physical camera and keep exposure inside the calculated non-wrap range. Enter Fullscreen before Start if more sequence area is needed, then adjust focus, ISO, or brightness.

The sequence is not visible in a screenshot

Use a physical phone or camera. A screenshot freezes one instant and cannot show the across-frame trail this workflow is designed to capture.

The photo shows a possible gap

Repeat after a full preflight with the same display mode, window placement, and exposure inside the displayed range. Browser, compositor, display, and camera factors can all contribute.

Fullscreen or Wake Lock is unavailable

Those controls depend on browser support and policy. The browser preflight and the fixed sequence still work without either capability.

Related tools

• Refresh Rate Test

  Estimate the refresh rate reaching this browser window from requestAnimationFrame timing. Review median frame interval, timing consistency, interruptions, and repeatable local results without treating browser Hz as panel telemetry.

• FPS Test

  Measure completed browser canvas frames under light, high-load, and paced reference workloads. Compare average FPS, frame-time tails, stalls, and local runs—not a game or GPU benchmark.

• Screen Tearing Test

  Run a fast hard-edge browser motion pattern to look for tear-like horizontal splits, then compare with a clearly labeled simulated tear reference. A normal browser cannot verify VSync, G-SYNC, FreeSync, or game tearing.

FAQ