packages/lighthouse
packages/lighthouse
Web performance dashboard powered by Lighthouse, forked from https://github.com/boyney123/garie with addition of
git clone https://github.com/FeliceGeracitano/webperf-dashboard.git
$ docker-compose -f "docker-compose.yml" up -d --build
open dashboard at localhost
, user: admin
pass: secret
this will run 4 services
influxdb
,chronograf
,grafana
&felicegeracitano/webperf-dashboard-lighthouse
In the root of the application there is a config.json
file, which is propagated to packages/lighthouse
during docker build step.
example,
{
"cron": "0 */10 * * * *",
"urls": [
{ "url": "https://reactjs.org", "options": { "report": true } },
{ "url": "https://vuejs.org", "options": { "report": true } },
{ "url": "https://angular.io", "options": { "report": true } }
]
}
Set
report
if you want to save lighthouse report as html.More info about the cron pattern at https://www.npmjs.com/package/cron
Inspired by the lighthouse report, analyze score trend over time, identify performance metric and their thresholds. Read suggestions directly from Latest Lighthouse report embedded in the dashboard
Pretty much a like Single Page Dashboard but oriented to 1vs1
or all
comparision.
packages/lighthouse
Comment out felicegeracitano/webperf-dashboard-lighthouse
service in docker-compose.yml
, then run to spin up dependecies:
$ docker-compose -f "docker-compose.yml" up -d --build
$ cd packages/lighthouse && npm start
packages/lighthouse
In docker-compose.yml
replace felicegeracitano/webperf-dashboard-lighthouse
with
webperf-dashboard-lighthouse
(or any other local name you prefer), then run:
$ cd packages/lighthouse && docker build -t webperf-dashboard-lighthouse .
$ cd ../.. && docker-compose up
$ cd packages/lighthouse
$ docker tag webperf-dashboard-lighthouse:latest felicegeracitano/webperf-dashboard-lighthouse:latest
$ docker push felicegeracitano/webperf-dashboard-lighthouse:latest
Tip:
replace latest tag with fixed version etc 1.1, 2.0...
docker kill $(docker ps -q)
docker rm $(docker ps -a -q)
docker rmi $(docker images -q)
You can improve reviewers life running Lighthouse audit on every PR update. In this repo there is an example using a Travis CI, the job communicate progress and result to GitHub.
Running Job:
Result Comment from the BOT:
Configure your repo with a Travis Job:
GITHUB_TOKEN
for your Travis job with the GitHub token here: https://travis-ci.com/{owner}/{repo}/settings.travis.yml
file in your repo similar to: https://github.com/FeliceGeracitano/webperf-dashboard/blob/master/.travis.yml
if you inspect run_audit.sh you will notice that you need to provide an url of your running up. This obsvously depends on your app, you can choose to build your app in the travis job itsels or provide an external URL.
run_audit.sh
will launch the lighthouse service and inspectig your app, posting the result in the PR created.