What Is a Good FPS Score on the Volume Shader BM Test?
Learn how to judge a Volume Shader BM Test result with a repeatable device baseline, refresh-rate limits, frame-time budgets, and fair comparison rules.
A useful Volume Shader BM Test result is a repeatable measurement under documented conditions. There is no universal pass score and no verified hardware ranking for this site's shader workload.
What a score represents
The benchmark renders one default WebGL volumetric shader at a fixed 1024 × 1024 drawing-buffer size. It reports current and average FPS, sampled minimum and maximum FPS, frame time, active running time, and rendered-frame count.
Changing the shader or its camera changes the workload. Running the same shader in another browser can also change the result because browser scheduling, graphics backends, drivers, and power settings differ. A number only becomes useful when you record those conditions with it.
Refresh rate can set a ceiling
The animation loop follows browser frame callbacks. On a display refreshing around 60 Hz, a capable GPU may still produce a result near 60 FPS in this test. That does not mean the GPU's maximum rendering throughput is 60 FPS. It may mean the browser is scheduling approximately one animation callback per display refresh.
The refresh-rate test estimates browser callback timing. Use it to understand a possible ceiling, while remembering that browser timing can differ from the panel's advertised refresh rate.
FPS and frame-time budgets
| Steady rate | Equivalent frame time |
|---|---|
| 30 FPS | 33.33 ms |
| 60 FPS | 16.67 ms |
| 90 FPS | 11.11 ms |
| 120 FPS | 8.33 ms |
| 144 FPS | 6.94 ms |
These are arithmetic conversions, not GPU tiers or predictions of gaming performance. The FPS calculator converts other rates and calculates the percentage change between two measurements.
Build a baseline for your device
- Restore the default shader and camera.
- Record the browser, OS, power settings, and available renderer information.
- Keep the page visible and close competing graphics workloads.
- Choose the same active duration for each run, such as 30 seconds.
- Pause and download JSON or CSV after each run.
- Repeat three times under comparable starting conditions.
Use that range as your baseline. If the three measurements vary substantially, investigate the environment before interpreting a small change as a hardware improvement or regression.
Comparing a change fairly
Suppose one controlled run averages 40 FPS and another 50 FPS. The arithmetic increase is 25 percent. Whether the change is meaningful depends on how much repeated runs normally vary and whether the browser, shader, camera, and settings stayed the same.
Do not compare a custom shader result with a default-shader result. Do not use scores from unrelated websites as if they run the same workload. Do not infer a game FPS value from this shader's FPS.
What the summary does not show
Minimum and maximum FPS refer to short reporting windows. They are not per-frame percentiles or 1% lows. The numeric frame-time readout does not provide a full distribution, lag-spike count, or input-latency measurement.
For individual frame timing, use browser profiling tools. For a possible hardware fault, use suitable system diagnostics. A low score by itself does not identify a failed component or prove thermal throttling.
When to investigate
Investigate when a result repeatedly falls outside your own controlled baseline, when the default shader shows visual artifacts, or when the browser loses its WebGL context. Start with the low-FPS troubleshooting guide and WebGL report.
Judge a result by reproducibility and context. The most useful comparison is often your own device before and after a single documented change.