Where does sitespeed.io put its report?

Under `sitespeed-result/ / /`, as a full static site: `index.html`, per-page and per-run pages, the waterfalls, filmstrip screenshots and video. It is meant to be served, which is why it never gets shared.

How do I share it without deploying a static host?

Drag the run directory (or a zip of it) into Comma. `index.html` becomes the report body, everything else uploads as assets with references rewritten, and you get a URL — no bucket, no CDN config, no expiring CI artifact.

Do the waterfalls and filmstrips still work?

Yes. Report HTML renders with scripts enabled inside a sandboxed iframe and the assets travel with the report, so the waterfall charts, the filmstrip and the metric graphs behave as they do locally.

The run folder is large — will it fit?

Usually, with care. Assets are capped at 25 MB per file and 250 MB / 500 files total. Video capture is what blows the budget — run with `--video false` (or drop the HAR) when the point is to share metrics rather than replay the load.

How do I compare this week to last week?

PATCH the same report id on every run. Each run appends a revision, so a regression in LCP has a visible before and after at the same URL.

Share a sitespeed.io report

sitespeed.io produces the most complete performance artifact in the open source world — metrics, waterfalls, a filmstrip, a video of the load — and delivers it as a directory that only makes sense over HTTP:

sitespeed-result/example.com/2026-08-30-09-14-22/
  index.html
  pages/…            # per-URL detail
  data/…             # HARs, budget results
  video/…            # capture, if enabled

So the performance conversation happens over a screenshot of a number, and the waterfall that explains the number stays on someone's laptop.

Publish the run

npx sitespeed.io https://example.com -n 5 --video false

Drag the timestamped run directory (or a zip of it) into the app:

index.html becomes the report body.
Pages, charts, HARs and screenshots upload as assets with their relative references rewritten to the uploaded copies.
Scripts run inside a sandboxed iframe, so the graphs and the waterfall interactions work.

Trim before you publish. --video false is the single biggest saving; the per-file cap is 25 MB and the run total is 250 MB across 500 files, and a video capture across five runs will eat both.

From CI, against one report id

npx sitespeed.io https://example.com --budget.configPath budget.json || true
zip -qr result.zip sitespeed-result
# PATCH the same report id — see /docs/ci for the full recipe

One URL per environment, one revision per run. A budget breach is then a diff between revisions instead of an alert nobody can contextualize.

What the review layer adds

Anchored threads on the offending request in the waterfall — "this third-party tag is the 400 ms, marketing owns it". See commenting on HTML.
Revisions so "did the CDN change help?" is answerable.
Access per report — private, team, domain-gated, or named reviewers. See the sharing model.

Keep it running

Performance regressions arrive on someone else's deploy schedule. A routine runs the measurement on a cron, PATCHes the same report, and notifies subscribers when it moves.

Limits

Entry HTML: 5 MB. Assets: 25 MB per file, 250 MB and 500 files total.
60 requests/minute per token.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish a performance report →