benchlab Explore tools
← Back to BenchLab
BENCHLAB / PERFORMANCE

Browser Benchmark

Measure your browser's JavaScript performance with repeatable computational workloads. Close heavy tabs for more consistent results.

OVERALL SCORE
— points

Run the benchmark to calculate your score.

Ready to test
TEST SUITE

JavaScript workloads

3 TESTS
∑

Mathematical operations

Arithmetic, square roots, and numeric calculations

— ms
⌘

Sorting performance

Sort generated numeric datasets repeatedly

— ms
{ }

Data processing

Transform and aggregate a numeric dataset

— ms

Waiting to start

Results depend on your device, browser, power mode, and background activity. This test runs locally in your browser.

ABOUT THIS BENCHMARK

How to read the results

This is a repeatable JavaScript workload test. It measures how long your current browser takes to complete these tasks; it does not measure your network, graphics performance, or native CPU speed.

Three workloads

Mathematical operations
1.2 million square-root and sine calculations.
Sorting performance
100,000 generated numeric values sorted numerically.
Data processing
A 500,000-element Float64Array is filled and aggregated.

Timing and score

Each workload runs once to warm up JavaScript execution paths, then runs three timed samples. The displayed time is the median of those three samples, in milliseconds. Lower times mean the task completed faster.

For each workload, the component score is its target time divided by its measured median: math 180 ms, sorting 260 ms, and data 180 ms. The overall score is Math.round(1000 × geometric mean(component scores)). A higher score therefore means faster performance relative to these fixed targets, not a certified or universal device ranking.

Compare fairly

Use the same browser and device when comparing runs. Keep the power mode, thermal state, browser version, open tabs, and background activity as consistent as possible, and avoid running other heavy work at the same time.

The workloads run synchronously on the main thread, so they can temporarily make the page less responsive. Repeat a run if the conditions changed, and compare the individual times as well as the relative score.