The Browser Arena

Compare per-action speed inside a running session: navigate, wait, screenshot, read, click, back. Actions per second, tail latency, drift, and cost per 1,000 actions.

Once a session is up, how fast does each agent step complete? Every session runs a fixed loop of ten actions on Wikipedia at a 1920x1080 viewport, each action timed on its own. A session only counts as a success when every action succeeded. Methodology.

Benchmark

Browser Throughput · Sequential runs

Percentile
#ProviderRunsSuccess (%)Actions (%)Actions/sTaskNavigateWaitScreenshotReadClickBackDrift$/1k actions
11020 actions100.0%100.0%5.793.45s301182190102621751.01x$0.0014
21020 actions100.0%100.0%5.293.78s30624119611289581.00x$0.0032
31020 actions100.0%100.0%4.594.36s36730322720380760.95x$0.0013
41020 actions100.0%100.0%3.725.38s521309224193892810.90x$0.0142
51020 actions100.0%100.0%3.475.76s44946627414282510.91x$0.0008
61020 actions100.0%100.0%3.336.01s732321264125052170.92x$0.0120
71020 actions100.0%100.0%2.258.91s886583410174545280.98x$0.0123
81020 actions100.0%100.0%0.7426.95s6801.67s1.82s1991.82s3971.05x$0.0383
91020 actions0.0%90.0%0.5532.93s18518821628N/A55—$0.0303

Per-action columns are in milliseconds at the selected percentile, over successful actions. Row numbers follow the current sort and percentile; the default order is actions per second, highest first.