CPU Benchmark
Run integer, floating-point and hashing workloads in the background for a browser-specific CPU score. Abortable, no external database.
This feature isn’t available here
Background processing isn’t available, so the CPU benchmark can’t run.
Commonly supported by: All modern browsers.
What you can do: Update your browser.
01How this test works
System and browser tests read information your browser already makes available — things like your screen, platform, and which features are supported. Simply viewing these pages triggers no permission prompts.
Nothing is combined into a tracking identifier. Where a value is only approximate because your browser hides some details for privacy, we tell you.
A feature showing as ‘supported’ means it exists in your browser; actually using some of those features may still need your permission or a secure (HTTPS) connection.
02How to use it
- Open the test — most system tests read values immediately with no permission needed.
- Review the reported information or capability matrix.
- Use search or filter where provided to find a specific feature.
- Copy or download the results if you want to share them (they contain no hidden identifier).
03What this test covers
What it detects
- Browser-exposed device details: platform, screen, cores, memory hint, languages and time zone
- Support for storage, graphics, media, worker and sensor APIs
- WebGL/WebGPU renderer details where the browser exposes them
- Battery, storage estimate and network information where available
What it can’t detect
- Exact hardware model, serial numbers, or anything deliberately hidden for privacy
- Physical component health (battery capacity, disk wear) — browsers don’t expose it
- Values reduced by the browser, such as a precise User-Agent or full GPU string
04Troubleshooting
| Symptom | What to do |
|---|---|
| Some info is missing | Modern browsers intentionally limit what they share to protect your privacy. |
| A feature shows unsupported | This browser doesn’t support that feature; try a recent version over HTTPS. |
| Graphics details are hidden | Some browsers hide your graphics-card name for privacy; that’s expected, not an error. |
| Battery info shows nothing | Several browsers removed battery reporting for privacy; use your device’s own battery indicator instead. |
05FAQ
Do you fingerprint me?
No. We show information but never build a hidden cross-session fingerprint or hash.
Why is some info missing?
Modern browsers intentionally limit what they expose to protect your privacy.
Is this data sent anywhere?
No. It’s read and displayed locally in your browser.
Does ‘supported’ mean I can use the feature?
It means the API exists. Using it may still require permission or a secure (HTTPS) context.
Why doesn’t it show my exact GPU or browser version?
Browsers increasingly reduce these details for privacy, so some values are approximate.
Can this test my hardware’s health?
No. Browsers don’t expose battery capacity, disk wear, or similar health metrics.
Related tests
Measure memory allocation and throughput in the background with a strict cap. Browser memory performance, not RAM health.
Measure 2D graphics rendering performance with moving shapes and text at several quality levels, reporting frame-time percentiles.
Render tens of thousands of animated points with WebGL and sample frame times at several quality levels. Browser-specific, not a health check.