# kitesurf bench report — 2026-06-01

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

## Summary (median wall time)

| Page | kitesurf/screenshot | kitesurf/html | container/screenshot | container/html |
|---|--:|--:|--:|--:|
| Example Domain | 540ms | 592ms | 375ms | 223ms |
| Hacker News | 1094ms | 935ms | 720ms | 540ms |
| Cloudflare Developer Docs | 1391ms | 1683ms | 905ms | 591ms |
| The Cloudflare Blog | 2019ms | 1886ms | 898ms | 760ms |
| Wikipedia Portal | 1173ms | 1182ms | 879ms | 480ms |
| TodoMVC · JavaScript ES6 | 733ms | 637ms | 431ms | 289ms |
| TodoMVC · React | 668ms | 608ms | 473ms | 305ms |
| TodoMVC · Vue | 696ms | 754ms | 464ms | 293ms |
| TodoMVC · Angular | 1637ms | 1448ms | 482ms | 337ms |
| TodoMVC · Preact | 624ms | 573ms | 436ms | 262ms |

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.