What metrics appear after a run?
After you run the GPU test online, the main reading is live FPS for the Volume Shader BM scene. Frame time and stability matter next: they show whether those frames arrive evenly or in bursts that feel like lag.
- FPS: frames rendered per second; higher is stronger for this scene
- Frame time: time to draw one frame; lower and steadier is better
- Stability: how consistent frame times stay under load
- Visible stutter: sudden drops that often mean heat or power limits
What is a good FPS score?
FPS ranges for this scene are guides, not grades for every device class. Complexity level, browser, and phone versus desktop change the bar.
- 60+ FPS: strong for the selected complexity
- 30–60 FPS: usable under load; watch for dips as the device warms
- 15–30 FPS: heavy load for this GPU or power mode; cool down and retest
- Below 15 FPS: the scene is overloading the device at this complexity
What factors change your results?
Browser choice, background apps, battery saver, device temperature, software age, and hardware age all move FPS. Close heavy tabs, cool the device, and use an updated browser before you judge a low score.
How do you compare devices fairly?
Compare similar classes under similar conditions. Match browsers when you can. Use the same complexity. Average a few runs after a cool-down. Do not treat a phone score and a desktop score as one chart.
- Same browser family when possible
- Similar temperature and power mode
- Same complexity level
- Multiple runs averaged after noise settles
- Similar device age and class
Why do frame time and stability matter?
A steady 30 FPS often feels smoother than a spiky 40–50 FPS average. Variable frame times cause visible stutter even when the average looks fine. Prefer consistency under load over a short peak.
What do results mean in real use?
Higher, steadier FPS on this scene usually tracks with smoother WebGL and 3D-heavy browser work. It is one graphics signal. It does not measure storage, camera, or battery life. For method limits, read are browser benchmarks accurate.
Why did my device score lower than expected?
Check background apps, battery saver, browser age, and heat first. Older or lower-end GPUs score lower by design. On phones, continue with the phone GPU test, lag, and stress guide.
Can I improve a noisy result?
Close background apps, leave performance mode on, cool the device, update the browser, and restart before a second pass. Stop if the device becomes too hot to hold. Safety notes are in is Volume Shader BM safe.
How should you use the leaderboards?
Your live FPS is a personal reading. Public leaderboards order hardware by average FPS from many anonymous shares on the branded Start runner. Use boards to see where similar devices tend to land, then judge your own run with the fair-compare tips above.
Read how Volume Shader BM leaderboards work for platform boards and sharing.
What should you open next?
Run another pass on the GPU test online, or pick a processor check on the CPU test online. Browse every tool from the Tests hub.