Frame Time Test - Detect Stutter and Frame Pacing Spikes
Run a live frame time test in your browser. Visualize frame pacing, detect timing spikes and understand why stable frame times matter more than peak FPS.
Live Frame Time Graph
Lower and more consistent frame times produce smoother motion.
Average
--
Equivalent FPS
--
Worst frame
--
Detected spikes
0
Frame Time vs FPS
FPS counts frames per second, while frame time measures how long each frame takes to appear. At 60 FPS the target is 16.67ms per frame; at 120 FPS it is 8.33ms. Equal average FPS can feel different when one session has frequent timing spikes.
Compare the result with the broader online FPS test.
How to Read the Graph
Short, even bars indicate consistent delivery. Isolated tall bars may be delayed frames. Repeated spikes can be caused by browser extensions, background tasks, thermal throttling, driver problems or power-saving settings.
Browser Test Limitations
This test measures browser animation timing, not a specific game's rendering pipeline. For game diagnosis, also use the game's frame-time overlay or a dedicated capture tool.
Frequently Asked Questions
What is a good frame time?
A good frame time matches your target: 16.67ms for 60 FPS, 8.33ms for 120 FPS and 6.94ms for 144 FPS. Consistency is as important as the average.
What causes frame time spikes?
Common causes include background CPU activity, shader compilation, storage access, thermal throttling, unstable drivers, browser extensions and power-saving modes.
Does high FPS eliminate micro-stutter?
No. A high average FPS can still include unevenly delivered frames. A frame-time graph exposes irregular pacing that an average FPS number can hide.