Device Speed Benchmark
Five timed trials, one score. See how your phone's browser performance compares — and whether it has slowed down over time.
How the benchmark works
The test runs five trials, each measuring how much work your browser completes in a fixed time: an integer-math loop, string building and joining, array sorting, WebGL rectangle drawing, and an animation frame-rate measurement. Each trial's throughput is normalized and the results combine into one score. Higher is better.
Everything runs locally on your device — no data is collected or uploaded. The whole test takes about 15–20 seconds.
Frequently asked questions
How does the score work?
The benchmark runs five timed trials — integer math, string building, array sorting, WebGL drawing, and an animation frame-rate test — and combines the timings into a single score. Higher is better. The same tests always run in the same order, so scores are comparable across devices.
Why do scores vary between runs?
Browsers dynamically adjust CPU clocks for temperature and battery, and other apps steal time in the background. For the most stable score, close other tabs and apps, plug the phone in, and run the test twice — take the second run.
Is this an accurate CPU benchmark like Geekbench?
No. It measures JavaScript and browser graphics performance, not raw chip speed. It's great for comparing phones in the same browser, or seeing whether your phone has gotten sluggish over time — but scores aren't comparable to native benchmark apps.
Does it work on desktop?
Yes. Desktops typically score much higher than phones — that's normal. The score is browser-based, so a fast phone and an old laptop may land closer than you'd expect.
Will it make my phone hot or drain the battery?
The test runs about 15–20 seconds of heavy computation, so the device may warm slightly. It stops immediately when finished and nothing runs in the background afterwards.