KlyveroWebGPU Test
Exercise WebGPU adapter/device and workloads.
Klyvero Benchmark v1 · Browser performance only
How does your browser handle everyday tasks?
Graphics calculations. Each result explains what was measured and how to read it.
About 15 seconds · Keep this tab open and close busy apps first. Your device may get warm and use more battery. You can stop at any time.
Optional. Keep this the same during the test. If you plug in or unplug, stop and start again.
Ready when you are
How should I use these results?
Start with the task, not the biggest number. More tasks per second means more work completed; fewer milliseconds means less waiting. 1,000 milliseconds equals one second. Different checks use different tasks and units, so their numbers cannot be compared with one another.
To compare repeated runs, use the same test version, browser, settings and power conditions. Technical details show the method, worker count and source hash needed to check whether runs match.
There is no overall score or device ranking yet. We do not have a reviewed reference dataset to say how your device compares with others. Score calibration pending. These are approximate browser measurements, not a hardware health certificate.
Optional/secure/policy/driver dependent; presence alone insufficient; handle null adapter and device loss
How to use this test
- Request an adapter and run the optional bounded WebGPU integer-compute workload.
- Choose a workload and explicitly start the versioned benchmark. You can stop at any time.
- Review seven raw samples and dispersion. Score calibration is pending; native benchmark equivalence is not claimed.
How it works & what results mean
How the test works
Exercise WebGPU adapter/device and workloads. It uses navigator.gpu; requestAdapter/requestDevice; bounded commands. The workspace shows observations from this browser or asks for your own confirmation.
Understanding your result
API exposure does not guarantee an adapter or device. Unsupported operation is not a low performance score; it remains unavailable. Optional/secure/policy/driver dependent; presence alone insufficient; handle null adapter and device loss Missing data, blocked permission and an operation that could not run are shown separately. None establishes a hardware fault.
Keep checking
Related tests
About this test & common questions
how to run a WebGPU compute test online?
This WebGPU test requests supported compute access and measures a bounded workload. The WebGPU benchmark reports completed work only after the operation succeeds.
why is a WebGPU test unsupported?
Secure context, browser support, platform policy and adapter availability can limit access. Missing support does not establish a GPU fault.