How to Fix Low FPS in the Volume Shader BM Test

A surprisingly low score on the Volume Shader BM Test is almost never a sign that your GPU is broken. Far more often, something between the silicon and the screen is holding it back — power management, a hot chip, a background app, or a stale driver. This guide walks through the causes from most likely to least, with a concrete fix for each.

Before you start: establish a baseline

Fix things one at a time so you know what actually helped. After every change, re-run the test and write down the average FPS.

Run log template:
Change made:        __________
Avg FPS:            __________
Frame time:         __________
Notes:              __________

Now, work through the list.

1. Power saving and battery mode

This is the number-one cause of mysteriously low scores, especially on laptops.

Plug laptops into power.
Turn off Low Power Mode (macOS) / Battery Saver (Windows, Android, iOS).
Select a high-performance or balanced power plan, not "battery saver."

A laptop on battery can score half of what it scores plugged in. Always benchmark on AC power unless you specifically want the battery figure.

2. Thermal throttling

A hot GPU protects itself by slowing down. If your FPS starts high and slides downward over the run, heat is the prime suspect.

Let the device cool for a few minutes before testing.
Use a hard surface; avoid beds, laps, and pillows that block vents.
Clean dust from desktop GPU fans and laptop intakes.
For desktops, check that case fans are working and airflow is clear.

3. Background applications

Anything competing for the GPU lowers your score.

Quit games, video editors, screen recorders, and streaming software.
Close extra browser tabs, especially video and 3D content.
Pause cloud sync, large downloads, and backups.
Wait for scheduled scans or system updates to finish before repeating a measurement.

4. Outdated or buggy GPU drivers

Old drivers miss performance fixes and WebGL optimizations.

Update to the latest GPU driver (NVIDIA, AMD, Apple, or your OEM).
On Windows, prefer the "Studio" or stable branch over a beta driver if stability matters.
Update your browser to the latest version.

5. Browser configuration

Browser settings can quietly cap WebGL performance.

Compare in a separate clean browser profile to identify extension-related differences without changing your usual privacy or security settings.
Ensure hardware acceleration is enabled in your browser settings.
Try a second browser to isolate the issue — Chrome and Edge both expose fast WebGL paths on Windows.

Browser quick-test:
1. Note FPS in your usual browser.
2. Open a clean second browser (no extensions).
3. Compare. If it jumps, the issue is browser-side.

6. Hardware acceleration disabled

If the browser falls back to software rendering, FPS collapses.

Confirm hardware acceleration is on.
Check that the browser is actually using your discrete GPU (on dual-GPU laptops, force the high-performance GPU for the browser).

7. Display and resolution effects

The benchmark uses a fixed 1024 × 1024 drawing buffer. Changing desktop resolution does not change that shader resolution. Browser animation callbacks can still be limited by display refresh and power settings. Use the refresh-rate test and keep the same display configuration during comparisons.

~~Windowed mode is fine~~ — mostly true, but some browsers render windowed content slightly less efficiently than fullscreen. If you are chasing every frame, test both.

8. Background system load and updates

Make sure no OS update is installing in the background.
Check Task Manager / Activity Monitor for surprise GPU usage.
Reboot before a benchmark session to clear stale state.

When to suspect a real problem

After working through the list, a genuinely low score that persists across all conditions may point to:

A driver/hardware conflict specific to your GPU model.
A failing or overheating component (especially on older hardware).
A browser bug in your current version — test another browser.

If your score is dramatically below the typical range for your hardware class after every fix here, the issue is likely environmental rather than the benchmark itself.

Avoiding the problem next time

Once your score is back to normal, a few habits keep it there. Keep your GPU driver and browser updated so you benefit from ongoing WebGL optimizations. Maintain clear airflow and clean dust periodically so thermals stay in check. On laptops, default to benchmarking on AC power. And before any future run, take thirty seconds to close background apps and tabs — that one step alone prevents most mysteriously low scores before they can mislead you.

The 15-minute recovery plan

If you only have a few minutes, do these in order:

Plug in and disable power saving.
Close every other app and tab.
Let the device cool for three minutes.
Update your GPU driver and browser.
Reboot, then run the test three times and average.

For almost everyone, that sequence recovers the missing performance. Once your numbers are honest again, run the benchmark and see the difference.