Skip to content

andredesousa/lighthouse-audit-testing

Repository files navigation

Testing web sites with Google Lighthouse

Lighthouse is an open-source, automated tool for improving the performance, quality, and correctness of your web sites. This project provides a basic setup for auditing websites using Google Lighthouse.

Overview

Lighthouse analyzes web apps and web pages, collecting modern performance metrics and insights on developer best practices. The tool audits the accessibility and SEO of your webpage, with a particular focus on Core Web Vitals. These metrics have become increasingly important for website owners that want to provide a good user experience and rank higher on Google.

A config file called lighthouserc.json at the test folder controls the options for Lighthouse CI. autorun command will automatically execute a number of commands behind the scenes and infer sensible defaults for you.

This project uses Lighthouse CI server in a Docker container, so first ensure you have Docker installed and running. You can use the docker-compose up -d command to startup Lighthouse CI server. Once the instance has started, navigate to http://localhost:9001/ where you should see the dashboard welcome page.

As detailed on the welcome page, you need to create a project for your Lighthouse results to be uploaded to. You can use npm run wizard command to guide you through these steps.

Available npm scripts

The scripts in package.json file were built with simplicity in mind to automate as much repetitive tasks as possible and help developers focus on what really matters.

The next scripts should be executed in a console inside the root directory:

  • check - Runs all checks.
  • lint - Runs several static code analysis.
  • lint:fix - Applies lint rules to project code.
  • test - Test the web site pages.
  • clean - Deletes the temporary files.

For more details, read the npm scripts documentation.

Linting and formatting code

Linters are also excellent tools for finding certain classes of bugs, such as those related to variable scope.

Use npm run lint to analyze your code. Many problems can be automatically fixed with npm run lint:fix.

Depending on your editor, you may want to add an editor extension to lint and format your code while you type or on-save.

Running audit tests

Audit tests are responsible for auditing the accessibility and SEO of your webpage, with a particular focus on Core Web Vitals.

Use npm run test to execute the audit tests via Lighthouse.

After running the audit of your webpage, Lighthouse will generate a report on 4 different areas:

  • Performance includes elements that slow your page down, including images and resources.
  • Accessibility audits how accessible your content is to users, including the use of assistive technology.
  • Best Practices identifies any web development element that does not follow best practices.
  • SEO highlights the most essential SEO issues with the webpage.

The HTML report is available in the .lighthouseci folder and you can opening it in your web browser. Lighthouse generates a HTML file for each page.

Reference documentation

For further reference, please consider the following articles:

Releases

No releases published

Packages

No packages published