Read real smoothness behind the FPS counter
Average FPS can look good on paper while hiding frametime spikes. To judge a Windows optimization, measure consistency as well as speed.
Latence lets you compare a session before and after a change and look at FPS, frametimes, and stability instead of relying on feel alone.
Download LatenceSimple definition
FPS is the number of frames produced per second. Frametime is how long each frame takes to arrive. At a steady 60 FPS, each frame should arrive about every 16.7 ms.
At 144 FPS, the target is about 6.9 ms. If some frames take much longer, you feel a stutter even when average FPS stays high.
In-game symptoms
Good FPS but a heavy feel
The counter shows 120 or 160 FPS, but movement is uneven during fights, fast turns, or area loading.
Short micro-stutters
The game catches briefly without a dramatic visible drop. Frametime graphs reveal these spikes better than an average FPS number.
What to record
- Average FPS for overall performance.
- 1% low and 0.1% low FPS for slower frames.
- Frametime graph or percentile values for consistency.
- GPU and CPU usage, temperatures, clocks, and memory pressure.
- Game version, driver version, resolution, preset, and test scene.
A reliable before-and-after test
- Choose one repeatable scene, route, replay, or benchmark.
- Keep resolution, graphics preset, frame cap, and refresh rate identical.
- Run the same number of passes and ignore the first pass if it is a shader-cache warm-up.
- Change one setting only, then repeat the exact test.
- Compare frametime shape, lows, and consistency, not just the highest average.
If a change raises the average by two FPS but adds large spikes, it may feel worse. A slightly lower but steadier result can be the better gaming profile.
Common measurement traps
Do not compare a busy multiplayer fight with an empty training area. Do not compare different driver versions, game patches, or background loads without recording them. Overlays and capture tools can also change the result.
Frame pacing is local. It is different from ping and network jitter, although a game can feel similar when either one becomes unstable.
What Latence can help you check
Latence helps keep the test readable: record the Windows state, compare before and after, and keep a rollback when a profile makes the system less stable. Pair this guide with unstable frametime diagnosis and Windows FPS drops.
Are average FPS enough?
No. Average FPS can hide long frames. Look at 1% lows and frametime consistency as well.
What is a good frametime at 144 FPS?
About 6.9 ms per frame when the frame rate is genuinely steady. Spikes above that value are what you feel as stutter.
Should I optimize for maximum FPS?
Not automatically. A stable frame time and predictable input can feel better than a higher but uneven average.
Measure smoothness, not just speed
A repeatable benchmark shows whether an optimization really improves the session.
Test Latence on Windows