Provide a CSV version of the report

Have you read the documentation?

• Yes, I've read the how to make a reproducable bug guide
• Yes, I've read the how to debug my script guide

URL

https://www.whitehouse.gov/

What are you trying to accomplish

I want to have an CSV of the errors so that it is easier to compare over time. I also would like to be able to share the sheets in a way that allow me to not send a 200MB file. I just want a nice light way to share a .csv with teams so that they can see:

• The Detailed Summary
• A list of the pages tested with their scores
• The Top List Pages

There might be others that are useful, but sharing / storing the whole report sucks down a lot of GB of disk space over time.

It looks like it was added here https://www.sitespeed.io/release-notes/1.8.2/

What browser did you use?

Firefox

How to reproduce

Run this with -o csv

docker run --rm -v "$(pwd):/sitespeed.io" sitespeedio/sitespeed.io:29.3.0 https://www.example.com/ -o csv -d 3 -m 50 --sustainable.enable --axe.enable --details --description

Log output

xdg-open: no method available for opening '/sitespeed.io/sitespeed-result/mn.gov/2023-08-28-20-34-35/index.html'

    at checkExecSyncError (node:child_process:885:11)
    at execSync (node:child_process:957:15)
    at start (file:///usr/src/app/bin/sitespeed.js:148:9)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at process.processImmediate (node:internal/timers:447:9)
    at async file:///usr/src/app/bin/sitespeed.js:178:1 {
  status: 3,
  signal: null,
  output: [
    null,
    <Buffer >,
    <Buffer 2f 75 73 72 2f 62 69 6e 2f 78 64 67 2d 6f 70 65 6e 3a 20 38 38 32 3a 20 77 77 77 2d 62 72 6f 77 73 65 72 3a 20 6e 6f 74 20 66 6f 75 6e 64 0a 2f 75 73 ... 314 more bytes>
  ],
  pid: 7676,
  stdout: <Buffer >,
  stderr: <Buffer 2f 75 73 72 2f 62 69 6e 2f 78 64 67 2d 6f 70 65 6e 3a 20 38 38 32 3a 20 77 77 77 2d 62 72 6f 77 73 65 72 3a 20 6e 6f 74 20 66 6f 75 6e 64 0a 2f 75 73 ... 314 more bytes>

Start by running the reported Docker command with -o csv and inspect the generated output and the report-opening path shown in bin/sitespeed.js. Trace how the Detailed Summary, tested-page scores, and Top List Pages are produced; done means a lightweight CSV includes those requested report sections and works without requiring the full HTML report.