Skip to Content
Platform.Ontology

CPU benchmarking and device class

Runs short compute loops to estimate how fast the device is.

Used to track youSpeed and timingComputeWeb browsersWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11None
EdgeSupported792020-01-15None
FirefoxSupported12004-11-09None
SafariSupported12003-06-23None
Safari on iPhoneSupported12007-06-29None
Chrome on AndroidSupported1Not listedNone
Samsung InternetSupported5.02016-12-15None

How a site asks for it

APIperformance.now() loops; Worker pools; WebAssembly; Atomics
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Run fixed compute loops
  2. Record elapsed time
  3. Spawn workers to find parallel scaling
  4. Compare to a device-class table

Data you get

What comes back: Elapsed ms per benchmark, noise 2 to 10%
Shape: float

FieldTypeUnitRangePrecision
scorefloatops/s1e6 to 1e9timer 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

TypeExampleApps
gamesA browser game tests your speed once, then picks the right graphics quality.None named
videoA streaming site picks the video quality that your device can decode without stutter.None named
shoppingA big shop serves a lighter page with fewer scripts to a slow phone.None named
securityA bot detector sees that a batch of visits all run at the same unusual speed, a sign of one server farm.None named
adsAn ad tech script sorts you into a device class by speed, which helps set ad quality and price.None named
developerA web team gathers speed classes from real visitors to learn what it must support.Vercel Analytics, SpeedCurve
educationAn 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

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits3Rough identifying entropy, when known

Sources

How well checked: Based on official documentation.

On this page