KlyveroRendering Benchmark
Measure rendering workload and responsiveness.
Klyvero Benchmark v1 · Browser performance only
How does your browser handle everyday tasks?
Updating a page and Responding while busy. Each result explains what was measured and how to read it.
About 30 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.
Main-thread/render callback behavior under defined load; no physical screen latency
How to use this test
- Run the fixed DOM/layout workload and the separate scheduling-responsiveness probe.
- 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
Measure rendering workload and responsiveness. It uses requestAnimationFrame; performance.now; optional PerformanceObserver. The workspace shows observations from this browser or asks for your own confirmation.
Understanding your result
Frame and task timing describe this controlled browser workload. Synthetic scheduling is not physical input latency. Main-thread/render callback behavior under defined load; no physical screen latency 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 test DOM rendering performance online?
This browser rendering benchmark observes timing during a controlled DOM workload. Use the rendering performance test to inspect browser response to this specific task.
is a rendering benchmark a website speed audit?
It does not audit the loading speed of another website or isolate panel refresh, network speed or native graphics performance.