Check browser animation intervals for timing gaps and uneven frame delivery. Compare repeated runs and understand the limits of an online frame skipping test.
Detects dropped or skipped frames using requestAnimationFrame timestamp deltas. Any frame whose delta exceeds 1.5× the expected interval (based on your display refresh rate) is counted as a stutter. A moving bar gives visual confirmation — jitter or hitching means the browser or GPU is missing frames.
Frame skipping detector
—Detected Hz
0Frames rendered
0Skipped frames
—Worst delta (ms)
—Jitter (stddev)
Click "Start test". The first 1 second is used to calibrate your refresh rate, then frame skips are counted.
Moving bar (visual confirmation)
A bar moves left-to-right at constant pixels-per-frame. Jitter or hitching in the bar = skipped frames. Smooth motion = stable refresh rate.
Stutter log
Was this tool helpful?Rate Frame Skipping Test:5.0(3 ratings)Thanks for rating!
Frame Skipping Test is a free, browser-based screen testing tool that lets you detects dropped frames using requestAnimationFrame timestamp analysis.
Cost: Free, no signup
Install: None — runs in the browser
Privacy: Runs locally, no uploads
Platforms: Windows, macOS, Linux, Android, iOS
Time: Under a minute
Online Frame Skipping Test for Browser Timing
Use this online frame skipping test to compare animation-callback intervals and look for timing gaps in the current browser session. The page estimates an expected interval and flags larger departures while showing a moving reference. A flag describes browser timing under those conditions; it is not direct proof that a monitor physically omitted a frame or that a particular component is faulty.
Why Browsers Skip Frames
Even on fast hardware, browsers skip frames for several reasons: JavaScript garbage collection stalling the main thread for 20+ ms, layout thrashing from extensions mutating the DOM, GPU compositing falling behind on scroll or animation, hardware acceleration being disabled, or thermal throttling on laptops. Battery-saver profiles often downclock the GPU and cause occasional skips. A repeating timing gap does not identify its cause by itself. Compare a clean browser session, foreground focus, power settings and workload one at a time before attributing it to an extension, driver or hardware component.
Frame Skipping vs FPS
An average frame rate can hide uneven intervals. Review the timing distribution, worst observed gap and variability rather than a single average. These browser-side observations can help make a controlled comparison, but they do not certify the number of physical refreshes presented by a display.
Using This With Other Display Tests
Pair this tool with our FPS test, refresh rate test, and monitor ghosting test for a complete display workflow. FPS tells you the average rate, refresh rate tells you what the panel supports, ghosting tells you about pixel response time, and this test tells you whether the browser is actually delivering frames at the expected cadence. A panel can have zero ghosting, native 240 Hz support, and still feel choppy if the browser is dropping every fifth frame. For the full browser-vs-camera workflow, read the frame skipping test guide.
Is this the same as a camera-based monitor frame-skipping test?
No. This page analyzes browser animation timing and provides a visual reference. A camera-based method observes the physical display through a separate procedure. Neither result should be substituted for the other without understanding what it measures.
Why can an online frame skipping test change between runs?
Tab visibility, power management, browser scheduling and other work can affect callback delivery. Keep the same settings and repeat in the foreground before comparing results.
How does this differ from an FPS or ghosting test?
The FPS test summarizes callback rate, while the monitor ghosting test provides a motion-trail comparison. Timing gaps and pixel-transition trails are different observations.
To check individual physical keys, open the keyboard tester and press each key once.
01 / 10Monitor reality check1000Hz Is Real. Worth $999?LG's UltraGear 25G590B is the first native 1000Hz 1080p monitor. Check the fine print first.02 / 10The price$999.99 for 1080pThat is the LG.com launch price, confirmed Sept 10. A 24.5-inch IPS esports panel.03 / 10The 1 ms mathOne Frame Lasts 1 msAt 1000 Hz a frame is on screen for 1 ms—the same figure as LG's own 1 ms GtG response spec.04 / 10LG's own footnoteMBR Pro Turns Off VRRFreeSync Premium and G-SYNC Compatible are disabled while MBR Pro runs. The 1100Hz overclock drops FreeSync.05 / 10Feeding itCan Your PC Push 1000 fps?LG lists Windows 11, RTX 50 / RX 9070-class GPUs and DisplayPort 2.1. 1000 Hz does not promise 1000 fps.06 / 10Reality check1080p Is Still the Majority50.52% of Steam players ran 1080p in August 2026. LG is selling speed to the biggest resolution group.07 / 10Same moneyWhat $999 Buys InsteadA 480Hz QHD OLED tracked at $547.54 on Jul 30. LG's own 480Hz dual-mode 27G850A: about $699.99.08 / 10Verdict splitBuilt for One Kind of PlayerSerious FPS competitors with GPUs to match may justify it. Everyone else buys sharper pixels for less.09 / 10Delivery dayTest Before You TrustVerify the refresh rate your system actually reports, frame skipping, dead pixels and motion clarity.10 / 10Your turnCheck Your Refresh RateSee what your browser reports right now. A browser check reads reported rate, not certified panel speed.
01 / 10Phone comparisonCompare evidence, not promisesExact-model measurements help shortlists; type, Hz and reviews cannot guarantee personal comfort.02 / 10Display methodsLCD, DC and PWM need contextDimming may change with settings. Check the exact model's waveform and test conditions.03 / 10Read the evidenceKeep the measurement conditionsKeep Hz, modulation depth, waveform, brightness and mode together; one figure misses settings.04 / 10Documented settingsCheck what a control actually changesCheck the exact-model manual. Names or labels alone do not prove an optical waveform.05 / 10Normal useStay within comfortable settingsNote comfortable normal use. Stop at discomfort; never run a challenge to provoke symptoms.06 / 10Comfort firstDo not force a low-brightness trialStop at discomfort. A difference between devices alone does not prove PWM caused symptoms.07 / 10Camera observationRecord exposure and shutter settingsCamera clips are qualitative: exposure, readout and display timing may create or hide bands.08 / 10Read cautiouslyNo bands does not mean no PWMCameras may hide PWM. Bands alone do not measure optical Hz or depth, or diagnose symptoms.09 / 10Before purchaseCheck the return policyCheck the seller's return terms. Normal-use notes inform decisions; a return window is no medical test.10 / 10Static referenceSave an observation with its limitsKeep static-field device/settings notes: no flashes, optical Hz measurement or diagnosis.
01 / 10Screen observationA static reference, not a diagnosisA steady gray field supports camera notes; it cannot diagnose symptoms or measure optical PWM Hz.02 / 10Symptom limitsSymptoms are not specific to PWMGlare, distance, dry eyes or vision issues may cause discomfort. Seek advice if symptoms persist.03 / 10What PWM meansA dimming method, not a diagnosisPWM varies on/off duty cycle; the waveform depends on the exact display, settings and mode.04 / 10Record conditionsUse comfortable brightnessNote device, mode and normal brightness. Never dim the display or keep viewing to provoke symptoms.05 / 10Static referenceNo flashing pattern is neededThe tool's steady gray field neither flashes nor moves lines, and does not access your camera.06 / 10Camera limitsBands have several explanationsExposure, rolling shutter and screen timing may hide/create bands; size or count cannot measure Hz.07 / 10Interpret cautiouslyNo single safe-Hz cutoffHz alone omits depth and waveform; no number guarantees everyone's comfort or medical safety.08 / 10Comfort firstDo not provoke symptomsUse comfortable normal settings. Stop at discomfort; seek professional advice for lasting symptoms.09 / 10Measurement limitsUse suitable optical instrumentsMeasure with suitable optical tools and recorded conditions. No bands does not prove no PWM.10 / 10Record an observationKeep the limits with the resultSave bands/no-bands and settings. Neither result diagnoses or certifies flicker-free.
01 / 10Monitor checkDark scenes losing detail?Your monitor may be turning several near-black shades into one flat black.02 / 10The symptomShadow texture disappearsHair, clothing, caves and night scenes merge into featureless black. That is black crush.03 / 10Before you testUse normal SDR settingsDim the room, avoid glare and let your eyes adapt for 30 to 60 seconds.04 / 10The testLook for 32 near-black stepsPatch 1 is darkest. Patch 32 is easiest. Use fullscreen and do not expect the low steps to glow.05 / 10Read the resultFind the first visible patchIt should be barely separate from the black background. Note its number.06 / 10ExcellentYou can see 1 through 32Your display is preserving very dark shadow steps. Subtle is correct.07 / 10Mild crushingVisibility starts near 4Brightness may be too low, or gamma may be hiding the first few steps.08 / 10Moderate to severeVisibility starts at 8 or 16Check the monitor black-level setting and whether the GPU is sending Full or Limited RGB.09 / 10Fix one variable at a timeBrightness. Range. Gamma.Retest after each change. Establish a clean SDR result before troubleshooting HDR.10 / 10See what your display keepsRun all 32 shadow stepsThe live tool is the proper diagnostic surface; compressed story images are only a guide.