How to Improve FPS: A Repeatable Troubleshooting Guide
Improve browser and game frame rates with a measured workflow covering refresh rate, power settings, background load, drivers, graphics options, and frame-time stability.
Improving FPS is easier when you first identify the limit. A low average can come from a GPU that is rendering too many pixels, a CPU that cannot keep up with game simulation, a laptop power mode, a thermal limit, or a browser that is running without hardware acceleration. Apply one change at a time and measure the result under the same conditions; otherwise it is impossible to know which tweak helped.
1. Establish a baseline
Write down the display resolution, refresh rate, browser or game version, power mode, and the scene or test used. Run the same test three times and record average FPS, minimum FPS, and worst frame time. A stable baseline is more useful than a single peak number.
For browser rendering, keep the FPS Checker tab visible and use the frame-time graph as well as the average. The browser FPS test measures the active rendering path; it does not claim to reproduce a particular game's engine.
2. Confirm the display refresh rate
Open the operating system display settings and select the highest mode supported by the monitor, cable, and adapter. A 144Hz display configured at 60Hz can make a fast renderer appear capped. Check the connection after changing resolution because some adapters reduce the available refresh-rate modes.
The display setting does not create more GPU performance. It only determines how often the panel can present a new image, so match the setting to the frame rate you can sustain.
3. Use the correct power and thermal state
On a laptop, compare plugged-in and battery results separately. Battery saver modes can reduce CPU and GPU clocks, while thin systems may throttle after several minutes of heat. Let the device reach a repeatable temperature, keep vents clear, and record whether the result is an initial burst or sustained performance.
Do not treat a cooler room, a fresh reboot, or a short benchmark as a permanent FPS improvement. If the score falls over time, the useful diagnosis is thermal or power management rather than a missing graphics setting.
4. Update drivers carefully
Install graphics drivers from the GPU or laptop manufacturer and note the version. Driver updates can fix a game-specific issue, but they can also change shader caches or default settings. After updating, rerun the same baseline and check that the game did not reset resolution, upscaling, or frame limits.
5. Remove background load
Pause large downloads, video calls, screen recording, virtual machines, and browser tabs with active media. Extensions can add work to every page and may affect a browser test. Compare a normal session with a clean browser profile before uninstalling software; the comparison provides better evidence about the cause.
6. Find whether the CPU or GPU is limiting you
Lower the render resolution while keeping the scene and frame cap unchanged. If FPS rises substantially, the workload is likely GPU- or pixel-limited. If it barely changes while the CPU is busy, the limit may be game simulation, draw calls, or another CPU task. This is a diagnostic comparison, not a universal rule, because engines can move work between processors.
7. Change graphics settings in a useful order
Start with settings that usually have a clear cost: resolution scale, ray tracing, shadows, volumetric effects, reflections, and view distance. Change one setting at a time and keep a short log. Upscaling can recover performance, but inspect the image for shimmering or ghosting instead of assuming a higher FPS number is automatically better.
For competitive play, a consistent frame time and a sensible frame cap may be preferable to an unstable maximum. Adaptive sync can reduce tearing when the frame rate varies, but its range and latency behavior depend on the display and GPU.
8. Check browser acceleration and page conditions
In a browser, hardware acceleration should normally be enabled, but a driver crash or policy can disable it. Check the browser's system page, restart after changing the setting, and rerun the visible test. Keep the window size, zoom, display scaling, and tab focus constant. Background tabs may be throttled by design; this is why requestAnimationFrame-based tests must stay visible.
Read the frame-time evidence
Average FPS hides uneven delivery. At 60 FPS the target is about 16.67ms per frame; at 144 FPS it is about 6.94ms. A graph with regular bars suggests stable pacing, while occasional tall bars indicate long frames. Compare the worst frame and the frequency of spikes before deciding that a tweak worked.
A safe comparison checklist
- Change one variable.
- Run the same scene or browser test three times.
- Record average FPS, minimum FPS, and frame-time spikes.
- Keep the best and worst run, not only the best run.
- Revert a change if the image quality, stability, or latency becomes worse.
The goal is not to chase a benchmark number. It is to find settings that keep frame delivery stable for the work you actually do. For browser measurements, run the FPS test after every meaningful change and include the conditions with your result.