CPU benchmarking and device class
Runs short compute loops to estimate how fast the device is.
In one line
Can run a short speed test to guess how fast your device is
Runs short compute loops to estimate how fast the device is.
A 50 to 500 ms JS or WebAssembly benchmark, plus worker scaling to test the real core count, ranks a phone or laptop into speed tiers. Used for adaptive quality, bot detection (headless VMs) and as a fingerprint component.
What it can and can't do
What the user does: Nothing. It happens when the page loads, and it takes about 50 to 500 ms
It can
- Run a short loop and time it
- Check how many processor cores really work
- Sort your device into a slow, medium or fast tier
- Spot bots and change video or game quality to match
It cannot
- Ask permission first
- See your files
- Name your exact device model
- Know who you are by itself
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | None |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Supported | 1 | 2004-11-09 | None |
| Safari | Supported | 1 | 2003-06-23 | None |
| Safari on iPhone | Supported | 1 | 2007-06-29 | None |
| Chrome on Android | Supported | 1 | Not listed | None |
| Samsung Internet | Supported | 5.0 | 2016-12-15 | None |
How a site asks for it
| API | performance.now() loops; Worker pools; WebAssembly; Atomics |
| How access is granted | none |
| What the user sees | Not listed |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Run fixed compute loops
- Record elapsed time
- Spawn workers to find parallel scaling
- Compare to a device-class table
Data you get
What comes back: Elapsed ms per benchmark, noise 2 to 10%
Shape: float
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
score | float | ops/s | 1e6 to 1e9 | timer and thermal noise |
Technical limits
- Timer coarsening adds noise
- Thermal throttling and background tabs distort results
The story
What it is
A script runs short math loops to estimate how fast and how powerful your device is.
For you
You see nothing, except maybe a tiny delay. The site learns whether your device is slow or fast and may change what it sends you. A fast device may get a richer page.
For makers
Sites use it to serve lighter pages on weak phones. Fraud tools use it to tell a real phone from a busy cloud server. Trackers use it to sort devices into classes.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game tests your speed once, then picks the right graphics quality. | None named |
| video | A streaming site picks the video quality that your device can decode without stutter. | None named |
| shopping | A big shop serves a lighter page with fewer scripts to a slow phone. | None named |
| security | A bot detector sees that a batch of visits all run at the same unusual speed, a sign of one server farm. | None named |
| ads | An ad tech script sorts you into a device class by speed, which helps set ad quality and price. | None named |
| developer | A web team gathers speed classes from real visitors to learn what it must support. | Vercel Analytics, SpeedCurve |
| education | An online exam site checks the device is fast enough to run the test without freezing. | None named |
Risks
- Reveals device age
- Used to sort people
Good uses and abuse
Legitimate uses
- Adaptive streaming and graphics quality
Known abuse
- Device tier, VM and bot detection, price discrimination
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 3 | Rough identifying entropy, when known |
Related capabilities
Related
- High resolution timer precision. Can use a clock whose sharpness shows your browser and privacy mode
- Clock skew and crystal timing fingerprint. Can compare your device clocks over many seconds to tell it apart
Sources
How well checked: Based on official documentation.