This is part one of a series of articles on monitoring website performance with Lighthouse. The goal of this first post is to just get the bare minimum up and running, it’s aimed more for those that don’t have much experience with Lighthouse, Gitlab, etc. The Lighthouse tool offers a lot of functionality, for more in-depth details please checkout their docs here and here. Also worth mentioning, Gitlab does provide a baked in solution for this, but you have to be on a paid tier of their service to use it.
TL;DR - clone this
Having automated tests is a good thing, but having automated tests that run as part of your build process is even better. The following few paragraphs are going to illustrate how to get started down that path.
First, a few essentials and a little about the tools that I’m using here. There are quite a few continuous integration tools out there, but for this example we are going with Gitlab.
