Start with GPU and CPU utilization, clocks, temperatures, and frame time. The component with sustained saturation is more useful evidence than a parts list alone.
FPS and frame time are different clues
Average FPS tells you how many frames are rendered over time. Frame time tells you how long individual frames take. A game can have a high average FPS and still feel uneven when frame times spike.
For a low-FPS problem, first determine whether the game is consistently slow or periodically dropping frames.
Check GPU load, CPU load, and clocks
If the GPU is near full utilization with stable clocks and temperatures, lowering GPU-heavy settings or resolution can show whether the graphics processor is the limit.
If GPU utilization is low while one or more CPU cores are saturated, the CPU, game engine, background software, or a frame-rate cap may be limiting performance. Check clocks and temperatures before concluding that the CPU is simply too slow.
Test graphics settings one category at a time
Resolution and render scale are strong GPU-load tests. Shadow quality, ray tracing, volumetric effects, and some post-processing options can also be expensive.
Do not change every setting at once. Change one group, repeat the same scene, and compare the result.
Check thermals and power behavior
A component that becomes hot can reduce its clock speed and lower performance. Watch GPU and CPU temperature alongside clock speed rather than looking at temperature alone.
On laptops, performance can also depend on the power profile and whether the system is running on AC power.
Use a repeatable test scene
The best comparison is the same game, same map or sequence, same resolution, and similar background workload. A repeatable test makes driver and settings changes meaningful and helps distinguish a real improvement from normal variation.
TWW diagnosis: change one variable at a time
A useful bottleneck test changes one graphics or workload variable and observes what happens to frame time. If lowering resolution produces a large improvement, the GPU is more likely to be limiting. If it barely changes performance while one CPU thread remains saturated, investigate the CPU or game-engine side instead.
Average FPS alone can hide the problem. Record average FPS together with 1% lows or frame-time behavior in the same repeatable scene so a fix can be judged against the same workload.
| Experiment | If performance changes a lot | Likely direction |
|---|---|---|
| Lower resolution | FPS rises substantially | GPU workload |
| Lower CPU-heavy settings | FPS or 1% lows improve | CPU/game-engine workload |
| Close background load | Stutter improves but average FPS changes little | Background contention |
| Cap FPS below the unstable peak | Frame pacing becomes smoother | Frame-time stability rather than raw GPU power |
See the evidence behind this topic
These TWW research pieces examine the measurements, mechanisms, or testing questions related to this guide. Research pages distinguish measured results from general technical guidance.
- What Actually Causes PC Game Stuttering? A Frame-Time InvestigationAverage FPS can look excellent while a game still feels bad. The useful evidence is how consistently frames arrive and what changed during the spike.
Frequently asked questions
Why is my GPU not at 100% in a game?
The GPU may not be the limiting component. A CPU thread, frame cap, synchronization setting, asset-loading delay, or game-engine limit can keep GPU utilization below full load.
Does more RAM increase FPS?
It can help when the game is memory-constrained, but it will not directly fix a GPU or CPU bottleneck.
We distinguish documented facts, measured results, and informed guidance. If a claim depends on a specific device, software version, game, or test method, that context should be stated rather than implied.
Meet the author·See our testing methodology·Read our editorial policy