# Share a sitespeed.io Report — A Link Instead of `sitespeed-result/`

Canonical: https://commareports.com/share-sitespeed-report
Published: 2026-08-30

> sitespeed.io writes a whole static site of performance results, filmstrips and waterfalls. Publish the run folder to Comma for a URL the team can open and annotate.

# 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

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

Drag the timestamped run directory (or a zip of it) into
[the app](https://commareports.com/):

- `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

```bash
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](/comment-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](/docs/sharing).

## Keep it running

Performance regressions arrive on someone else's deploy schedule. A
[routine](/features/routines/scheduled-html-reports) 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 →](https://commareports.com/)**

### Related

- [Share a Lighthouse report](/share-lighthouse-report) · [Share a k6 load test report](/share-k6-load-test-report)
- [Share a JMeter report](/share-jmeter-report) · [Share a Gatling report](/share-gatling-report)
- [Share a Pa11y report](/share-pa11y-report) · [Scheduled reports](/features/routines/scheduled-html-reports)