All benchmark files are loaded before the start. The measured phase then remains free of network requests. Keep the tab visible and do not resize the window.
Technical check
System check
Browser capabilities and test files are checked once before the benchmark starts.
Browser capabilities and test files are being checked.
Checking
Before the benchmark starts, we check the five technical requirements the suite actually needs. This only takes a moment and prevents a run from failing several minutes later because a required browser feature is missing.
When all five items show OK and the status above says “Ready”, your browser is technically ready to start. Actual performance is only measured once the benchmark begins.
Optional
Contribute this run to reference calibration
Voluntary
BrowserBenchmark.org is still new and needs real measurements from many different devices. If you want, your run can help build that reference. The benchmark itself works exactly the same if you leave the box unchecked.
What does this mean in practice?
The data is retained while it is needed to build, review and complete the reference calibration. To avoid repeated tests from one computer being counted as many different devices, a data-minimised device signature is created before the run from technical characteristics such as screen, pixel density/colour depth, CPU thread count, touch capability, platform family and time zone. We do not use font lists, audio fingerprints or canvas-pixel fingerprints for this.
Publicly sharing your result is separate and can be explicitly enabled later on the result page. Privacy details
Depending on the device, the test usually takes about 1–3 minutes. Very slow hardware may need longer.
BB
Benchmark running
—
—
Keep the tab visible and do not resize the window.