Run Lighthouse audits on the pipeline
Lighthouse is an open-source, automated tool for improving the quality of web pages. It's built into Google Chrome, but it can also run on the command-line.
Lighthouse can measure accessibility, SEO, general best practices, and performance.
We do not currently track metrics about the website itself over time. It might be helpful to track Lighthouse scores in order to spot regressions or find weak points to focus on.
Questions
- When should it run? We could run this as part of MRs to
gitlab-docs
, or only as part of a release, or on a schedule... - Which pages should it test?
- How much time does it add to the pipeline?
- How would we be able to use the data outside of the CI job?
Links
- https://developer.chrome.com/docs/lighthouse/overview/
- https://github.com/GoogleChrome/lighthouse-ci
- Demo dashboard of Lighthouse scores: https://sarahgerman.gitlab.io/docs-website-audit/ (code here)