For a number of our build assets, we'd like to keep track of how big they are over time.

• lighthouse-background.js: Used in both extension and devtools.
• viewer/main.js: Used in the online viewer
• the tarball that's published to NPM

Relatedly.. we're also interested in tracking the duration of doing a default lighthouse run. Potentially against both a simple site (example.com) and a more complex one (chromestatus.com).

This is pretty wide open for implementation.

Some of this could be done based on our travis/smokehouse runs.
No preferences on where the data gets beaconed to, but something that's easy for the team and community to view.