# kitesurf bench report — 2026-05-31

commit: `cd6a6d5` · 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 | 633ms | 621ms | 455ms | 261ms |
| Hacker News | 872ms | 798ms | 857ms | 615ms |
| Cloudflare Developer Docs | 1196ms | 1116ms | 1141ms | 853ms |
| The Cloudflare Blog | 1483ms | 1369ms | 1157ms | 872ms |
| Wikipedia Portal | 1109ms | 869ms | 864ms | 610ms |
| TodoMVC · JavaScript ES6 | 701ms | 650ms | 580ms | 358ms |
| TodoMVC · React | 728ms | 670ms | 549ms | 372ms |
| TodoMVC · Vue | 785ms | 725ms | 545ms | 390ms |
| TodoMVC · Angular | 876ms | 844ms | 629ms | 419ms |
| TodoMVC · Preact | 679ms | 651ms | 539ms | 325ms |

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.