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 |
|---|---|---|---|---|---|---|
| Kernel | 98.1 | 0.25s | 0.01s | 0.06s | 0.13s | 100% |
| Browser Use | 96.0 | 0.44s | 0.17s | 0.11s | 0.08s | 100% |
| Browserbase | 94.7 | 0.66s | 0.14s | 0.25s | 0.12s | 100% |
| Hyperbrowser | 94.6 | 0.63s | 0.26s | 0.13s | 0.13s | 100% |
| Tilion | 93.1 | 0.70s | 0.37s | 0.03s | 0.20s | 100% |
| Steel | 80.4 | 1.57s | 0.28s | 0.82s | 0.08s | 100% |
| Notte | 78.6 | 2.38s | 0.99s | 0.50s | 0.71s | 100% |
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%