Browser Throughput Benchmark
Browser Throughput
Per-action throughput inside a running session — 10 sequential actions across 100 sessions per provider.
Powered byWant to see a provider added?
Methodology
What We Measure
Each session executes 10 sequential actions inside a single running browser: navigate → waitForSelector → screenshot → textContent → click → waitForSelector → screenshot → textContent → goBack → waitForSelector, on Wikipedia.
Every action is timed individually. A failed action does not abort the session — the sequence continues and the failure is recorded. This lets us observe degradation patterns rather than discarding unlucky sessions.
Each provider runs 100 sessions per benchmark run. All sessions use stealth mode and a 1920×1080 viewport to match realistic agent conditions. Benchmarks run weekly via GitHub Actions and results are committed to the public benchmarks repo.
How We Score
The Composite Score (0–100, higher is better) weights four axes that matter for agent workloads, then multiplies by success rate so flaky providers can't hide behind fast averages.
- • Actions/sec median: 40% — primary throughput signal
- • Task duration median: 25% — typical session cost
- • Task duration p95: 20% — tail consistency
- • Screenshot median: 15% — vision-agent proxy
The final score is multiplied by success rate — the fraction of sessions that completed all 10 actions. A provider that fails 1 in 10 actions is penalized proportionally.