Skip to main content
FPS & Frame PerformanceFrame Latency (ms)

Frame Time Test — Measure Millisecond Latency Online

Inspect individual frame generation intervals in milliseconds, evaluate P95/P99 latency percentiles, and detect micro-stutter spikes.

READYMicrosecond Performance Clock (performance.now)

Measure Frame Time Latency

Measures exact millisecond intervals between rendered frames to detect micro-stutters and scheduling variance.

Reference Baseline:
Median Frame Time
50th percentile (P50)
95th Percentile (P95)
Tail latency
99th Percentile (P99)
Worst 1% latency
Spikes (>1.5x)
0
Detected stutters

Frame Time Reference Table

Frame time is inversely proportional to FPS (Formula: Frame Time = 1000 ÷ FPS). Consistency across frame intervals is the true foundation of smooth visual motion.

Frame Time Reference Matrix

Formula: 1000 ÷ FPS
Target Frame RateExact Frame TimeOperational Context
30 FPS33.33 msBaseline interactive frame rate
60 FPS16.67 msUniversal desktop & mobile standard
90 FPS11.11 msSmooth motion threshold
120 FPS8.33 msHalf the frame latency of 60Hz
144 FPS6.94 msStandard esports monitor target
165 FPS6.06 msEnhanced motion clarity
240 FPS4.17 msNear-instantaneous frame delivery
360 FPS2.78 msSub-3ms frame rendering pipeline

Frequently Asked Questions

Why is frame time more revealing than average FPS?

Average FPS blends fast and slow frames together, masking brief 50ms stutters. Frame time measures the exact millisecond delivery cost of every single frame, exposing micro-hitching and latency spikes directly.

What are P95 and P99 frame times?

P95 and P99 represent the 95th and 99th percentile worst-case frame times. If your median frame time is 6.94ms (144 FPS) but your P99 is 30ms, you will experience noticeable hitching in 1% of rendered frames.

What causes frame-time spikes?

Spikes are triggered by garbage collection passes, background CPU thread contention, GPU thermal throttling, or asset loading delays in the browser graphics pipeline.