# kitesurf bench report — 2026-05-25

commit: `caf5678` · backends: kitesurf, container · endpoints: screenshot, html · runs/combo: 5 (+ 2 warmup)
target: https://kitesurf-bench.rendering.cfdata.org

> rerun with concurrent-producer wallMs fix

## Summary (median wall time)

| Page | kitesurf/screenshot | kitesurf/html | container/screenshot | container/html |
|---|--:|--:|--:|--:|
| Example Domain | 526ms | 520ms | 274ms | 154ms |
| Hacker News | 662ms | 653ms | 672ms | 480ms |
| Cloudflare Developer Docs | 760ms | 746ms | 645ms | 449ms |
| The Cloudflare Blog | 1507ms | 1188ms | 741ms | 514ms |
| Wikipedia Portal | 633ms | 658ms | 608ms | 369ms |
| TodoMVC · JavaScript ES6 | 581ms | 545ms | 358ms | 183ms |
| TodoMVC · React | 567ms | 438ms | 365ms | 218ms |
| TodoMVC · Vue | 585ms | 572ms | 352ms | 202ms |
| TodoMVC · Angular | 599ms | 597ms | 349ms | 243ms |
| TodoMVC · Preact | 558ms | 571ms | 348ms | 188ms |

Notes:

- Values are run medians across recorded runs. p95 and min/max are in the JSON.
- Backends are dispatched from inside the `kitesurf-bench` worker via RPC bindings: `env.KITESURF.fetch(/screenshot|/html)` for kitesurf (service binding to the engine), `env.BROWSER.quickAction('screenshot'|'content', …)` for browser-run (Browser Rendering RPC), and `env.CONTAINER_HOST.fetch(…)` for container (sibling worker fronting its container backend). Wall time is the orchestrator's `performance.now()` span; `backendWallMs` / `backendCpuMs` in the JSON come from Workers Observability (kitesurf) or container-side timing headers (container). None of the measurement paths traverse the public internet.
- A cell shows `—` when every recorded run for that combination errored. See `rows` in the JSON for individual failure messages.