Volume Shader Test FPS Result Guide
How to read your result — FPS tiers, frame time, stability, and what actually changes the score.
Your Volume Shader BM result is more than a single number. Here is how to read the FPS, frame time and stability values, and what they tell you about your GPU.
Quick answer
- 60+ FPS — this workload is rendering smoothly under the current conditions.
- 30–60 FPS — this workload is running at a moderate interactive frame rate.
- 15–30 FPS — heavy load, switch to Light or Medium for a fairer reading.
- Under 15 FPS — this mode is below a comfortable interactive frame rate; FPS alone does not reveal the cause.
- Compare only the same engine version, mode, resolution and browser conditions.
FPS — average vs minimum
Average FPS describes how the run felt overall. Minimum FPS shows the worst second — if your minimum is far below the average, you're hitting GPU stalls (shader recompilation on first run, background tab competing for the GPU, thermal step-down).
Frame time — the sister metric
Frame time is the time in milliseconds to render one frame. 60 FPS ≈ 16.7 ms, 30 FPS ≈ 33.3 ms. A spiky frame time graph is what makes a game feel "stuttery" even when the average FPS looks fine. If you see large spikes, try fixing the lag first.
Stability
Stability is minimum 1-second FPS divided by maximum 1-second FPS. A higher value means less variation in this run, but it does not identify the cause of variation or predict VR, AI, game or creative-app performance.
What changes your FPS
- GPU generation and tier — naturally.
- Integrated vs dedicated GPU — laptops often default to integrated.
- Browser hardware acceleration on / off.
- Thermal throttling on long Heavy or Extreme runs.
- Other tabs using GPU (video playback, WebGL ads, Google Maps).
- OS power profile (Battery Saver, Low Power Mode, GPU frequency cap).
Run the test
Take a measurement, then come back and check your number against the tiers above.
