KlyveroCPU/JavaScript Benchmark
Run distinct main-thread JavaScript and single-worker workloads.
Klyvero Benchmark v1 · Browser performance only
How does your browser handle everyday tasks?
Number calculations and Background calculations. 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.
JavaScript/engine main-thread throughput; no native CPU or core performance equivalence
How to use this test
- Run the main-thread JavaScript and single-worker kernels under stable foreground conditions.
- 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
Run distinct main-thread JavaScript and single-worker workloads. It uses Bounded main-thread JavaScript workload; performance.now. The workspace shows observations from this browser or asks for your own confirmation.
Understanding your result
These exercise the JavaScript engine and scheduling. They are not native CPU throughput, physical core count or clock-speed measurements. JavaScript/engine main-thread throughput; no native CPU or core performance equivalence JavaScript/engine/worker throughput; no native CPU or core performance equivalence Missing data, blocked permission and an operation that could not run are shown separately. None establishes a hardware fault.
What you can inspect
CPU/JavaScript Benchmark
JavaScript/engine main-thread throughput; no native CPU or core performance equivalence
Single Worker Benchmark
JavaScript/engine/worker throughput; no native CPU or core performance equivalence
Keep checking
Related tests
About this test & common questions
how to run a CPU benchmark in a browser?
Run a CPU benchmark using timed JavaScript calculations. This browser processor benchmark reports the work completed by the selected calculation workload.
does a browser CPU test measure native processor speed?
Browser engine, power state and background work affect results. JavaScript throughput is not native CPU throughput or a clock-speed measurement.