<commit_before>---
layout: default
title: Documentation sitespeed.io 9.x
description: Read about all you can do with sitespeed.io.
keywords: tools, documentation, web performance
nav: documentation
category: sitespeed.io
image: https://www.sitespeed.io/img/sitespeed-2.0-twitter.png
twitterdescription: Documentation for sitespeed.io.
---

# Documentation v9

<img src="{{site.baseurl}}/img/logos/sitespeed.io.png" class="pull-right img-big" alt="sitespeed.io logo" width="200" height="214">

Sitespeed.io is the complete toolbox to test the web performance of your web site. Use it to monitor your performance or checkout how your competition is doing. You can see all the latest changes in the [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for the project.

## Start
 * [Introduction](introduction/) - start here if you are new to the project or web performance testing.
 * [Installation](installation/) - install using npm, yarn or run our Docker containers.
 * [Browsers](browsers/) - collect timings using real browsers. We support Firefox, Chrome and Chrome on Android.
 * [Configuration](configuration/) - there's a lot of things you can do with sitespeed.io, lets checkout how!
 * [Connectivity](connectivity/) - set the connectivity to emulate real users network conditions.
 * [Docker](docker/) - how to use our Docker containers.
 * [F.A.Q and Best Practice](best-practice/) - here we keep track of questions we get in Slack.
 * [Scripting](scripting/) - test a user journey, test multiple URLs, test login, test adding items to the cart with scripting.

## More details
 * [Alerts](alerts/) - send alerts (email/Slack/PagerDuty etc) when you get a performance regression.
 * [Continuous Integration](continuous-integration/) - generate JUnit XML/TAP and use Jenkins, Circle CI, Gitlab CI, Github Actions, Grunt or the Gulp plugin.
 * [CPU](cpu/) - measure CPU metrics to see where your page spends the time.
 * [Developers](developers/) - start here when you want to do PRs or create a plugin.
 * [Graphite](graphite/) - how to configure and store your metrics in Graphite (and using StatsD).
 * [How to Write a Good Bug Report](bug-report/) - if you write a good bug report, we can spend more time helping you fixing the problem instead of asking you questions
 * [Lighthouse](lighthouse/) - run Lighthouse and Google PageSpeed Insights from sitespeed.io.
 * [Metrics](metrics/) - configure which metrics you want to use.
 * [Mobile phones](mobile-phones/) - test using your mobile phone (Android only).
 * [Performance Budget](performance-budget/) - make sure you are within your performance budget.
 * [Performance Dashboard](performance-dashboard/) - keep track of your metrics and performance.
 * [Performance Leaderboard](leaderboard/) - compare your pages with your competition.
 * [Plugins](plugins/) - list/disable/enable or create your own plugin.
 * [Pre/post scripting](prepostscript/) - run Selenium scripts before/after you test a URL.
 * [Setup S3](s3/) - how to setup S3 for your html result/videos and screenshots.
 * [Setup GCS](gcs/) - how to setup Google Cloud storage (GCS) for your html result/videos and screenshots.
 * [Single Page Application](spa/) - how to test your single page application.
 * [Third party requests](thirdparty/) - keep track of those 3rd party scripts.
 * [Video](video/) - all that you can do with the video and filmstrip.
 * [WebPageReplay](webpagereplay/) - WebPageReplay is proxy that first records your web site and then replay it locally. That can help you find performance regression in the front-end code easier: Latency/server timings are constant.
 * [WebPageTest](webpagetest/) - drive WebPageTest and fetch metrics and graph them.
<commit_msg>docs: show dashboard/leaderboard higher up in the docs #2443<commit_after>---
layout: default
title: Documentation sitespeed.io 9.x
description: Read about all you can do with sitespeed.io.
keywords: tools, documentation, web performance
nav: documentation
category: sitespeed.io
image: https://www.sitespeed.io/img/sitespeed-2.0-twitter.png
twitterdescription: Documentation for sitespeed.io.
---

# Documentation v9

<img src="{{site.baseurl}}/img/logos/sitespeed.io.png" class="pull-right img-big" alt="sitespeed.io logo" width="200" height="214">

Sitespeed.io is the complete toolbox to test the web performance of your web site. Use it to monitor your performance or checkout how your competition is doing. You can see all the latest changes in the [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for the project.

## Start
 * [Introduction](introduction/) - start here if you are new to the project or web performance testing.
 * [Installation](installation/) - install using npm, yarn or run our Docker containers.
 * [Browsers](browsers/) - collect timings using real browsers. We support Firefox, Chrome and Chrome on Android.
 * [Configuration](configuration/) - there's a lot of things you can do with sitespeed.io, lets checkout how!
 * [Connectivity](connectivity/) - set the connectivity to emulate real users network conditions.
 * [Docker](docker/) - how to use our Docker containers.
 * [F.A.Q and Best Practice](best-practice/) - here we keep track of questions we get in Slack.
 * [Performance Dashboard](performance-dashboard/) - monitor your web site and keep track of your metrics and performance.
 * [Performance Leaderboard](leaderboard/) - compare your pages with your competition.
 * [Scripting](scripting/) - test a user journey, test multiple URLs, test login, test adding items to the cart with scripting.

## More details
 * [Alerts](alerts/) - send alerts (email/Slack/PagerDuty etc) when you get a performance regression.
 * [Continuous Integration](continuous-integration/) - generate JUnit XML/TAP and use Jenkins, Circle CI, Gitlab CI, Github Actions, Grunt or the Gulp plugin.
 * [CPU](cpu/) - measure CPU metrics to see where your page spends the time.
 * [Developers](developers/) - start here when you want to do PRs or create a plugin.
 * [Graphite](graphite/) - how to configure and store your metrics in Graphite (and using StatsD).
 * [How to Write a Good Bug Report](bug-report/) - if you write a good bug report, we can spend more time helping you fixing the problem instead of asking you questions
 * [Lighthouse](lighthouse/) - run Lighthouse and Google PageSpeed Insights from sitespeed.io.
 * [Metrics](metrics/) - configure which metrics you want to use.
 * [Mobile phones](mobile-phones/) - test using your mobile phone (Android only).
 * [Performance Budget](performance-budget/) - make sure you are within your performance budget.
 * [Plugins](plugins/) - list/disable/enable or create your own plugin.
 * [Pre/post scripting](prepostscript/) - run Selenium scripts before/after you test a URL.
 * [Setup S3](s3/) - how to setup S3 for your html result/videos and screenshots.
 * [Setup GCS](gcs/) - how to setup Google Cloud storage (GCS) for your html result/videos and screenshots.
 * [Single Page Application](spa/) - how to test your single page application.
 * [Third party requests](thirdparty/) - keep track of those 3rd party scripts.
 * [Video](video/) - all that you can do with the video and filmstrip.
 * [WebPageReplay](webpagereplay/) - WebPageReplay is proxy that first records your web site and then replay it locally. That can help you find performance regression in the front-end code easier: Latency/server timings are constant.
 * [WebPageTest](webpagetest/) - drive WebPageTest and fetch metrics and graph them.

{'fraction_non_alphanumeric': 0.09708096684718003, 'fraction_numerical': 0.004226654338924845, 'mean_word_length': 4.351236749116608, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 4, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3386543', 'n_tokens_mistral': 2113, 'n_tokens_neox': 2019, 'n_words': 913}