Browser Benchmarks
Headless browser session benchmarks — create, connect, navigate, and release latency across providers. 100 iterations per run.
Powered byPerformance Over Time
Composite Score
Detailed Metrics
Provider | Score | Total (med) | Create (med) | Connect (med) | Navigate (med) | Success |
|---|---|---|---|---|---|---|
| Tilion | 98.9 | 0.12s | 0.02s | 0.03s | 0.06s | 100% |
| Kernel | 97.8 | 0.26s | 0.01s | 0.07s | 0.13s | 100% |
| Browser Use | 95.6 | 0.50s | 0.18s | 0.17s | 0.07s | 100% |
| Hyperbrowser | 94.4 | 0.66s | 0.26s | 0.14s | 0.15s | 100% |
| Browserbase | 90.1 | 1.30s | 0.14s | 0.91s | 0.11s | 100% |
| Notte | 84.5 | 1.89s | 0.41s | 0.52s | 0.77s | 100% |
| Steel | 21.5 | 11.81s | 2.75s | 1.39s | 0.11s | 99% |
Want to see a provider added?
Methodology
What We Measure
Each benchmark provisions a headless browser session, connects over CDP, navigates to a target page, and releases the session, measuring the time for each phase independently.
Five metrics are captured per iteration: create, connect, navigate, release, and total end-to-end latency.
Each provider is tested with 100 iterations per run. Benchmarks run automatically via GitHub Actions on a recurring schedule. All results are committed to the public benchmarks repo.
How We Score
The Composite Score is a weighted blend of total-latency percentiles and create latency, multiplied by the success rate. Latency is scored against a fixed 10-second ceiling: 100 × (1 − value / 10,000ms).
The weighted score is multiplied by the success rate (0–1), so providers that fail frequently are penalized proportionally.
- • Total median: 40%
- • Create median: 30%
- • Total P95: 20%
- • Total P99: 10%