Move from master to main (#3036)

.github/PULL_REQUEST_TEMPLATE.md

@@ -4,7 +4,7 @@ Please review the [guidelines for contributing](CONTRIBUTING.md) to this reposit
 - [ ] I'm making a big change or adding functionality so I've already opened an issue proposing the change to other contributors, so I got feedback on the idea before took the time to write precious code
 - [ ] Check that your change/fix has corresponding unit tests (if applicable)
 - [ ] Squash commits so it looks sane
-- [ ] Update the documentation https://github.com/sitespeedio/sitespeed.io/tree/master/docs in another PR
+- [ ] Update the documentation https://github.com/sitespeedio/sitespeed.io/tree/main/docs in another PR
 - [ ] Verify that the test works by running `npm test` and test linting by `npm run lint`
 
 

.github/workflows/docker.yml

@@ -2,10 +2,10 @@ name: Docker
 on:
   push:
     branches:
-    - master
+    - main
   pull_request:
     branches:
-    - master
+    - main
 jobs:
   build:
     runs-on: ubuntu-latest

.github/workflows/linux.yml

@@ -2,10 +2,10 @@ name: Linux browsers
 on:
   push:
     branches:
-    - master
+    - main
   pull_request:
     branches:
-    - master
+    - main
 jobs:
   build:
     runs-on: ubuntu-latest

.github/workflows/safari.yml

@@ -2,10 +2,10 @@ name: OSX Safari
 on:
   push:
     branches:
-    - master
+    - main
   pull_request:
     branches:
-    - master
+    - main
 jobs:
   build:
     runs-on: macos-latest

.github/workflows/unittests.yml

@@ -2,10 +2,10 @@ name: Unit tests
 on:
   push:
     branches:
-    - master
+    - main
   pull_request:
     branches:
-    - master
+    - main
 jobs:
   build:
     runs-on: ubuntu-latest

.github/workflows/windows.yml

@@ -2,10 +2,10 @@ name: Windows Edge
 on:
   push:
     branches:
-    - master
+    - main
   pull_request:
     branches:
-    - master
+    - main
 jobs:
   build:
     runs-on: windows-latest

CHANGELOG.md

@@ -2,7 +2,7 @@
 
 ## 13.3.0 - 2020-06-04
 ### Added
-* Updated to [Browsertime 8.14.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#8140---2020-06-03) that fixes broken MS Edge support.
+* Updated to [Browsertime 8.14.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#8140---2020-06-03) that fixes broken MS Edge support.
 
 ### Fixed
 * Support the old budget format too in JUnit and Tap [#3022](https://github.com/sitespeedio/sitespeed.io/pull/3022)
@@ -25,7 +25,7 @@
 
 ## 13.0.2 - 2020-05-27
 ### Fixed
-* Updated to [Browsertime 8.13.1](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#8131---2020-05-26)
+* Updated to [Browsertime 8.13.1](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#8131---2020-05-26)
 * Make sure errors from the CLI logs errors with "Error:" which makes it easier to act on errors in the log [#3013](https://github.com/sitespeedio/sitespeed.io/pull/3013)
 
 ## 13.0.1 - 2020-05-25
@@ -38,9 +38,9 @@
 * Show the Browsertime xvfb parameters in the CLI help [#3003](https://github.com/sitespeedio/sitespeed.io/pull/3003)
 * Generic cleanup to make sure we show FCP/LCP/CLS where we show metrics and converted the old layout shift to cumulative layout shift [#3004](https://github.com/sitespeedio/sitespeed.io/pull/3004)
 * Upgraded to Chromedriver 83 and Chrome 83 in the Docker container.
-* Upgraded to [Browsertime 8.13.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#8130---2020-05-19).
+* Upgraded to [Browsertime 8.13.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#8130---2020-05-19).
 * The +1 container now uses Lighthouse 6.0.0.
-* Upgraded to Grafana 7.0.0 and [updated dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker) to the new layout (and a NEW [plus1 dashboard](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/master/dashboards/graphite/Plus1.json) with metrics from GPSI and Lighthouse).
+* Upgraded to Grafana 7.0.0 and [updated dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker) to the new layout (and a NEW [plus1 dashboard](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/main/dashboards/graphite/Plus1.json) with metrics from GPSI and Lighthouse).
 
 ### Fixed
 * Better guards for missing WebPageTest first view data [#3002](https://github.com/sitespeedio/sitespeed.io/pull/3002)
@@ -66,7 +66,7 @@
 Some time ago we got [a tweet](https://twitter.com/robnavrey/status/1258063125242314755) about adding the Web Vitals to sitespeed.io. The thing is we always add new metrics as soon as they arrive in Chrome/Firefox/Edge or Safari, so we had those metrics for months. But maybe we don't make it easy for people to see them? We have refactored how we show metrics in the HTML and the CLI output to make it easier for you!
 
 ### Added
-* Upgraded to [Browsertime 8.12.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#8120---2020-05-12):
+* Upgraded to [Browsertime 8.12.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#8120---2020-05-12):
   * Run tests with Safari Technology Preview using `--safari.useTechnologyPreview`
   * Make it possible to enable Safe Browsing and Tracking protection for Firefox. Fireefox precerences was messed up before. Set `--firefox.disableSafeBrowsing false --firefox.disableTrackingProtection false` and let the browser settle for 30 seconds to download the lists and they are enabled. In the future we want it to be enabled by default [#1272](https://github.com/sitespeedio/browsertime/pull/1272).
   * Output TBT, CLS and TTFB in the CLI summary when availible [#1276](https://github.com/sitespeedio/browsertime/pull/1276) and per run. Also unify how we output metrics from thee CLI [#1277](https://github.com/sitespeedio/browsertime/pull/1277)
@@ -87,7 +87,7 @@ Some time ago we got [a tweet](https://twitter.com/robnavrey/status/125806312524
 ## 12.8.1 - 2020-05-05
 ### Fixed
 * Reverted to Python 2 in the Docker container to make TSProxy work again.
-* Upgraded to [Browsertime 8.9.1](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#891---2020-05-05) that many font issues in the video on Android devices.
+* Upgraded to [Browsertime 8.9.1](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#891---2020-05-05) that many font issues in the video on Android devices.
 
 ## 12.8.0 - 2020-05-01
 ### Added
@@ -101,13 +101,13 @@ Some time ago we got [a tweet](https://twitter.com/robnavrey/status/125806312524
 ### Fixed
 * 12.7.0 broke sending groups when you used URL alias. Fixed in [#2973](https://github.com/sitespeedio/sitespeed.io/pull/2973).
 * Correctly send messages on html.finished message, thank you [Erick Wilder](https://github.com/erickwilder) for the PR[#2971](https://github.com/sitespeedio/sitespeed.io/pull/2971).
-* Updated to [Browsertime 8.8.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#880---2020-04-29) that fixes the Firefox error that sometimes happend introduced in 8.7.0.
+* Updated to [Browsertime 8.8.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#880---2020-04-29) that fixes the Firefox error that sometimes happend introduced in 8.7.0.
 
 ## 12.7.0 - 2020-04-27
 ### Added
 * Use loadEventEnd for budget, summary box and page summary [#2969](https://github.com/sitespeedio/sitespeed.io/pull/2969).
 * Configurable group names. Use `--groupAlias` to assing an alias to a group (that is used in Graphite/InfluxDB). Use one alias per URL. [#2964](https://github.com/sitespeedio/sitespeed.io/pull/2964)
-* Upgraded to [Browsertime 8.7.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#870---2020-04-24):
+* Upgraded to [Browsertime 8.7.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#870---2020-04-24):
   * Fixed typo in an error message of click.js, fixed in [#1246](https://github.com/sitespeedio/browsertime/pull/1246), thank you [petemyron](https://github.com/petemyron).
   * Mouse focus on element won't be lost at script measurement start, fixed in [#1248](https://github.com/sitespeedio/browsertime/pull/1248). Thank you [Icecold777](https://github.com/Icecold777).
   * With the great merge of Mozillas changes I've missed to make sure the result.json wasn't bloated. [Gregory Mierzwinski](https://github.com/gmierz) fixed this in [#1252](https://github.com/sitespeedio/browsertime/pull/1252) making sure a lot of Firefox internal data isn't included by default. You can still enable that with `--firefox.appconstants`.
@@ -118,7 +118,7 @@ Some time ago we got [a tweet](https://twitter.com/robnavrey/status/125806312524
 
 ## 12.6.0 - 2020-04-21
 ### Added
-* Updated to Browsertime 8.6.1 (from 8.5.0) and upgraded the main Docker container to use Ubuntu 20.04 and Python 3. Browsertime also includes [a couple of bug fixes](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#861---2020-04-16) when running Chrome on Android.
+* Updated to Browsertime 8.6.1 (from 8.5.0) and upgraded the main Docker container to use Ubuntu 20.04 and Python 3. Browsertime also includes [a couple of bug fixes](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#861---2020-04-16) when running Chrome on Android.
 
 ## 12.5.1 - 2020-04-09
 ### Fixed
@@ -132,12 +132,12 @@ Some time ago we got [a tweet](https://twitter.com/robnavrey/status/125806312524
 
 ## 12.4.0 - 2020-04-06
 ### Added
-* Updated to [Browsertime 8.4.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#840---2020-04-03).
+* Updated to [Browsertime 8.4.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#840---2020-04-03).
 
 ## 12.3.1 - 2020-03-26
 ### Fixed
 * Catch URLs that uses U+2013 that breaks Graphite [#2943](https://github.com/sitespeedio/sitespeed.io/pull/2943)
-* Upgrade to [Browsertime 8.3.1](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#831---2020-03-26).
+* Upgrade to [Browsertime 8.3.1](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#831---2020-03-26).
 
 ## 12.3.0 - 2020-03-23
 ### Fixed
@@ -150,7 +150,7 @@ Some time ago we got [a tweet](https://twitter.com/robnavrey/status/125806312524
 ### Fixed 
 * Remove videoRecordingStart from the summary [#2935](https://github.com/sitespeedio/sitespeed.io/pull/2935).
 * Show CPU geckorprofile link only when you run Firefox [#2931](https://github.com/sitespeedio/sitespeed.io/pull/2931).
-* Upgraded to [Browsertime 8.3.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#830---2020-03-20).
+* Upgraded to [Browsertime 8.3.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#830---2020-03-20).
 
 ## 12.2.2 - 2020-03-16
 ### Fixed
@@ -185,11 +185,11 @@ Some time ago we got [a tweet](https://twitter.com/robnavrey/status/125806312524
 
 ## 12.0.1 - 2020-02-07
 ### Fixed
-* Upgraded to [Browsertime 8.0.1](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#801-2020-02-07) that fixes the broken TSProxy issue. Thank you [Kenrick](https://github.com/kenrick95) for reporting and fixing in PR [#1169](https://github.com/sitespeedio/browsertime/pull/1169).
+* Upgraded to [Browsertime 8.0.1](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#801-2020-02-07) that fixes the broken TSProxy issue. Thank you [Kenrick](https://github.com/kenrick95) for reporting and fixing in PR [#1169](https://github.com/sitespeedio/browsertime/pull/1169).
 
 ## 12.0.0 - 2020-02-06
 
-Read about Browsertime 8.0 and sitespeed.io 12.0 in [the blog post](https://www.sitespeed.io/sitespeed.io-12.0-and-browsertime-8.0/) and checkout the [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#800-2020-02-05) to see all the changes!
+Read about Browsertime 8.0 and sitespeed.io 12.0 in [the blog post](https://www.sitespeed.io/sitespeed.io-12.0-and-browsertime-8.0/) and checkout the [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#800-2020-02-05) to see all the changes!
 
 ### Added
 * Browsertime 8.0.0 - this is an massive update with a lot of new things!
@@ -323,7 +323,7 @@ Read about Browsertime 8.0 and sitespeed.io 12.0 in [the blog post](https://www.
 * The timestamp on the page summary was wrong: it showed when all tests started instead of the time of the first run as reported in [#2766](https://github.com/sitespeedio/sitespeed.io/issues/2766) and fixed in [#2768](https://github.com/sitespeedio/sitespeed.io/pull/2768).
 * If uploading to S3 or GCS fails, the exit code will be an error and you can see that it failed in the HTML [#2774](https://github.com/sitespeedio/sitespeed.io/pull/2774).
 * A safer check when generating pages HTML page if something went wrong earlier in the run [#2778](https://github.com/sitespeedio/sitespeed.io/pull/2778)
-* Upgraded to [Browsertime 7.0.2](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#702---2019-11-13)
+* Upgraded to [Browsertime 7.0.2](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#702---2019-11-13)
 
 ## 11.0.0 -  2019-11-07
 ### Changed
@@ -340,7 +340,7 @@ Read about Browsertime 8.0 and sitespeed.io 12.0 in [the blog post](https://www.
 * Upgraded to Axe Core 3.4.0 [#2723](https://github.com/sitespeedio/sitespeed.io/pull/2723).
 * Added contentSize to budget [#2721](https://github.com/sitespeedio/sitespeed.io/pull/2721).
 * You can now configure which summary boxes (which metric) you can see on the start page. Thank you [thapasya-m](https://github.com/thapasya-m) for the PR [#2736](https://github.com/sitespeedio/sitespeed.io/pull/2736)!
-* Upgraded to [Browsertime 7.0.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#700---2019-11-02):
+* Upgraded to [Browsertime 7.0.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#700---2019-11-02):
   * Changed a couple of Firefox settings to follow the Mozilla teams downstream version [#965](https://github.com/sitespeedio/browsertime/pull/965).
   * Added Contentful speed index is a new SI metric developed by Bas Schouten at Mozilla which uses edge detection to calculate the amount of "content" that is visible on each frame, thank you [dpalmeiro](https://github.com/dpalmeiro) for the PR [#976](https://github.com/sitespeedio/browsertime/pull/976).
   * Firefox 67 and above has a built-in window recorder ([bug 1536174](https://bugzilla.mozilla.org/show_bug.cgi?id=1536174)) that is able to dump PNG images of each frame that is painted to the window. This can be enabled and disabled in the browser console, or through the chrome context with selenium webdriver. This PR introduces a new privileged API that is able to execute JS in the chrome context, as well as support for generating a variable rate MP4 using the output images from the window recorder. The motivation for this work was to introduce a low-overhead video recorder that will not introduce performance disturbances during page loads. Thank you [dpalmeiro](https://github.com/dpalmeiro) for the PR [#978](https://github.com/sitespeedio/browsertime/pull/978). You can try it out with `--video --firefox.windowRecorder`
@@ -385,7 +385,7 @@ to run Axe! [#2676](https://github.com/sitespeedio/sitespeed.io/pull/2676).
 * Set correct tag for CPU Long Tasks in InfluxDB [#2677](https://github.com/sitespeedio/sitespeed.io/pull/2677)
 * Handle float numbers in statistics, thank you [tengremlin](https://github.com/tengremlin) for the PR [#2675](https://github.com/sitespeedio/sitespeed.io/pull/2675).
 * Upgraded to Yargs 14.2.0 that fixes so you can extend config.json files in multiple steps. Before only on step worked.
-* Upgraded to Browsertime [6.1.3](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#browsertime-changelog) that fixes the TSProxy bug.
+* Upgraded to Browsertime [6.1.3](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#browsertime-changelog) that fixes the TSProxy bug.
 * Testing localhost broke the third party plugins. Fixed in the new Coach and in sitespeed.io [#2689](https://github.com/sitespeedio/sitespeed.io/pull/2689).
 * Upgraded to the Coach 4.0.2.
 
@@ -403,7 +403,7 @@ to run Axe! [#2676](https://github.com/sitespeedio/sitespeed.io/pull/2676).
   * Removed settings for enabling LayoutInstabilityAPI in Chrome (is on by default in Chrome 77) [#949](https://github.com/sitespeedio/browsertime/pull/949.
   * Fixed a bug for Chrome when you couldn't send more that one request header [#950](https://github.com/sitespeedio/browsertime/pull/950).
   * Empty long task after you collect them.
-* Updated dashboards: New WebPageTest dashboard showing standartd deviation: https://github.com/sitespeedio/grafana-bootstrap-docker/blob/master/dashboards/graphite/WebPageTestDeviation.json and updated page timing metrics dashboard for sitespeed.io so you can just use the drowdown to see the standard deviation for different metrics https://github.com/sitespeedio/grafana-bootstrap-docker/blob/master/dashboards/graphite/PageTimingMetrics.json
+* Updated dashboards: New WebPageTest dashboard showing standartd deviation: https://github.com/sitespeedio/grafana-bootstrap-docker/blob/main/dashboards/graphite/WebPageTestDeviation.json and updated page timing metrics dashboard for sitespeed.io so you can just use the drowdown to see the standard deviation for different metrics https://github.com/sitespeedio/grafana-bootstrap-docker/blob/main/dashboards/graphite/PageTimingMetrics.json
 
 ##  10.0.3 - 2019-09-24
 ### Fixed
@@ -426,7 +426,7 @@ to run Axe! [#2676](https://github.com/sitespeedio/sitespeed.io/pull/2676).
 
 ## 10.0.1 - 2019-09-12
 ### Fixed
-* Updated Browsetime with stable ChromeDriver (instead of beta), do not show First Paint for Safari, and fixing getting long task data if you first navigate and then measure a URL. See the [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#601---2019-09-12) for all the info.
+* Updated Browsetime with stable ChromeDriver (instead of beta), do not show First Paint for Safari, and fixing getting long task data if you first navigate and then measure a URL. See the [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#601---2019-09-12) for all the info.
 
 ## 10.0.0 - 2019-09-11
 ### Added
@@ -439,7 +439,7 @@ to run Axe! [#2676](https://github.com/sitespeedio/sitespeed.io/pull/2676).
 * Limited support for using Safari. You need Catalina + iOS 13 to run Safari on your phone/tablet. Read more in the [documentation](https://www.sitespeed.io/documentation/sitespeed.io/browsers/#safari).
 * Send FirstMeaningfulPaint by default to Graphite/InfluxDb [#2559](https://github.com/sitespeedio/sitespeed.io/pull/2559)
 * [Updated dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker) with a new annotation (for sitespeed.io changes) and fixed WebPageTest dashboards to work with annotations.
-* Upgraded to [Browsertime 6.0.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md).
+* Upgraded to [Browsertime 6.0.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md).
   * Upgraded to Ubuntu Disco in the Docker container [#908](https://github.com/sitespeedio/browsertime/pull/908).
   * Use [TSProxy](https://github.com/WPO-Foundation/tsproxy) to throttle the connection. You should use TSProxy when you run on Kubernetes. Use it by `--connectivity.engine tsproxy`. We used to have support years ago but it never worked good on Mac/Linux so we dropped it. But it works now so we added it back [#891](https://github.com/sitespeedio/browsertime/pull/891).
   * You can now add your own metrics directly from your script (or post script) using *context.result.extras*. More info coming [#917](https://github.com/sitespeedio/browsertime/pull/917)
@@ -480,14 +480,14 @@ to run Axe! [#2676](https://github.com/sitespeedio/sitespeed.io/pull/2676).
 
 ## 9.7.0 - 2019-07-29
 
-In this release we moved functionality for Chrome from our [browser extension](https://github.com/sitespeedio/browsertime-extension) to the devtools protocol instead, so that the same functionality also works in Chrome on Android. Read the [changelog for Browsertime for all changes](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#560----2019-07-27).
+In this release we moved functionality for Chrome from our [browser extension](https://github.com/sitespeedio/browsertime-extension) to the devtools protocol instead, so that the same functionality also works in Chrome on Android. Read the [changelog for Browsertime for all changes](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#560----2019-07-27).
 
 ### Fixed
 * You can now use `--android` to run tests on Android phones (the same way as on Browsertime) [#2544](https://github.com/sitespeedio/sitespeed.io/pull/2544).
 
 ### Added
 * Upgraded to third-party-web 0.10.1.
-* Upgraded to Browsertime [5.6.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#560----2019-07-27) and [5.6.1](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#561----2019-07-28).
+* Upgraded to Browsertime [5.6.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#560----2019-07-27) and [5.6.1](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#561----2019-07-28).
 
 ##  9.6.0 - 2019-07-11
 ### Added
@@ -514,7 +514,7 @@ In this release we moved functionality for Chrome from our [browser extension](h
 
 ## 9.4.0 - 2019-06-29
 ### Added
-* Upgraded to [Browsertime 3.4.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#530---2019-06-29) with the following fixes:
+* Upgraded to [Browsertime 3.4.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#530---2019-06-29) with the following fixes:
   * Added support for `--injectJs` using Chrome [#864](https://github.com/sitespeedio/browsertime/pull/864).
   * Use CDP to set request headers for Chrome (instead of the Browsertime extension). This enables adding extra headers for Chrome on Android and fixes [#2520](https://github.com/sitespeedio/sitespeed.io/issues/2520). Fixed in [#867](https://github.com/sitespeedio/browsertime/pull/867).
 * Report JS heap size by deafult for Chrome to Graphite/InfluxDb [#2524](https://github.com/sitespeedio/sitespeed.io/pull/2524)
@@ -574,7 +574,7 @@ In this release we moved functionality for Chrome from our [browser extension](h
 ## 9.2.0 - 2019-06-01
 
 ### Added
-* The config file `--config` now supports extending other config files. Read [yargs documentation](https://github.com/yargs/yargs/blob/master/docs/api.md#extends-keyword) for how to use the extends keyword. Add `"extends":"/default.json"` to extend your config file named *default.json* file. One thing: The configuration files are merged and the extended ones keys are overriden if they exist in your configuration. This is upstream thing but maybe we can fix that in the future.
+* The config file `--config` now supports extending other config files. Read [yargs documentation](https://github.com/yargs/yargs/blob/main/docs/api.md#extends-keyword) for how to use the extends keyword. Add `"extends":"/default.json"` to extend your config file named *default.json* file. One thing: The configuration files are merged and the extended ones keys are overriden if they exist in your configuration. This is upstream thing but maybe we can fix that in the future.
 
 ### Fixed
 * Updated Browsertime to 5.1.3 that goes back to use default Selenium 3.6 (without CDP supports) and with CDP support implemented on the side. Also updated Coach with the latest Browsertime.
@@ -602,7 +602,7 @@ Using CPU metrics on Android phones was broken since 9.0.0, fixed in [#844](http
 ## 9.0.0 - 2019-05-21
 
 ### Added
-* Upgraded to [Browsertime 5.0.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#500---2019-05-16).
+* Upgraded to [Browsertime 5.0.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#500---2019-05-16).
 
 * Collect CPU long tasks in Chrome using `--chrome.collectLongTasks` using the [Long Task API](https://developer.mozilla.org/en-US/docs/Web/API/Long_Tasks_API). For the long tasks to work, we inject JS using the *Page.addScriptToEvaluateOnNewDocument* devtools command. We collect all long tasks and related data (not so much at the moment but will get better/more useful information when browsers supports it) and count the total number of long tasks, long tasks that happens before first paint and first contentful paint. Implemented in [#821](https://github.com/sitespeedio/browsertime/pull/821) and [#825](https://github.com/sitespeedio/browsertime/pull/825).
 
@@ -664,12 +664,12 @@ Using CPU metrics on Android phones was broken since 9.0.0, fixed in [#844](http
 
 * Upgraded to third-party-web 0.6.1 that includes more domains.
 
-* Upgrading to [Browsertime 4.7.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#470---2019-04-21) adds three new things to scripting:
+* Upgrading to [Browsertime 4.7.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#470---2019-04-21) adds three new things to scripting:
   * You can add your own error `commands.error(message)`. The error will be attached to the latest tested page. Say that you have a script where you first measure a page and then want to click on a specific link and the link doesn't exist. Then you can attach your own error with your own error text. The error will be sent to your datasource and will be visible in the HTML result.
 
   * You can add meta data to your script with `commands.meta.setTitle(title)` and `commands.meta.setDescription(desc)`
 
-* Upgrading to [Browsertime 4.8.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#480---2019-04-23) fixes so errors thrown from your script, holds a usable error message instead of the wrapped ChromeDriver error.
+* Upgrading to [Browsertime 4.8.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#480---2019-04-23) fixes so errors thrown from your script, holds a usable error message instead of the wrapped ChromeDriver error.
 
 ### Fixed
 * If a page failed, pug through an error [#2428](https://github.com/sitespeedio/sitespeed.io/pull/2428)
@@ -706,7 +706,7 @@ Using CPU metrics on Android phones was broken since 9.0.0, fixed in [#844](http
 ## 8.11.0 - 2019-04-08
 
 ### Added
-* Upgraded to [Browsertime 4.6.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#460---2019-04-07) that enables the use of [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). We now uses a modified version of Selenium that can use CDP. We also automatically collect the CDP performance metrics *Performance.getMetrics* (you can turn that off with `--chrome.cdp.performance false`). We also enabled raw use of the CDP in scripting: `cdp.sendAndGet(command, args)` and `cdp.send(command, args)` [#2410](https://github.com/sitespeedio/sitespeed.io/pull/2410).
+* Upgraded to [Browsertime 4.6.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#460---2019-04-07) that enables the use of [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). We now uses a modified version of Selenium that can use CDP. We also automatically collect the CDP performance metrics *Performance.getMetrics* (you can turn that off with `--chrome.cdp.performance false`). We also enabled raw use of the CDP in scripting: `cdp.sendAndGet(command, args)` and `cdp.send(command, args)` [#2410](https://github.com/sitespeedio/sitespeed.io/pull/2410).
 
 * Show loadEventEnd in the metrics section and send it to Graphite/Grafana [#2411](https://github.com/sitespeedio/sitespeed.io/pull/2411).
 
@@ -826,7 +826,7 @@ Using CPU metrics on Android phones was broken since 9.0.0, fixed in [#844](http
 ### Fixed
 
 - Upgraded to PageXray 2.5.4 that categorise first party using the actual domain instead of the full URL (as reported by [arunthilak](https://github.com/arunthilak)).
-- Upgraded to [Browsertime 4.4.8](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#448---2019-03-04).
+- Upgraded to [Browsertime 4.4.8](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#448---2019-03-04).
 - Lighthouse audit tag for InfluxDB, thank you [Semyon](https://github.com/SemyonLosmakov) for the PR [#2359](https://github.com/sitespeedio/sitespeed.io/pull/2359)
 - Changed the unused message gc.finished to gcs.finished to work with comming Google Cloud Storage support [#2362](https://github.com/sitespeedio/sitespeed.io/pull/2362)
 
@@ -911,7 +911,7 @@ Using CPU metrics on Android phones was broken since 9.0.0, fixed in [#844](http
 
 - Give your test a name with `--name` [#2302](https://github.com/sitespeedio/sitespeed.io/pull/2302). At the moment only used in the HTML.
 
-- Upgraded to Browsertime [4.4.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#440---2019-02-12):
+- Upgraded to Browsertime [4.4.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#440---2019-02-12):
   - There are two new cache clear commands: cache.clearKeepCookies() and cache.clear() (only working on Desktop) [#769](https://github.com/sitespeedio/browsertime/pull/769).
   - Updated RUM Speed Index to include upstream fix [#766](https://github.com/sitespeedio/browsertime/pull/766).
   - Make sure the body of the page is shown when setting the fullscreen to orange (when recording the video) [#767](https://github.com/sitespeedio/browsertime/pull/767)
@@ -932,13 +932,13 @@ Using CPU metrics on Android phones was broken since 9.0.0, fixed in [#844](http
 
 - Added json as output type for the budget. Set `--budget.output json` and it will store _budgetResult.json_ in your result directory [#2299](https://github.com/sitespeedio/sitespeed.io/pull/2299).
 
-- Upgraded to Browsertime [4.3.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#430-2019-02-10) with new addText.bySelector(text, selector) command + fixed so click.byJs and click.byJsAndWait works on elements that is hidden.
+- Upgraded to Browsertime [4.3.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#430-2019-02-10) with new addText.bySelector(text, selector) command + fixed so click.byJs and click.byJsAndWait works on elements that is hidden.
 
 - Added endpoint to s3 configurations to allow for pushing HTML reports to Digital Ocean's Spaces as it is S3 compatible. [#2072]
 
 ### Fixed
 
-- Upgraded to Browsertime [4.2.6](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#426-2019-02-08) with two fixes:
+- Upgraded to Browsertime [4.2.6](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#426-2019-02-08) with two fixes:
   - Command set value by id was broken, it used to set the value to the id [#761](https://github.com/sitespeedio/browsertime/pull/761).
   - I've missed that for some URLs (as in this [login](https://github.com/sitespeedio/sitespeed.io/issues/2290#issuecomment-461601990) you could have an alias for an URL but the URL was actually slightly different. For example, you login to a site and the login step redirect to a URL and for that URL one value of a GET parameter differs. So with this fix we lock the alias tyo one specific URL. If your URL change and you use an alias, the first variation of the URL will be used [#763](https://github.com/sitespeedio/browsertime/pull/763).
 - Spelling for the script-reader message (was scrtipt-reader).
@@ -947,7 +947,7 @@ Using CPU metrics on Android phones was broken since 9.0.0, fixed in [#844](http
 
 ### Fixed
 
-- Upgraded to Browsertime [4.2.5](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#425---2019-02-06) that hopefully fixes the wrong metrics inserted into the HAR file if you run test multiple pages.
+- Upgraded to Browsertime [4.2.5](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#425---2019-02-06) that hopefully fixes the wrong metrics inserted into the HAR file if you run test multiple pages.
 
 ## 8.2.2 2019-02-05
 
@@ -959,13 +959,13 @@ Using CPU metrics on Android phones was broken since 9.0.0, fixed in [#844](http
 
 ### Fixed
 
-- New Browsertime [4.2.4](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#424---2019-02-04) with fixed bug for commands set.innerHtml and click.byXpath.
+- New Browsertime [4.2.4](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#424---2019-02-04) with fixed bug for commands set.innerHtml and click.byXpath.
 
 ## 8.2.0 2019-02-04
 
 ### Added
 
-- New Browsertime [4.2.3](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md) with:
+- New Browsertime [4.2.3](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md) with:
   - Fixed so that `js.run()` returns whatever it gets back so you can script and get whatever you need from your page [#749](https://github.com/sitespeedio/browsertime/pull/749).
   - New help command **set** to set innerHtml, innerText and value of element. [#750](https://github.com/sitespeedio/browsertime/pull/750).
   - Added click.bySelector and rewrote most of click methods to use plain JavaScript instead of Selenium (so it will work on hidden elements) [#751](https://github.com/sitespeedio/browsertime/pull/751).
@@ -986,7 +986,7 @@ Using CPU metrics on Android phones was broken since 9.0.0, fixed in [#844](http
 - New tab showing the filmstrip (if you record a video and keep the screenshots). We had the screenshots forever but never done anything with them. Inspired by [Stefan Burnickis](https://github.com/sburnicki) work on https://github.com/iteratec/wpt-filmstrip [#2274](https://github.com/sitespeedio/sitespeed.io/pull/2274).
 - Show Server Timings in the metric section (if the page uses Server Timing) [#2277](https://github.com/sitespeedio/sitespeed.io/pull/2277).
 - Upgraded the Docker container to use Chrome 72 and Firefox 65.
-- Upgraded to [Browsertime 4.1](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#410---2019-01-31) with latest ChromeDriver and Geckodriver. There's also a new command `js.runAndWait('')` that makes it possible to run your own JavaScript, click a link and wait on page navigation.
+- Upgraded to [Browsertime 4.1](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#410---2019-01-31) with latest ChromeDriver and Geckodriver. There's also a new command `js.runAndWait('')` that makes it possible to run your own JavaScript, click a link and wait on page navigation.
 
 ### Fixed
 
@@ -1046,7 +1046,7 @@ Read the blog post: [https://www.sitespeed.io/sitespeed.io-8.0-and-browsertime.4
 - Use fully loaded metric from the HAR instead of the Resource Timing API [#2242](https://github.com/sitespeedio/sitespeed.io/pull/2242) and [#2244](https://github.com/sitespeedio/sitespeed.io/pull/2244).
 - Group metrics by type in HTML output [#2240](https://github.com/sitespeedio/sitespeed.io/pull/2240)
 - Show timing metrics in ms/s (instead of just ms) [#2245](https://github.com/sitespeedio/sitespeed.io/pull/2245)
-- Use Browsertime 4.0 that adds support for testing Single Page Applications and test multiple pages with scripting. See the [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#400-beta1---2019-01-14) [#2236](https://github.com/sitespeedio/sitespeed.io/pull/2236)
+- Use Browsertime 4.0 that adds support for testing Single Page Applications and test multiple pages with scripting. See the [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#400-beta1---2019-01-14) [#2236](https://github.com/sitespeedio/sitespeed.io/pull/2236)
 - There's a new and simpler way of setting up a budget file [#2252](https://github.com/sitespeedio/sitespeed.io/pull/2252) and [#2253](https://github.com/sitespeedio/sitespeed.io/pull/2253)
 
 ### Fixed
@@ -1103,7 +1103,7 @@ Read the blog post: [https://www.sitespeed.io/sitespeed.io-8.0-and-browsertime.4
 
 ### Fixed
 
-- New [Browsertime 3.8.2](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#382) that finally fixes the problem for Firefox introduced in 7.6.0.
+- New [Browsertime 3.8.2](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#382) that finally fixes the problem for Firefox introduced in 7.6.0.
 
 ## 7.6.1 - 2018-10-15
 
@@ -1115,7 +1115,7 @@ Read the blog post: [https://www.sitespeed.io/sitespeed.io-8.0-and-browsertime.4
 
 ### Added
 
-- Upgraded to [Browsertime 3.8.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#380---2018-10-15). The new version changes how the change happen bewteen preURL/preScript and the URL being tested. Before we automatically turned the screen white between pre runs and the URL. Now we do not do that. The metrics will be the same but when you look at the video, it will start with the pre URL instead of a white screen. This fixes bugs like [#2091](https://github.com/sitespeedio/sitespeed.io/issues/2091) where routing through hash wasn't getting the right first visual change (and other bugs).
+- Upgraded to [Browsertime 3.8.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#380---2018-10-15). The new version changes how the change happen bewteen preURL/preScript and the URL being tested. Before we automatically turned the screen white between pre runs and the URL. Now we do not do that. The metrics will be the same but when you look at the video, it will start with the pre URL instead of a white screen. This fixes bugs like [#2091](https://github.com/sitespeedio/sitespeed.io/issues/2091) where routing through hash wasn't getting the right first visual change (and other bugs).
 
 ## 7.5.2 - 2018-10-12
 
@@ -1173,7 +1173,7 @@ Read the blog post: [https://www.sitespeed.io/sitespeed.io-8.0-and-browsertime.4
 
 - We updated to PageXray 2.4.0 that correctly pick up mime types for video/audio/xml and pdf (that was missed before).
 
-- Updated to [Coach 2.3.0](https://github.com/sitespeedio/coach/blob/master/CHANGELOG.md) that fixes so that the CSS advice never can be a negative score.
+- Updated to [Coach 2.3.0](https://github.com/sitespeedio/coach/blob/main/CHANGELOG.md) that fixes so that the CSS advice never can be a negative score.
 
 - Fixed the bug that made us show wrong video/screenshot on page summary[#2169](https://github.com/sitespeedio/sitespeed.io/pull/2169). Before we always showed the first screenshot/video. Now we show the median pick (so it correlates to the right waterfall and metrics tab).
 
@@ -1202,7 +1202,7 @@ Read the blog post: [https://www.sitespeed.io/sitespeed.io-8.0-and-browsertime.4
 
 - Updated the CLI to link to how to setup connectivity.
 - Detailed and summary page show wrong metrics if you test on multiple domains [#2134](https://github.com/sitespeedio/sitespeed.io/issues/2134).
-- Updated [fix release](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#331---2018-08-09) of Browsertime that makes the log cleaner and easier to use.
+- Updated [fix release](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#331---2018-08-09) of Browsertime that makes the log cleaner and easier to use.
 
 ## 7.3.5 - 2018-07-29
 
@@ -1264,8 +1264,8 @@ Read the blog post: [https://www.sitespeed.io/sitespeed.io-8.0-and-browsertime.4
 
 - Copy assets first before generating assets, making pages work even if parts fail [#2081](https://github.com/sitespeedio/sitespeed.io/pull/2081).
 - The Docker container uses Firefox 61 stable.
-- Upgraded to [Browsertime 3.1.4](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#314---2018-06-25) including latest Geckodriver.
-- Upgraded the [Coach to 2.0.4](https://github.com/sitespeedio/coach/blob/master/CHANGELOG.md#204---2018-06-25) with a fix that makes sitespeed.io faster when generating the result if you you are using many runs.
+- Upgraded to [Browsertime 3.1.4](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#314---2018-06-25) including latest Geckodriver.
+- Upgraded the [Coach to 2.0.4](https://github.com/sitespeedio/coach/blob/main/CHANGELOG.md#204---2018-06-25) with a fix that makes sitespeed.io faster when generating the result if you you are using many runs.
 
 and Coach 2.0.4.
 
@@ -1313,7 +1313,7 @@ Read more about [sitespeed.io 7.0](https://www.sitespeed.io/sitespeed.io-7.0/).
 - A lot of love for WebPageTest: Bugfix for getting Chrome timing metrics per run [#2046](https://github.com/sitespeedio/sitespeed.io/pull/2046), show the WebPageTests id and tester name in the HTML [#2047](https://github.com/sitespeedio/sitespeed.io/pull/2047), use WebPageTest screenshot if you don't run Browsertime [#2048](https://github.com/sitespeedio/sitespeed.io/pull/2048), show some Lighthouse metrics you use Lighthouse [#2049](https://github.com/sitespeedio/sitespeed.io/pull/2049) and show some of those interactive metrics if they exists [#2050](https://github.com/sitespeedio/sitespeed.io/pull/2050).
 - Link directly to each individual run if you use WebPageTest [#2045](https://github.com/sitespeedio/sitespeed.io/pull/2045).
 - Add StatsD support (with bulking). Thank you [Omri](https://github.com/omrilotan) for the PR [#1994](https://github.com/sitespeedio/sitespeed.io/pull/1994).
-- We upgraded to [Browsertime 3.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#300).
+- We upgraded to [Browsertime 3.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#300).
 - We upgraded the S3 plugin that fixes (all) the problems we have seen with large files failing to upload [#2013](https://github.com/sitespeedio/sitespeed.io/pull/2013).
 - Get console messages from Chrome in the HTML output and send the number of errors to Graphite/InfluxDB by default.
 - You can now change safe char for groups/domain in InfluxDB with --influxdb.groupSeparator. Thank you [amic87](https://github.com/amic81) for your PR!
@@ -1465,7 +1465,7 @@ As a sitespeed.io user there shouldn't be any breaking changes upgrading from 6.
 
 ### Fixed
 
-- Upgraded to Browsertime 2.1.4 with [new bug fixes](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md) and newer ChromeDriver.
+- Upgraded to Browsertime 2.1.4 with [new bug fixes](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md) and newer ChromeDriver.
 
 - Fixed the start script so that you on Ubuntu can run WebPageReplay in the Docker container for your Android phone.
 
@@ -1542,7 +1542,7 @@ As a sitespeed.io user there shouldn't be any breaking changes upgrading from 6.
 ### Fixed
 
 - Remove the unused unminified CSS file from the result [#1835](https://github.com/sitespeedio/sitespeed.io/pull/1835)
-- Updated to Browsertime 2.0.1 with [fixes for Android](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#version-201-2017-11-28).
+- Updated to Browsertime 2.0.1 with [fixes for Android](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#version-201-2017-11-28).
 
 ## 6.0.2 2017-11-28
 
@@ -1614,7 +1614,7 @@ the url would be treated as a plugin name, and the command would fail.
 
 - We have moved the GPSI outside of sitespeed.io and you can find it [here](https://github.com/sitespeedio/plugin-gpsi). To run in along with sitespeed.io you just follow [the instructions how to add a plugin](https://www.sitespeed.io/documentation/sitespeed.io/plugins/#add-a-plugin). We moved it outside of sitespeed.io to make the code base cleaner and with the hope that we can find a maintainer who can give it more love.
 
-- The [StorageManager](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/core/resultsStorage/storageManager.js) API has been updated. The following changes may break code written using the 5.x API:
+- The [StorageManager](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/core/resultsStorage/storageManager.js) API has been updated. The following changes may break code written using the 5.x API:
 
   - `createDataDir(directoryName)` is now `createDirectory(...directoryNames)` and takes any number of directory names (which will be joined together) as arguments.
   - `writeData(filename, data)` has reversed the order of its arguments. It is now `writeData(data, filename)`.
@@ -1640,7 +1640,7 @@ the url would be treated as a plugin name, and the command would fail.
 - When you run sitespeed.io using Docker we now always set no-sandbox to Chrome (so you don't need to do that yourself).
 - Custom metrics in WebPageTest broke the HTML [#1722](https://github.com/sitespeedio/sitespeed.io/issues/1722)
 - Skip storing faulty toplists on disk when using the analysisstorer plugin. The lists is generated from the raw data, so if you need them yourself as JSON, you can generate them [#1721](https://github.com/sitespeedio/sitespeed.io/pull/1721)
-- Upgraded to latest shining [Browsertime](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#version-193-2017-09-29)
+- Upgraded to latest shining [Browsertime](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#version-193-2017-09-29)
 
 ## 5.6.2 2017-09-17
 
@@ -1661,7 +1661,7 @@ the url would be treated as a plugin name, and the command would fail.
 ### Added
 
 - Use load time as of the default metrics for data storage when you use WebPageTest [#1704](https://github.com/sitespeedio/sitespeed.io/issues/1704)
-- Upgraded Browsertime to 1.8.0 with [all these changes](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#version-180-2017-09-13)
+- Upgraded Browsertime to 1.8.0 with [all these changes](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#version-180-2017-09-13)
 
 ### Fixed
 
@@ -1694,7 +1694,7 @@ the url would be treated as a plugin name, and the command would fail.
 ### Fixed
 
 - Upgrading node-sass to work when installing on Windows 10 [#1671](https://github.com/sitespeedio/sitespeed.io/issues/1671)
-- Upgrading to Browsertime 1.5.4 checkout [https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#version-154-2017-07-19](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#version-154-2017-07-19)
+- Upgrading to Browsertime 1.5.4 checkout [https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#version-154-2017-07-19](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#version-154-2017-07-19)
 - Always add the first asset to the size list [#1676](https://github.com/sitespeedio/sitespeed.io/issues/1676)
 
 ## 5.4.3 2017-07-14
@@ -1958,7 +1958,7 @@ There's one change in 5.0 that changes the default behavior: TSProxy isn't defau
 
 ### Fixed (hopefully)
 
-- Upgraded to [Browsertime beta 21](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#version-100-beta21-2017-01-09) to finally once and for all fix the problem with the too early firstVisualChange that sometimes happend in Chrome:
+- Upgraded to [Browsertime beta 21](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#version-100-beta21-2017-01-09) to finally once and for all fix the problem with the too early firstVisualChange that sometimes happend in Chrome:
   - We removed the center cropping of images when visual metrics checks if an image is orange/white. The cropping made us miss the small orange lines that sometimes appear only in Chrome.
   - We also fine tuned (and made configurable) the number when the diff of two images (orange and white) is ... orange.
   - We re-arranged how we record the screen to record as little extra video as possible
@@ -2117,7 +2117,7 @@ There's one change in 5.0 that changes the default behavior: TSProxy isn't defau
   - Export chrome perflog dumps as json in extraJson property of the result, instead of a string in the extras property. Only relevant to api users.
   - Upgraded sltc so we use 0.6.0 with simplified tc that actually works
   - We now run xvfb from inside NodeJS so we can set the screen size, making it easy to record the correct size for VisualMetrics. We also use environment variables that starts with BROWSERTIME so we can turn on xvfb easily on Docker.
-    https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md
+    https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md
 
 ## 4.0.4 2016-11-04
 
@@ -2279,7 +2279,7 @@ And many many more changed. Read about the release https://www.sitespeed.io/site
 - Right CLI parameter name for setting the Selenium URL (if you use a standalone server)
 - Made it easier to understand how to configure location and connectivity for WebPageTest.
 - Fixed breaking GPSI when summary was missing from the rule. #1110
-- Updated browsertime, so when you are running pre/post script, you can get hold of the selenium-webdriver from the context (a lot of people have had problem with it). Checkout https://github.com/sitespeedio/browsertime/blob/master/test/prepostscripts/preLoginExample.js for an example.
+- Updated browsertime, so when you are running pre/post script, you can get hold of the selenium-webdriver from the context (a lot of people have had problem with it). Checkout https://github.com/sitespeedio/browsertime/blob/main/test/prepostscripts/preLoginExample.js for an example.
 - Finally Firefox works again, you can use Firefox 48 since we now use Geckodriver.
 - New version of TSProxy that fixes the redirect problems for HTTP -> HTTPS https://github.com/sitespeedio/browsertime/issues/175
 - New PerfCascade that takes care of responses that misses a content type #1030

CODE_OF_CONDUCT.md

@@ -43,6 +43,6 @@ Anyone asked to stop unacceptable behavior is expected to comply immediately. If
 
 ## Thanks
 
-This code of conduct is based on the [Twitter Code of Conduct](https://github.com/twitter/code-of-conduct/blob/master/code-of-conduct.md) that was based on [Open Code of Conduct](https://github.com/todogroup/opencodeofconduct) from the [TODOGroup](http://todogroup.org).
+This code of conduct is based on the [Twitter Code of Conduct](https://github.com/twitter/code-of-conduct/blob/main/code-of-conduct.md) that was based on [Open Code of Conduct](https://github.com/todogroup/opencodeofconduct) from the [TODOGroup](http://todogroup.org).
 
 We are thankful for their work and all the communities who have paved the way with code of conducts.

Dockerfile

@@ -36,7 +36,7 @@ ADD docker/adb/insecure_shared_adbkey /root/.android/adbkey
 ADD docker/adb/insecure_shared_adbkey.pub /root/.android/adbkey.pub
 
 # Allow all users to run commands needed by sitespeedio/throttle via sudo
-# See https://github.com/sitespeedio/throttle/blob/master/lib/tc.js
+# See https://github.com/sitespeedio/throttle/blob/main/lib/tc.js
 RUN echo 'ALL ALL=NOPASSWD: /usr/sbin/tc, /usr/sbin/route, /usr/sbin/ip' > /etc/sudoers.d/tc
 
 ENTRYPOINT ["/start.sh"]

Dockerfile-slim

@@ -35,7 +35,7 @@ WORKDIR /usr/src/app
 COPY docker/scripts/start-slim.sh /start.sh
 
 # Allow all users to run commands needed by sitespeedio/throttle via sudo
-# See https://github.com/sitespeedio/throttle/blob/master/lib/tc.js
+# See https://github.com/sitespeedio/throttle/blob/main/lib/tc.js
 RUN echo 'ALL ALL=NOPASSWD: /usr/sbin/tc, /usr/sbin/route, /usr/sbin/ip' > /etc/sudoers.d/tc
 
 ENTRYPOINT ["bash","/start.sh"]

HELP.md

@@ -8,10 +8,10 @@ We love to have more people involved in improving sitespeed.io. We are constantl
 As a designer there's a lot you can do: You can help us improve the HTML result pages. Maybe we should restructure the metrics  ? Or could the header/footer look better? You could also have look at [https://www.sitespeed.io](https://www.sitespeed.io/) where we have all the documentation. You can pretty much help us with everything, no one in the core team got design skills :)
 
 ## Documentation
-Documentation is fun and it is the core of making sitespeed.io easy to use. We got a [special documentation tag for issues](https://github.com/sitespeedio/sitespeed.io/issues?q=is%3Aissue+is%3Aopen+label%3Adocumentation) that you can use to find where we know we lack documentation. Fixing spelling mistakes is great. Or rewrite parts that you think is too complicated. You can find what you need to send a PR to the documentation [here](https://github.com/sitespeedio/sitespeed.io/tree/master/docs).
+Documentation is fun and it is the core of making sitespeed.io easy to use. We got a [special documentation tag for issues](https://github.com/sitespeedio/sitespeed.io/issues?q=is%3Aissue+is%3Aopen+label%3Adocumentation) that you can use to find where we know we lack documentation. Fixing spelling mistakes is great. Or rewrite parts that you think is too complicated. You can find what you need to send a PR to the documentation [here](https://github.com/sitespeedio/sitespeed.io/tree/main/docs).
 
 ## Tests
-We lack unit tests. You can read about [our testing pipeline](https://www.sitespeed.io/releasing-with-confidence/) that works good for us but more unit tests are always good. A good start is adding support for the code in the [support library](https://github.com/sitespeedio/sitespeed.io/tree/master/lib/support).
+We lack unit tests. You can read about [our testing pipeline](https://www.sitespeed.io/releasing-with-confidence/) that works good for us but more unit tests are always good. A good start is adding support for the code in the [support library](https://github.com/sitespeedio/sitespeed.io/tree/main/lib/support).
 
 
 ## Companies
@@ -20,4 +20,4 @@ Do you use sitespeed.io in your everyday work? Then we have a perfect propositio
 # Help wanted
 You can help us:
 * [Add connectivity support](https://github.com/sitespeedio/browsertime/issues/313) for Android phones.
-* Help us improve the documentation. We love your feedback and help [https://github.com/sitespeedio/sitespeed.io/tree/master/docs](https://github.com/sitespeedio/sitespeed.io/tree/master/docs).
+* Help us improve the documentation. We love your feedback and help [https://github.com/sitespeedio/sitespeed.io/tree/main/docs](https://github.com/sitespeedio/sitespeed.io/tree/main/docs).

README.md

@@ -1,10 +1,10 @@
 # sitespeed.io
 
-![Unit tests](https://github.com/sitespeedio/sitespeed.io/workflows/Unit%20tests/badge.svg?branch=master)
-![Linux browsers](https://github.com/sitespeedio/sitespeed.io/workflows/Linux%20browsers/badge.svg?branch=master)
-![Docker](https://github.com/sitespeedio/sitespeed.io/workflows/Docker/badge.svg?branch=master)
-![Windows Edge](https://github.com/sitespeedio/sitespeed.io/workflows/Windows%20Edge/badge.svg?branch=master)
-![OSX Safari](https://github.com/sitespeedio/sitespeed.io/workflows/OSX%20Safari/badge.svg?branch=master)
+![Unit tests](https://github.com/sitespeedio/sitespeed.io/workflows/Unit%20tests/badge.svg?branch=main)
+![Linux browsers](https://github.com/sitespeedio/sitespeed.io/workflows/Linux%20browsers/badge.svg?branch=main)
+![Docker](https://github.com/sitespeedio/sitespeed.io/workflows/Docker/badge.svg?branch=main)
+![Windows Edge](https://github.com/sitespeedio/sitespeed.io/workflows/Windows%20Edge/badge.svg?branch=main)
+![OSX Safari](https://github.com/sitespeedio/sitespeed.io/workflows/OSX%20Safari/badge.svg?branch=main)
 [![Downloads][downloads-image]][downloads-url]
 [![Docker][docker-image]][docker-url]
 [![Stars][stars-image]][stars-url]
@@ -12,7 +12,7 @@
 [![Changelog #212][changelog-image]][changelog-url]
 
 
-[Website](https://www.sitespeed.io/) | [Documentation](https://www.sitespeed.io/documentation/sitespeed.io/) | [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) | [Twitter](https://twitter.com/SiteSpeedio)
+[Website](https://www.sitespeed.io/) | [Documentation](https://www.sitespeed.io/documentation/sitespeed.io/) | [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) | [Twitter](https://twitter.com/SiteSpeedio)
 
 ## Welcome to the wonderful world of web performance!
 
@@ -103,28 +103,28 @@ Using sitespeed.io you can:
 * Create HTML-result pages or store the metrics in Graphite.
 * Write your own plugins that can do whatever tests you want/need.
 
-See all the latest changes in the [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md).
+See all the latest changes in the [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md).
 
 Checkout our example [dashboard.sitespeed.io](https://dashboard.sitespeed.io/dashboard/db/page-summary)
 
 A summary report in HTML:
-<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docs/img/start-readme.jpg">
+<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docs/img/start-readme.jpg">
 
 Individual page report:
-<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docs/img/start-url-readme.jpg">
+<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docs/img/start-url-readme.jpg">
 
 Collected metrics from a URL in Graphite/Grafana:
-<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docs/img/grafana-readme.jpg">
+<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docs/img/grafana-readme.jpg">
 
 And look at trends in Grafana:
-<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docs/img/grafana-trends-readme.jpg">
+<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docs/img/grafana-trends-readme.jpg">
 
 Video - easiest using Docker. This gif is optimized, the quality is much better IRL:
 
-<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docs/img/barack.gif">
+<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docs/img/barack.gif">
 
 ## Test using WebPageReplay
-We have a special Docker container that comes with [WebPageReplay](https://github.com/catapult-project/catapult/blob/master/web_page_replay_go/README.md) installed. This is a really early alpha release but we think you should try it out.
+We have a special Docker container that comes with [WebPageReplay](https://github.com/catapult-project/catapult/blob/main/web_page_replay_go/README.md) installed. This is a really early alpha release but we think you should try it out.
 
 WebPageReplay will let you replay your page locally (getting rid of server latency etc) and makes it easier to have stable metrics and find front end regressions.
 

docker/docker-compose.yml

@@ -28,11 +28,11 @@ services:
         # Make sure whisper and graphite.db/grafana.db lives outside your containerr
         # https://www.sitespeed.io/documentation/sitespeed.io/graphite/#graphite-for-production-important
         - whisper:/opt/graphite/storage/whisper
-        # Download an empty graphite.db from https://github.com/sitespeedio/sitespeed.io/tree/master/docker/graphite
+        # Download an empty graphite.db from https://github.com/sitespeedio/sitespeed.io/tree/main/docker/graphite
         # - /absolute/path/to/graphite/graphite.db:/opt/graphite/storage/graphite.db
         # 
         # And put the configuration files on your server, configure them as you need
-        # Download from https://github.com/sitespeedio/docker-graphite-statsd/tree/master/conf/graphite
+        # Download from https://github.com/sitespeedio/docker-graphite-statsd/tree/main/conf/graphite
         # - /absolute/path/to/graphite/conf/storage-schemas.conf:/opt/graphite/conf/storage-schemas.conf
         # - /absolute/path/to/graphite/conf/storage-aggregation.conf:/opt/graphite/conf/storage-aggregation.conf
         # - /absolute/path/to/graphite/conf/carbon.conf:/opt/graphite/conf/carbon.conf

docs/_includes/index/box2.md

@@ -1,10 +1,10 @@
 ## Get the latest versions
 * * *
 
- * [sitespeed.io](/documentation/sitespeed.io/) {% include version/sitespeed.io.txt %} [[Docker](https://hub.docker.com/r/sitespeedio/sitespeed.io/)/[npm](https://www.npmjs.com/package/sitespeed.io)/[changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/sitespeed.io/releases.atom)]
- * [Browsertime](/documentation/browsertime/) {% include version/browsertime.txt %} [[Docker](https://hub.docker.com/r/sitespeedio/browsertime/)/[npm](https://www.npmjs.com/package/browsertime)/[changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/browsertime/releases.atom)]
- * [Coach](/documentation/coach/) {% include version/coach.txt %} [[Docker](https://hub.docker.com/r/sitespeedio/coach/)/[npm](https://www.npmjs.com/package/webcoach)/[changelog](https://github.com/sitespeedio/coach/blob/master/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/coach/releases.atom)]
- * [PageXray](/documentation/pagexray/) {% include version/pagexray.txt %} [[npm](https://www.npmjs.com/package/pagexray)/[changelog](https://github.com/sitespeedio/pagexray/blob/master/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/pagexray/releases.atom)]
- * [Compare](https://compare.sitespeed.io/) {% include version/compare.txt %} [[npm](https://www.npmjs.com/package/@sitespeed.io/compare)/[changelog](https://github.com/sitespeedio/compare/blob/master/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/compare/releases.atom)]
- * [Throttle](/documentation/throttle/) {% include version/throttle.txt %} [[npm](https://www.npmjs.com/package/@sitespeed.io/throttle)/[changelog](https://github.com/sitespeedio/throttle/blob/master/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/throttle/releases.atom)]
- * [Chrome-HAR](/documentation/chrome-har/) {% include version/chrome-har.txt %} [[npm](https://www.npmjs.com/package/chrome-har)/[changelog](https://github.com/sitespeedio/chrome-har/blob/master/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/chrome-har/releases.atom)]
+ * [sitespeed.io](/documentation/sitespeed.io/) {% include version/sitespeed.io.txt %} [[Docker](https://hub.docker.com/r/sitespeedio/sitespeed.io/)/[npm](https://www.npmjs.com/package/sitespeed.io)/[changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/sitespeed.io/releases.atom)]
+ * [Browsertime](/documentation/browsertime/) {% include version/browsertime.txt %} [[Docker](https://hub.docker.com/r/sitespeedio/browsertime/)/[npm](https://www.npmjs.com/package/browsertime)/[changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/browsertime/releases.atom)]
+ * [Coach](/documentation/coach/) {% include version/coach.txt %} [[Docker](https://hub.docker.com/r/sitespeedio/coach/)/[npm](https://www.npmjs.com/package/webcoach)/[changelog](https://github.com/sitespeedio/coach/blob/main/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/coach/releases.atom)]
+ * [PageXray](/documentation/pagexray/) {% include version/pagexray.txt %} [[npm](https://www.npmjs.com/package/pagexray)/[changelog](https://github.com/sitespeedio/pagexray/blob/main/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/pagexray/releases.atom)]
+ * [Compare](https://compare.sitespeed.io/) {% include version/compare.txt %} [[npm](https://www.npmjs.com/package/@sitespeed.io/compare)/[changelog](https://github.com/sitespeedio/compare/blob/main/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/compare/releases.atom)]
+ * [Throttle](/documentation/throttle/) {% include version/throttle.txt %} [[npm](https://www.npmjs.com/package/@sitespeed.io/throttle)/[changelog](https://github.com/sitespeedio/throttle/blob/main/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/throttle/releases.atom)]
+ * [Chrome-HAR](/documentation/chrome-har/) {% include version/chrome-har.txt %} [[npm](https://www.npmjs.com/package/chrome-har)/[changelog](https://github.com/sitespeedio/chrome-har/blob/main/CHANGELOG.md)/[RSS](https://github.com/sitespeedio/chrome-har/releases.atom)]

docs/_includes/index/box8.md

@@ -3,6 +3,6 @@
 
 There's a lot of things you can do to help us make sitespeed.io even better than it is today.
 
-If you code, write documentation or do UX you can check the [help section](https://github.com/sitespeedio/sitespeed.io/blob/master/HELP.md) and the [full issue list](https://github.com/sitespeedio/sitespeed.io/issues).
+If you code, write documentation or do UX you can check the [help section](https://github.com/sitespeedio/sitespeed.io/blob/main/HELP.md) and the [full issue list](https://github.com/sitespeedio/sitespeed.io/issues).
 
-[These people](https://github.com/sitespeedio/sitespeed.io/blob/master/CONTRIBUTORS.md) has already improved sitespeed.io with pull requests or ideas (massive love!).
+[These people](https://github.com/sitespeedio/sitespeed.io/blob/main/CONTRIBUTORS.md) has already improved sitespeed.io with pull requests or ideas (massive love!).

docs/_includes/index/dashboard.md

@@ -2,7 +2,7 @@
 * * *
 [<img src="{{site.baseurl}}/img/dashboard-front.png" class="pull-left img-big" alt="Performance dashboard" width="500" height="227">]({{site.baseurl}}/documentation/sitespeed.io/performance-dashboard/)
 
-Using sitespeed.io together with Grafana and Graphite enables you to monitor the performance of your web site. We have a prepared [docker-compose file](https://github.com/sitespeedio/sitespeed.io/blob/master/docker/docker-compose.yml) for your setup and some ready made [generic Grafana dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/master/dashboards/graphite) that will make it easy for you to get it up and running. You can get it up and running in almost 5 minutes!
+Using sitespeed.io together with Grafana and Graphite enables you to monitor the performance of your web site. We have a prepared [docker-compose file](https://github.com/sitespeedio/sitespeed.io/blob/main/docker/docker-compose.yml) for your setup and some ready made [generic Grafana dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/main/dashboards/graphite) that will make it easy for you to get it up and running. You can get it up and running in almost 5 minutes!
 
 We have a version of the dashboard at [dashboard.sitespeed.io](https://dashboard.sitespeed.io/d/000000044/page-timing-metrics?orgId=1) where you can have look and try it out.
 

docs/_layouts/default.html

@@ -65,7 +65,7 @@ layout: compress
 				<div class="col-1-1">
 					<div class="edit">
 						<a
-							href="{{ page.path | prepend: "https://github.com/sitespeedio/sitespeed.io/edit/master/docs/" }}">Edit
+							href="{{ page.path | prepend: "https://github.com/sitespeedio/sitespeed.io/edit/main/docs/" }}">Edit
 							on
 							GitHub</a>
 					</div>

docs/_posts/2016-10-27-sitespeed.io-4.0-is-released.md

@@ -12,7 +12,7 @@ nav: blog
 
 <img src="{{site.baseurl}}/img/celebrate.png" class="pull-right img-big" alt="It's time to celebrate 4.0 is here" width="200" height="200">
 
-Yes we have finally released 4.0. We ([Peter](https://twitter.com/soulislove)/[Tobias](https://twitter.com/tobiaslidskog)/[Jonathan](https://twitter.com/beenanner) and [contributors](https://github.com/sitespeedio/sitespeed.io/blob/master/CONTRIBUTORS.md)) have been working extremely hard the last year to make it happen. Actually we started to think about the new version when we released 3.0 December 2014. So it's almost 2 years in the making. It has been a long ride.
+Yes we have finally released 4.0. We ([Peter](https://twitter.com/soulislove)/[Tobias](https://twitter.com/tobiaslidskog)/[Jonathan](https://twitter.com/beenanner) and [contributors](https://github.com/sitespeedio/sitespeed.io/blob/main/CONTRIBUTORS.md)) have been working extremely hard the last year to make it happen. Actually we started to think about the new version when we released 3.0 December 2014. So it's almost 2 years in the making. It has been a long ride.
 
 Before reading, you should just try it out:
 
@@ -109,7 +109,7 @@ We have changed the key structure of the keys in Graphite. Yes that means you wi
 ## Dashboard in 2 seconds
 Well almost 2 seconds :) Using our new Docker compose script and ready made dashboards you can get it up and running as fast as the containers are downloaded. We also worked to get the Graphite key structure re-usable between web sites, so it's easy to share dashboards.
 
-1. Download our new Docker compose file: curl -O https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/docker-compose.yml
+1. Download our new Docker compose file: curl -O https://raw.githubusercontent.com/sitespeedio/sitespeed.io/mains/docker/docker-compose.yml
 2. Run: <code>docker-compose up</code>
 3. Run sitespeed: <code> docker-compose run sitespeed.io https://www.sitespeed.io/ --graphite.host=graphite</code>
 4. Access the dashboard: http://127.0.0.1:3000
@@ -138,7 +138,7 @@ What's been the hardest part doing 4.0? Things that we cannot control or do not
 * Firefox. We love Firefox. We love Chrome. And it is important that sitespeed.io works on at least two different browsers. The move from Firefoxdriver to Geckodriver hasn't been smooth and there's been a lot of problems getting things to work. Firefox versions not working with Selenium, some thing broken etc, but we hope that all those problems are over now :)
 
 # sitespeed.io 5.0
-Hehe that's going to take some time! We will continue to work on 4.0 for a while to implement the things we missed, fixing bugs, and we would love [your help](https://github.com/sitespeedio/sitespeed.io/blob/master/HELP.md)!
+Hehe that's going to take some time! We will continue to work on 4.0 for a while to implement the things we missed, fixing bugs, and we would love [your help](https://github.com/sitespeedio/sitespeed.io/blob/main/HELP.md)!
 
 The next couple of days we will be doing cleanup and remove old issues, old projects, and try to get a fresh start.
 

docs/_posts/2017-02-14-sitespeed.io-4.4.0-is-released.md

@@ -61,4 +61,4 @@ You can check out this feature in action on [https://dashboard.sitespeed.io](htt
 
 /Jonathan
 
-P.S Read the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for 4.4.0.
+P.S Read the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for 4.4.0.

docs/_posts/2017-03-01-that-timeline-from-chrome.md

@@ -59,4 +59,4 @@ There's [a bug](https://github.com/sitespeedio/browsertime/issues/284) in Chrome
 
 /Peter
 
-P.S Read the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for 4.5.0.
+P.S Read the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for 4.5.0.

docs/_posts/2017-03-11-find-that-median-run.md

@@ -52,4 +52,4 @@ That was all for this release, see you soon!
 
 /Peter
 
-P.S Read the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for 4.6.0.
+P.S Read the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for 4.6.0.

docs/_posts/2017-03-15-4.7.0.md

@@ -21,4 +21,4 @@ We are back with a small release with some important things:
 
 /Peter
 
-P.S Read the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for 4.7.0.
+P.S Read the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for 4.7.0.

docs/_posts/2017-04-03-releasing-with-confidence.md

@@ -26,7 +26,7 @@ We are a [three member team]({{site.baseurl}}/aboutus/), with more PRs (but we w
 Let us show exactly what happens when we push code:
 
  1. We commit our code (or merge your PR) to [GitHub](https://github.com/sitespeedio/sitespeed.io).
- 2. [Travis-CI](https://travis-ci.org/sitespeedio/sitespeed.io) runs a couple of unit tests and a couple of full integration test where we run sitespeed.io from the command line, testing a couple of sites in Chrome/Firefox, and tests our WebPageTest integration. You can find our Travis configuration [here](https://github.com/sitespeedio/sitespeed.io/blob/master/.travis.yml).
+ 2. [Travis-CI](https://travis-ci.org/sitespeedio/sitespeed.io) runs a couple of unit tests and a couple of full integration test where we run sitespeed.io from the command line, testing a couple of sites in Chrome/Firefox, and tests our WebPageTest integration. You can find our Travis configuration [here](https://github.com/sitespeedio/sitespeed.io/blob/main/.travis.yml).
  3. The commit also builds a new [Docker container at the Docker Hub](https://hub.docker.com/r/sitespeedio/sitespeed.io-autobuild/). Remember: This is not the same image as you use when you run sitespeed.io in production, this one contains the latest and greatest commits.
  4. We have a test server on Digital Ocean that runs the latest Docker container (it auto updates when there's a new version of the container). When the next test runs, it will use that latest version. When the test runs, it will upload the HTML to S3 and send the metrics to our Graphite instance.
  5. On the server we also watch the sitespeed.io log and notify via a Slack message when we get an error in the logs using curl as described ([here](http://blog.getpostman.com/2015/12/23/stream-any-log-file-to-slack-using-curl/)).
@@ -59,7 +59,7 @@ Let us show exactly what happens when we push code:
 Having a server continuously running the latest code, pushing the metrics to Graphite has worked out really well for us. It's easy to inspect the result pages at S3. And getting alerted when we have an error in the logs is just awesome. This really lowers the barrier for us to know if something fails.
 
 ### Release
-When we release (= a new version to npm and a new tag to the Docker hub) we use [this](https://github.com/sitespeedio/sitespeed.io/blob/master/release.sh) super simple release script. Before we release we always let the latest code run for a while on our test server and wait for errors on our Slack channel. We also manually browse the logs before a release and verify the HTML result pages on S3.
+When we release (= a new version to npm and a new tag to the Docker hub) we use [this](https://github.com/sitespeedio/sitespeed.io/blob/main/release.sh) super simple release script. Before we release we always let the latest code run for a while on our test server and wait for errors on our Slack channel. We also manually browse the logs before a release and verify the HTML result pages on S3.
 
 ### How you should upgrade sitespeed.io
 If you use Docker (and you should) make sure that you run a tagged versions and by tag we don't mean latest. Pull by setting the version number just like this:
@@ -68,7 +68,7 @@ If you use Docker (and you should) make sure that you run a tagged versions and
 docker pull sitespeedio/sitespeed.io:4.7.0
 ~~~
 
-When you upgrade, read the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) and Docker pull the new version and then change your run script/yml file (or whatever you use to start sitespeed.io) so that it matches the new version number.
+When you upgrade, read the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) and Docker pull the new version and then change your run script/yml file (or whatever you use to start sitespeed.io) so that it matches the new version number.
 
 
 ## What can we do better

docs/_posts/2017-05-14-video-fixes-for-Firefox.md

@@ -22,5 +22,5 @@ In the new release we support testing sites behind Basic Auth as long as you use
 * Show backEndTime in Summary Timings (to make it easy to find runs with same backEndTime).
 * If WebPageTest fails we always log the WebPageTest id so you easily can backtrack the error.
 
-Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for all changes.
+Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for all changes.
 /Peter

docs/_posts/2017-06-24-5.4.0.md

@@ -36,6 +36,6 @@ We also upgraded PageXray (thank you [@vio](https://github.com/vio) for the [PR]
 We are going to take a long vacation this year to recharge and make sure we can make sitespeed.io even better this autumn. What does this mean? We will not answer issues within 8 hours that we usually do, but don't be scared: If we get any important bugs, we will fix them. And we will do maintenance releases when there's a new Chrome/Firefox. And if you want a change, send us a PR :)
 
 
-Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for all changes.
+Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for all changes.
 
 /Peter

docs/_posts/2017-11-27-sitespeed.io-6.0.md

@@ -25,7 +25,7 @@ We've moved out the [GPSI plugin](https://github.com/sitespeedio/plugin-gpsi) to
 These changes will make the plugins more powerful than ever before. We have a new repo where we will keep track of 3rd party plugins [https://github.com/sitespeedio/plugins](https://github.com/sitespeedio/plugins). Go there and checkout [Lorenzo Urbini](https://github.com/siteriaitaliana) work in progress to implement a Lighthouse plugin and help out if you can!
 
 
-When you upgrade, please read our [upgrade notes](https://www.sitespeed.io/documentation/sitespeed.io/upgrade/) and check out the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md).
+When you upgrade, please read our [upgrade notes](https://www.sitespeed.io/documentation/sitespeed.io/upgrade/) and check out the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md).
 
 ### What did not reach 6.0?
 One of the most asked functionalities has been to be able to test multiple pages in one run. We created a meta issue for that, join the discussion at [#1827](https://github.com/sitespeedio/sitespeed.io/issues/1827).
@@ -46,7 +46,7 @@ We removed TSProxy and tc (sltc) as connectivity engines since none of them work
 Important: This change means you need to actively choose to use Throttle or Docker networks.
 {: .note .note-warning}
 
-Read the [full changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#version-200-2017-11-23).
+Read the [full changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#version-200-2017-11-23).
 
 ## PageXray 2.0
 Only bug fixes and upgrading to NodeJS 8 in 2.0, but did you know that in the Autumn we also released a [standalone JavaScript version of PageXray](https://github.com/sitespeedio/pagexray/releases) that you can use in the browser?

docs/_posts/2017-12-12-sitespeed.io-6.1.md

@@ -58,7 +58,7 @@ Screenshot
 ## Docker with bundled WebPageReplay
 Ohhh we are excited about this: It's an really early release and you can help us by try it out.
 
-Both sitespeed.io and Browsertime have a new Docker container that you should use when you try out [WebPageReplay](https://github.com/catapult-project/catapult/tree/master/web_page_replay_go). If you haven't used WebPageReplay (or other performance tools like [mahimahi](https://github.com/ravinet/mahimahi)) the short explanation is that they record your website and replay it locally so when you run your tests, you don't need to hit the internet. This will give you a chance to have very stable metrics and make it easier to find regressions.
+Both sitespeed.io and Browsertime have a new Docker container that you should use when you try out [WebPageReplay](https://github.com/catapult-project/catapult/tree/main/web_page_replay_go). If you haven't used WebPageReplay (or other performance tools like [mahimahi](https://github.com/ravinet/mahimahi)) the short explanation is that they record your website and replay it locally so when you run your tests, you don't need to hit the internet. This will give you a chance to have very stable metrics and make it easier to find regressions.
 
 ### Test it out with sitespeed.io
 
@@ -98,6 +98,6 @@ We also has some fixes in sitespeed.io for this release:
 
 * Fixed broken metrics list [#1850](https://github.com/sitespeedio/sitespeed.io/issues/1850). Thank you [https://github.com/suratovvlad](https://github.com/suratovvlad) for reporting.
 
-Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for all changes.
+Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for all changes.
 
 /Peter

docs/_posts/2018-01-24-sitespeed.io-6.3.md

@@ -52,10 +52,10 @@ We have upgraded to latest video.js 6.6 with smoother progress bar [#1864](https
 And we added filenames to the video when you combine two videos in combineVideos.sh. By naming your video wisely, you can now make it easier understand what you actually compare.
 
 ## Fixes
-We upgraded to latest Browsertime 2.1.4 with [new bug fixes](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md).
+We upgraded to latest Browsertime 2.1.4 with [new bug fixes](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md).
 
 We also fixed the start script so that you on Ubuntu can run WebPageReplay in the Docker container for your Android phone.
 
-Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for all changes.
+Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for all changes.
 
 /Peter

docs/_posts/2018-05-10-browsertime-3.0.md

@@ -65,7 +65,7 @@ We now use pageLoadStrategy _none_. That means if you run your own pageCompleteC
 
 ### WebPageReplay support using Docker
 
-We had it in alpha/beta for a while and now it's there in our default container: [WebPageReplay](https://github.com/catapult-project/catapult/blob/master/web_page_replay_go/README.md).
+We had it in alpha/beta for a while and now it's there in our default container: [WebPageReplay](https://github.com/catapult-project/catapult/blob/main/web_page_replay_go/README.md).
 
 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.
 
@@ -169,7 +169,7 @@ We updated how Browsertime drives Chrome on Android and it works better than bef
 
 ### And more ...
 
-Checkout the full [Changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md) for all changes.
+Checkout the full [Changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md) for all changes.
 
 ## Breaking Changes
 
@@ -193,4 +193,4 @@ We got some breaking changes, please read about them before you upgrade.
 * In some cases we leaked Bluebird promises, they are now native promises.
 * Running the engine took a promise that eventually became the scripts. Now you need to run with the scripts directly (no promises) to simplify the flow.
 
-And by the way: the master branch of sitespeed.io is using 3.0 and we plan to release the next major of in a month or so.
+And by the way: the main branch of sitespeed.io is using 3.0 and we plan to release the next major of in a month or so.

docs/_posts/2018-05-24-sitespeed.io-7.0.md

@@ -62,7 +62,7 @@ Read more about the all changes in [Browsertime 3.0](/browsertime-3.0/).
 The Docker container uses the latest release of Chrome stable and a beta release of Firefox 61. We use Firefox 61 so that the new [HAR Export trigger](https://github.com/devtools-html/har-export-trigger) works.
 
 ### WebPageReplay support using Docker
-We had it in alpha/beta for a while and now it's there in our default container: [WebPageReplay](https://github.com/catapult-project/catapult/blob/master/web_page_replay_go/README.md).
+We had it in alpha/beta for a while and now it's there in our default container: [WebPageReplay](https://github.com/catapult-project/catapult/blob/main/web_page_replay_go/README.md).
 
 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.
 
@@ -162,6 +162,6 @@ For plugin makers or plugin users that uses screenshots or Chrome trace logs the
 ## What's next
 The coming weeks/month we going to take care of bugs, concentrate on making a better guide to deploy sitespeed.io and then it's time for summer vacation :)
 
-Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for all changes.
+Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for all changes.
 
 /Peter

docs/_posts/2018-10-10-sitespeed.io-7.5.md

@@ -9,7 +9,7 @@ nav: blog
 ---
 
 # sitespeed.io version 7.5
-Today (the 10th of October) is six years ago we [released sitespeed.io 1.0](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md#version-10---2012-10-10). A lot have changed (for the better) over the years and today we are doing release number 200! 
+Today (the 10th of October) is six years ago we [released sitespeed.io 1.0](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md#version-10---2012-10-10). A lot have changed (for the better) over the years and today we are doing release number 200! 
 
 ## New in 7.5
 We have been collecting a couple of features and fixes over the last months that's finally being released.
@@ -104,7 +104,7 @@ You can give alias for URLs in the CLI with ```--urlAlias```. The number of alia
 We have been old and conservative in how we use # when creating URLs: From the beginning (6+ years ago) we always left out # from URLs when we decided if a URL is unique or not. Now you can choose yourself with ```--useHash``` [#2142](https://github.com/sitespeedio/sitespeed.io/pull/2142).
 
 ### Updated dashboards
-There's a new version of the [page summary](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/master/dashboards/graphite/PageSummary.json) and [page timing](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/master/dashboards/graphite/PageTimingMetrics.json) dashboards for Graphite, trying to make it easier to find regressions: [https://github.com/sitespeedio/grafana-bootstrap-docker](https://github.com/sitespeedio/grafana-bootstrap-docker)
+There's a new version of the [page summary](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/main/dashboards/graphite/PageSummary.json) and [page timing](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/main/dashboards/graphite/PageTimingMetrics.json) dashboards for Graphite, trying to make it easier to find regressions: [https://github.com/sitespeedio/grafana-bootstrap-docker](https://github.com/sitespeedio/grafana-bootstrap-docker)
 
  ![New updated dashboards for Graphite]({{site.baseurl}}/img/page-summary-7.5.png)
 {: .img-thumbnail-center}
@@ -117,7 +117,7 @@ There's a new version of the [page summary](https://github.com/sitespeedio/grafa
 
 * We updated to PageXray 2.4.0 that correctly pick up mime types for video/audio/xml and pdf (that was missed before). 
 
-* Updated to [Coach 2.3.0](https://github.com/sitespeedio/coach/blob/master/CHANGELOG.md) that fixes so that the CSS advice never can be a negative score.
+* Updated to [Coach 2.3.0](https://github.com/sitespeedio/coach/blob/main/CHANGELOG.md) that fixes so that the CSS advice never can be a negative score.
 
 * Fixed the bug that made us show wrong video/screenshot on page summary[#2169](https://github.com/sitespeedio/sitespeed.io/pull/2169). Before we always showed the first screenshot/video. Now we show the median pick (so it correlates to the right waterfall and metrics tab).
 
@@ -129,6 +129,6 @@ There's a new version of the [page summary](https://github.com/sitespeedio/grafa
 
 
 ## Summary
-Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for all the changes.
+Checkout the full [Changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for all the changes.
 
 /Peter

docs/_posts/2018-11-20-coach-3.0.md

@@ -91,7 +91,7 @@ There's been a lot of changes in the background:
 * We bumped all dependencies to use the latest releases.
 * We upgraded to latest Browsertime.
 
-If you want to checkout the actual changes, go to the [changelog](https://github.com/sitespeedio/coach/blob/master/CHANGELOG.md) where we have references to all PRs.
+If you want to checkout the actual changes, go to the [changelog](https://github.com/sitespeedio/coach/blob/main/CHANGELOG.md) where we have references to all PRs.
 
 ## Summary
 Is there any advice the Coach is missing? Or should we change anything? Help us out by [letting us know](https://github.com/sitespeedio/coach/issues/new). 

docs/_posts/2019-01-21-sitespeed.io-8.0-and-browsertime.4.0.md

@@ -10,7 +10,7 @@ nav: blog
 
 # Sitespeed.io 8.0 and Browsertime 4.0
 
-There are so many new and great thing in this release and we will focus on a couple of new things in this blog post. You can read about the rest of the changes in the [changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md) for Browsertime and the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for sitespeed.io.
+There are so many new and great thing in this release and we will focus on a couple of new things in this blog post. You can read about the rest of the changes in the [changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md) for Browsertime and the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for sitespeed.io.
 
 Lets talk about:
 - [Testing multiple pages within a browser session](#testing-multiple-pages-within-a-browser-session)
@@ -155,7 +155,7 @@ We have updated our dashboards to include new metrics like Privacy score from th
 ![Compare to last week]({{site.baseurl}}/img/new-dashboard-8.0.jpg)
 {: .img-thumbnail}
 
-You can get the [updated dashboards from GitHub](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/master/dashboards/graphite) and check them out at [dashboard.sitespeed.io](https://dashboard.sitespeed.io/d/000000044/page-timing-metrics?orgId=1).
+You can get the [updated dashboards from GitHub](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/main/dashboards/graphite) and check them out at [dashboard.sitespeed.io](https://dashboard.sitespeed.io/d/000000044/page-timing-metrics?orgId=1).
 
 ## New budget configuration
 One problem before 8.0 was that it was really hard to configure a performance budget: You needed to use the internal data structure and that sucks. Looking at other tools we could see that configuring a budget is usually hard. That's why we are introducing a new way in 8.0 (if you where using the old configuration pre 8.0, don't worry, that will continue to work).

docs/_posts/2019-02-02-sitespeed.io-8.1.md

@@ -98,6 +98,6 @@ module.exports = async function(context, commands) {
 ~~~
 
 ## Changlog
-To see all changes you need to read the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md).
+To see all changes you need to read the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md).
 
 /Peter

docs/_posts/2019-02-17-sitespeed.io-8.6.md

@@ -10,7 +10,7 @@ nav: blog
 
 # Sitespeed.io 8.6
 
-You should look at the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md), the last 7 days we released a couple of releases with bug fixes and some new (smallish) features.
+You should look at the full [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md), the last 7 days we released a couple of releases with bug fixes and some new (smallish) features.
 
 ## Features
 

docs/_posts/2019-03-30-sitespeed.io-8.9.md

@@ -16,7 +16,7 @@ The [Third party web](https://github.com/patrickhulce/third-party-web) project l
 
 One thing to remember is that a tool can have multiple categories. For example, it can be both a analytics tool AND a [surveillance](https://en.wikipedia.org/wiki/Surveillance_capitalism) tool.
 
-By default the third party information will be sent to Graphite/InfluxDb and if you are a Graphite user you can upgrade the page summary dashboard to [the latest version](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/master/dashboards/graphite/PageSummary.json). You will then get two new graphs.
+By default the third party information will be sent to Graphite/InfluxDb and if you are a Graphite user you can upgrade the page summary dashboard to [the latest version](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/main/dashboards/graphite/PageSummary.json). You will then get two new graphs.
 
 The first graph shows you third party requests by category. Here can you see how many requests each category generates.
 
@@ -37,12 +37,12 @@ And then also see the exact tools that are used.
 ![Third party tools]({{site.baseurl}}/img/8.9/thirdparty-tools-html.png)
 {: .img-thumbnail}
 
-At the moment we are very liberate on categorising tools as surveillance and need your help to get it right. Do a PR to help us help by changing [https://github.com/sitespeedio/sitespeed.io/blob/master/lib/plugins/thirdparty/index.js#L34-L38](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/plugins/thirdparty/index.js#L34-L38).
+At the moment we are very liberate on categorising tools as surveillance and need your help to get it right. Do a PR to help us help by changing [https://github.com/sitespeedio/sitespeed.io/blob/main/lib/plugins/thirdparty/index.js#L34-L38](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/plugins/thirdparty/index.js#L34-L38).
 
 The new categorisation happens automatically. But you should still use the `--firstParty` regex to categorise requests since it is used when we internally categorise requests and gives you the flexibility to choose what requests are first/third party.
 
 We also moved the 3rd part information from PageXray to the new tab and hopefully we can add more data there in the future. What about download time spent per tool and CPU time? Would love your help there if you are a user and your web site have a lot of third parties.
 
-8.9.0 also contains a couple of bug fixes that you can read about in the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md).
+8.9.0 also contains a couple of bug fixes that you can read about in the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md).
 
 /Peter

docs/_posts/2019-05-21-sitespeed.io-9.0.md

@@ -57,7 +57,7 @@ You can now track CPU spent per tool/third party. It's turned off by default and
 ![CPU spent per tool]({{site.baseurl}}/img/cpu-per-tool.png)
 {: .img-thumbnail}
 
-The Grafana dashboards are updated to include the new metrics if you use Graphite. You can [download the new page timing metric dashboard](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/master/dashboards/graphite/PageTimingMetrics.json).
+The Grafana dashboards are updated to include the new metrics if you use Graphite. You can [download the new page timing metric dashboard](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/main/dashboards/graphite/PageTimingMetrics.json).
 
 ### Easier way of blocking 3rd parties
 
@@ -132,7 +132,7 @@ At the moment you find the info in the raw tab:
 
 
 ## Changelog
-To see all changes and the PRs you should read the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md). 
+To see all changes and the PRs you should read the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md). 
 
 Remember when you upgrade there are two things that can change: Metrics could be a little slower in Chrome since we now collect more trace log (only when you turn on CPU tracing) and there are new categoris for the CPU trace! If you use Lighthouse and had your own hack for including the HTML, that isn't needed any more.
 

docs/_posts/2019-05-30-sitespeed.io-9.1.md

@@ -34,6 +34,6 @@ Or you can compare Coach performance and privacy score:
 
 You can read more about the new leaderboard in the [documentation](/documentation/sitespeed.io/leaderboard/).
 
-We have some more changes and some bug fixes that you can read about in the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md).
+We have some more changes and some bug fixes that you can read about in the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md).
 
 /Peter

docs/_posts/2019-09-11-sitespeed.io-10.0.md

@@ -90,7 +90,7 @@ If you drive WebPageTest and disabled Browsertime, the annotation will show the
 
 ## Dashboards updated
 
-We have updated all the default dashboards, you [download them from here](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/master/dashboards/graphite).
+We have updated all the default dashboards, you [download them from here](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/main/dashboards/graphite).
 
 
 ## Run your tests on Kubernetes
@@ -126,6 +126,6 @@ There are also three breaking changes:
 * Upgraded to Ubuntu Disco in the Docker container [#908](https://github.com/sitespeedio/browsertime/pull/908).
 * There's an alternative to collect Visual Metrics using the Chrome trace log, using [SpeedLine](https://github.com/paulirish/speedline) implemented in [#876](https://github.com/sitespeedio/browsertime/pull/876). Using video give more accurate metrics (at least in our testing) but maybe it could help running on Chrome on Android and add less overhead than recording a video. You can enable it with:  `--cpu --browsertime.chrome.visualMetricsUsingTrace --browsertime.chrome.enableTraceScreenshots`
 
-We have some more changes and some bug fixes that you can read about in the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md).
+We have some more changes and some bug fixes that you can read about in the [changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md).
 
 /Peter

docs/_posts/2019-11-07-sitespeed.io-11.0.md

@@ -70,10 +70,10 @@ We done two important bug fixes:
 * Fixed so that you can disable video/visual metrics in your configuration JSON in Docker as reported in [#2692](https://github.com/sitespeedio/sitespeed.io/issues/2692) fixed by PR [#2715](https://github.com/sitespeedio/sitespeed.io/pull/2715).
 * Fixed so that running AXE when testing multiple URLs works in scripting (reported in [#2754](https://github.com/sitespeedio/sitespeed.io/issues/2754)). Fixed in [#2755](https://github.com/sitespeedio/sitespeed.io/pull/2755).
 
-Read about all the changes in [the changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md)!
+Read about all the changes in [the changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md)!
 
 ## Sponsor sitespeed.io
-We are also launching [GitHub sponsorship](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) with this release! [Read more about sponsoring sitespeed.io](/sponsor/).
+We are also launching [GitHub sponsorship](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) with this release! [Read more about sponsoring sitespeed.io](/sponsor/).
 
 
 /Peter

docs/_posts/2020-02-06-sitespeed.io-12.0-and-browsertime-8.0.md

@@ -10,7 +10,7 @@ nav: blog
 
 # sitespeed.io 12.0 and Browsertime 8.0 
 
-The [changelog for the new Browsertime 8.0](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#800-2020-02-05) is massive because we have many new contributions, mainly from the Mozilla performance team! Extra special thank you to all new contributors:
+The [changelog for the new Browsertime 8.0](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#800-2020-02-05) is massive because we have many new contributions, mainly from the Mozilla performance team! Extra special thank you to all new contributors:
 
 * [Nick Alexander](https://github.com/ncalexan)
 * [Denis Palmeiro](https://github.com/dpalmeiro)
@@ -92,6 +92,6 @@ Making Sharp an optional requirement as proposed by [Nick Alexander](https://git
 
 Move visualmetrics.py to a python package [#1148](https://github.com/sitespeedio/browsertime/pull/1148) - thank you [Tarek Ziade](https://github.com/tarekziade)!
 
-Checkout the [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md#800-2020-02-05) for the massive list of all things that have been fixed in latest 8.0 release.
+Checkout the [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md#800-2020-02-05) for the massive list of all things that have been fixed in latest 8.0 release.
 
 /Peter

docs/_posts/2020-03-03-sitespeed.io-12.1-and-browsertime-8.1.md

@@ -94,7 +94,7 @@ By default the hosting data (knowing if a host is green) is collected from a loc
 You can also disable the hosting match (all hosts will be treated as grey hosting) with `--sustainable.disableHosting`.
 
 ## Video and Visual Metrics on OS X
-An old friend is back, we again support video and Visual Metrics on OS X! You need to install FFMpeg and the rest of the dependencies, checkout the [Travis-CI setup](https://github.com/sitespeedio/browsertime/blob/master/.travis.yml).
+An old friend is back, we again support video and Visual Metrics on OS X! You need to install FFMpeg and the rest of the dependencies, checkout the [Travis-CI setup](https://github.com/sitespeedio/browsertime/blob/main/.travis.yml).
 
 We also a aim to make it possible to use video Visual Metrics on Windows and you can help us out in [Browsertime #1203](https://github.com/sitespeedio/browsertime/issues/1203)!
 
@@ -109,6 +109,6 @@ You can download the ChromeDriver yourself from the [Google repo](https://chrome
 You can also choose versions for Edge and Firefox with `EDGEDRIVER_VERSION` and `GECKODRIVER_VERSION`.
 
 ## And more
-We also done a couple of bug fixes. Checkout the  [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md) and the [sitespeed.io changelog](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) for the full list. 
+We also done a couple of bug fixes. Checkout the  [Browsertime changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md) and the [sitespeed.io changelog](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) for the full list. 
 
 /Peter

docs/documentation/browsertime/details/index.md

@@ -40,7 +40,7 @@ It's easiest to run [our ready-made Docker container](https://hub.docker.com/r/s
 
 The default video will include a timer and showing when the metrics happens, but you can turn that off using <code>--videoRaw</code>.
 
-<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docs/img/video-example.gif">
+<img src="https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docs/img/video-example.gif">
 
 ## Test using Docker
 You can build and test changes using Docker locally. First build it:
@@ -65,7 +65,7 @@ Browsertime supports Chrome on Android: Collecting SpeedIndex, HAR and video! Th
 
 You need to [install ADB](https://www.sitespeed.io/documentation/sitespeed.io/mobile-phones/#desktop) and [prepare your phone](https://www.sitespeed.io/documentation/sitespeed.io/mobile-phones/#on-your-phone) before you start.
 
-The current version doesn't support Docker so you need to [install the requirements](https://github.com/sitespeedio/docker-visualmetrics-deps/blob/master/Dockerfile) for VisualMetrics yourself on your machine before you start.
+The current version doesn't support Docker so you need to [install the requirements](https://github.com/sitespeedio/docker-visualmetrics-deps/blob/main/Dockerfile) for VisualMetrics yourself on your machine before you start.
 
 If you want to set connectivity you need to use something like [Pi Network Conditioner](https://github.com/phuedx/pinc).
 

docs/documentation/browsertime/index.md

@@ -13,7 +13,7 @@ twitterdescription: Documentation for Browsertime.
 
 <img src="{{site.baseurl}}/img/logos/browsertime.png" class="pull-right img-big" alt="Browsertime logo" width="200" height="175">
 
-Browsertime is the heart of sitespeed.io that handles everything with the browser. At the moment we support Chrome and Firefox on desktop, Chrome on Android and limited support for Safari on OS X and iOS. You can see all the latest changes in the [Changelog](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md) for the project.
+Browsertime is the heart of sitespeed.io that handles everything with the browser. At the moment we support Chrome and Firefox on desktop, Chrome on Android and limited support for Safari on OS X and iOS. You can see all the latest changes in the [Changelog](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md) for the project.
 
  * [Introduction](introduction/) - what you can do with Browsertime.
  * [Installation](installation/) - install using npm, yarn or run our Docker containers.

docs/documentation/coach/developers/index.md

@@ -169,7 +169,7 @@ if (util.isHTTP2(page)) {
 
 
 ## Test in your browser
-You can and should test your advice in your browser. It's easy. Just copy/paste your advice into the browser console. If you use the [utility methods](https://github.com/sitespeedio/coach/blob/master/lib/dom/util.js)  you need to copy/paste that too inside your console before you test your advice.
+You can and should test your advice in your browser. It's easy. Just copy/paste your advice into the browser console. If you use the [utility methods](https://github.com/sitespeedio/coach/blob/main/lib/dom/util.js)  you need to copy/paste that too inside your console before you test your advice.
 
 ## Add a test case
 When you create a new advice you also need to create unit tests. We run the tests in both Firefox & Chrome.
@@ -187,7 +187,7 @@ it('We should find out if we load an print CSS', function() {
 });
 ```
 
-Right now all these tests run in https://github.com/sitespeedio/coach/blob/master/test/dom/performance/indexTest.js
+Right now all these tests run in https://github.com/sitespeedio/coach/blob/main/test/dom/performance/indexTest.js
 
 Each test case runs against a specific HTML page located in `test/http-server` Create a suitable HTML page with the structure you want to test. Create the test case in `test/dom` or `test/har` and run it with <code>npm test</code>
 

docs/documentation/sitespeed.io/axe/index.md

@@ -33,7 +33,7 @@ That will run [axe-core](https://github.com/dequelabs/axe-core) and generate a n
 
 
 ## Configure Axe
-You can [configure Axe](https://github.com/dequelabs/axe-core/blob/master/doc/API.md#api-name-axeconfigure) which rules/checks that will be used. In the *axe* namespace we pass on all parameters to the configuration object of Axe. `--axe.checks` will result in a configuration object like:
+You can [configure Axe](https://github.com/dequelabs/axe-core/blob/main/doc/API.md#api-name-axeconfigure) which rules/checks that will be used. In the *axe* namespace we pass on all parameters to the configuration object of Axe. `--axe.checks` will result in a configuration object like:
 
 ```json
 checks: {

docs/documentation/sitespeed.io/best-practice/index.md

@@ -74,7 +74,7 @@ You should also try out our new setup with [WebPageReplay](../webpagereplay/).
 Checkout the [scripting capabilities](../scripting/) that makes it easy to test multiple pages.
 
 ### I want to test on different CPUs how do I do that?
-We currently don't built in support for changing the CPU. What we do know is that you should not use the built in support in Chrome or try to simulate slow CPUs by running on slow AWS instance. What should do is what WPTAgent do. You can check the code at [https://github.com/WPO-Foundation/wptagent/blob/master/wptagent.py](https://github.com/WPO-Foundation/wptagent/blob/master/wptagent.py) and do the same before you start a run and then remove it after the run.
+We currently don't built in support for changing the CPU. What we do know is that you should not use the built in support in Chrome or try to simulate slow CPUs by running on slow AWS instance. What should do is what WPTAgent do. You can check the code at [https://github.com/WPO-Foundation/wptagent/blob/main/wptagent.py](https://github.com/WPO-Foundation/wptagent/blob/main/wptagent.py) and do the same before you start a run and then remove it after the run.
 
 ### Throttle or not throttle your connection?
 **PLEASE, YOU NEED TO ALWAYS THROTTLE YOUR CONNECTION!** You should always throttle/limit the connectivity because it will make it easier for you to find regressions. If you don't do it, you can run your tests with different connectivity profiles and regressions/improvements that you see is caused by your servers flaky internet connection. Check out our [connectivity guide]({{site.baseurl}}/documentation/sitespeed.io/connectivity/).

docs/documentation/sitespeed.io/browsers/index.md

@@ -22,7 +22,7 @@ You can fetch timings, run your own JavaScript and record a video of the screen.
 The latest version of Firefox should work out of the box.
 
 ### Firefox profile setup
-At the moment we setup a new profile for each run the browser do. We set up the profiles preferences like [this](https://github.com/sitespeedio/browsertime/blob/master/lib/firefox/webdriver/firefoxPreferences.js). We use Mozillas [own configuration](https://searchfox.org/mozilla-central/source/testing/talos/talos/config.py) as default with some changes + some extra configuration for performance and privacy.
+At the moment we setup a new profile for each run the browser do. We set up the profiles preferences like [this](https://github.com/sitespeedio/browsertime/blob/main/lib/firefox/webdriver/firefoxPreferences.js). We use Mozillas [own configuration](https://searchfox.org/mozilla-central/source/testing/talos/talos/config.py) as default with some changes + some extra configuration for performance and privacy.
 
 We try to disable all Firefox ping home:
  * We disable [heartbeat](https://wiki.mozilla.org/Firefox/Shield/Heartbeat).
@@ -97,7 +97,7 @@ docker run --shm-size 2g --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io
 The latest version of Chrome should work out of the box. Latest version of stable [ChromeDriver](http://chromedriver.chromium.org) is bundled in sitespeed.io and needs to match your Chrome version.
 
 ### Chrome setup
-When we start Chrome it is setup with [these](https://github.com/sitespeedio/browsertime/blob/master/lib/chrome/webdriver/chromeOptions.js) command line switches.
+When we start Chrome it is setup with [these](https://github.com/sitespeedio/browsertime/blob/main/lib/chrome/webdriver/chromeOptions.js) command line switches.
 
 ### Add your own Chrome args
 Chrome has a [long list](https://peter.sh/experiments/chromium-command-line-switches/) of command line switches that you can use to make Chrome act differently than the default setup. You can add those switched to Chrome with ```--chrome.args``` (repeat the argument if you have multiple arguments).
@@ -195,7 +195,7 @@ If you add your own complete check you can also choose when your check is run. B
 
 ## Custom metrics
 
-You can collect your own metrics in the browser by supplying JavaScript file(s). By default we collect all metrics inside [these folders](https://github.com/sitespeedio/browsertime/tree/master/browserscripts), but you might have something else you want to collect.
+You can collect your own metrics in the browser by supplying JavaScript file(s). By default we collect all metrics inside [these folders](https://github.com/sitespeedio/browsertime/tree/main/browserscripts), but you might have something else you want to collect.
 
 Each JavaScript file need to return a metric/value which will be picked up and returned in the JSON. If you return a number, statistics will automatically be generated for the value (like median/percentiles etc).
 

docs/documentation/sitespeed.io/bug-report/index.md

@@ -25,7 +25,7 @@ Sometimes we get a really detailed issue: You describe exactly how you do when y
 
 It also happens (quite often) that we get issues that misses important information, so we need to ask you again and again about the problem (like how to reproduce the issue). Sometimes we need to do that two/three/four times within that issue. Issues that misses vital information takes longer time to fix/close and that makes us spend more time asking questions instead of fixing actual bugs or creating new functionality. 
 
-We use a [issue template](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/.github/ISSUE_TEMPLATE.md) with a comment of what we need write but it seems that is not the best way so let us instead show you what we need!
+We use a [issue template](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/.github/ISSUE_TEMPLATE.md) with a comment of what we need write but it seems that is not the best way so let us instead show you what we need!
 
 Before you start creating a issue, you should make sure you have read through our [F.A.Q and Best Practice](https://www.sitespeed.io/documentation/sitespeed.io/best-practice/).
 

docs/documentation/sitespeed.io/configuration/index.md

@@ -231,7 +231,7 @@ You can also extend another JSON config file. The path needs to be absolute.
 }
 ~~~
 
-You can check out [our example configuration](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/master/config) for [dashboard.sitespeed.io](https://dashboard.sitespeed.io). 
+You can check out [our example configuration](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/main/config) for [dashboard.sitespeed.io](https://dashboard.sitespeed.io). 
 
 
 ## Advanced

docs/documentation/sitespeed.io/configure-html/index.md

@@ -89,7 +89,7 @@ Or use a configuration json:
 
 # Configure the thresholds for red/yellow/green summary boxes
 
-You can override the default configurations that definees the colors of the summary boxes. The default code is set [here](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/plugins/html/setup/summaryBoxesDefaultLimits.js) and is a good starting point for what you can set.
+You can override the default configurations that definees the colors of the summary boxes. The default code is set [here](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/plugins/html/setup/summaryBoxesDefaultLimits.js) and is a good starting point for what you can set.
 
 Define your JSON file with the limits and feed it to sitespeed.io with `--html.summaryBoxesThresholds`.
 
@@ -113,7 +113,7 @@ docker run --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io:{% include ve
 
 
 # Configurable metrics 
-Here are the different metrics that you can show in the summary boxes or in the page HTML. Any metric missing? [Make a PR](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/support/friendlynames.js) or [create a issue](https://github.com/sitespeedio/sitespeed.io/issues/new)!
+Here are the different metrics that you can show in the summary boxes or in the page HTML. Any metric missing? [Make a PR](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/support/friendlynames.js) or [create a issue](https://github.com/sitespeedio/sitespeed.io/issues/new)!
 
 
 ~~~

docs/documentation/sitespeed.io/continuous-integration/index.md

@@ -104,7 +104,7 @@ docker run -v ${WORKSPACE}:/sitespeed.io sitespeedio/sitespeed.io --outputFolder
 Remember that you can also send the metrics to Graphite to keep a closer eye on all metrics over time.
 
 ## Travis
-We have an example project for setting up Travis [https://github.com/sitespeedio/travis/](https://github.com/sitespeedio/travis/blob/master/.travis.yml). You should not try to use timings in your budget, simply because they tend to vary and be highly unreliable. We suggest using metrics that do not vary greatly and will be the same between runs like Coach score or number of requests.
+We have an example project for setting up Travis [https://github.com/sitespeedio/travis/](https://github.com/sitespeedio/travis/blob/main/.travis.yml). You should not try to use timings in your budget, simply because they tend to vary and be highly unreliable. We suggest using metrics that do not vary greatly and will be the same between runs like Coach score or number of requests.
 
 ## Circle CI
 Setting up your sitespeed tests on Circle is a straight forward process. What works the best is to use Circle's [Linux VM](https://circleci.com/build-environments/linux/) which will spin-up a pre-configured VM made to run variations of Docker and pre-installed with lots of tools that you may need to get sitespeed up and running.

docs/documentation/sitespeed.io/continuously-run-your-tests/index.md

@@ -33,9 +33,9 @@ The script creates a file called **sitespeed.run** in your current folder. If yo
 
 The first part before the first dot in the filename will be appended to the Graphite namespace namespace (`--graphite.namespace`). If your file is named *login.js* the namespace will be `login`. If your file is named *login.2.js* the namespace is still `login`.
 
-Do you want to add a new URL to test on desktop? Navigate to [**desktop/urls**](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/master/nyc3-1/desktop/urls) and create your new file there. Want to add a user journey? Add the script in [**desktop/scripts**](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/master/nyc3-1/desktop/scripts).
+Do you want to add a new URL to test on desktop? Navigate to [**desktop/urls**](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/main/nyc3-1/desktop/urls) and create your new file there. Want to add a user journey? Add the script in [**desktop/scripts**](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/main/nyc3-1/desktop/scripts).
 
-Our example run tests for [desktop](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/master/nyc3-1/desktop), [emulated mobile](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/master/nyc3-1/mobile) (both URLs and scripts), testing using WebPageReplay ([replay](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/master/nyc3-1/replay/urls)) and WebPageTest ([webpagetest](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/master/nyc3-1/webpagetest/urls)). But you probably don't need all that so you can remove the code in the [**run.sh**](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/master/run.sh) script.
+Our example run tests for [desktop](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/main/nyc3-1/desktop), [emulated mobile](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/main/nyc3-1/mobile) (both URLs and scripts), testing using WebPageReplay ([replay](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/main/nyc3-1/replay/urls)) and WebPageTest ([webpagetest](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/main/nyc3-1/webpagetest/urls)). But you probably don't need all that so you can remove the code in the [**run.sh**](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/main/run.sh) script.
 
 The structure looks like this:
 
@@ -72,9 +72,9 @@ The structure looks like this:
 └── run.sh
 ```
 
-The [**loop.sh**](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/master/loop.sh) is the start point. Run it and feed it with the folder name of the server (in our case we only run the tests on server names *nyc3-1*). That script will git pull the rep for every iteration and run the script [**run.sh**](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/master/run.sh).
+The [**loop.sh**](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/main/loop.sh) is the start point. Run it and feed it with the folder name of the server (in our case we only run the tests on server names *nyc3-1*). That script will git pull the rep for every iteration and run the script [**run.sh**](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/main/run.sh).
 
-Then [**run.sh**](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/master/run.sh) will use the right configuration in [**/config/**](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/master/config) and run the URLs/scripts that are configured. Our configuration files extends configuration files that only exits on the server where we hold secret information like username and passwords. You don't need set it up that way, if you use a private git repo.
+Then [**run.sh**](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/main/run.sh) will use the right configuration in [**/config/**](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/main/config) and run the URLs/scripts that are configured. Our configuration files extends configuration files that only exits on the server where we hold secret information like username and passwords. You don't need set it up that way, if you use a private git repo.
 
 ### What you need to do
 You need to modify our tests and scripts so that you don't test the exact same URLs as us :)
@@ -120,7 +120,7 @@ In our example we have two configuration files on the server that we extends. Th
 }
 ```
 
-Then our configuration files in [**/config/**](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/master/config) extends these config files. They look something like this:
+Then our configuration files in [**/config/**](https://github.com/sitespeedio/dashboard.sitespeed.io/tree/main/config) extends these config files. They look something like this:
 
 ```json
 {
@@ -129,7 +129,7 @@ Then our configuration files in [**/config/**](https://github.com/sitespeedio/da
 }
 ```
 
-And when we run our tests, we map the volume on the server /config to our docker container. You can see that in the [run.sh](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/master/run.sh) file. Look for `-v /config:/config`. That is the magic line.
+And when we run our tests, we map the volume on the server /config to our docker container. You can see that in the [run.sh](https://github.com/sitespeedio/dashboard.sitespeed.io/blob/main/run.sh) file. Look for `-v /config:/config`. That is the magic line.
 
 
 We then also map the current working dir to `-v "$(pwd)":/sitespeed.io` and then feed the the config file to sitespeed `--config /sitespeed.io/config`. That way, inside the Docker container we have **/config/** that has the secret configuration files and in **/sitespeed.io/config** the configuration we want to use for our tests.

docs/documentation/sitespeed.io/developers/index.md

@@ -29,7 +29,7 @@ Sitespeed.io uses a lot of other Open Source tools so massive love to those proj
  * [Skeleton](http://getskeleton.com)
  * [Simple crawler](https://github.com/cgiffard/node-simplecrawler)
  * [Pug](https://www.npmjs.com/package/pug)
- * all other projects in the [package.json](https://github.com/sitespeedio/sitespeed.io/blob/master/package.json).
+ * all other projects in the [package.json](https://github.com/sitespeedio/sitespeed.io/blob/main/package.json).
 
 And we also have plugins so that you can use:
 
@@ -182,7 +182,7 @@ Before you send the PR make sure you:
  * Squash your commits so it looks sane
  * Make sure your code follow our lint rule by running: <code>npm run lint</code> and use <code>npm run lint:fix</code> if you have any breaking rules
  * Make sure your code don't break any tests: <code>npm test</code>
- * Update the documentation [https://github.com/sitespeedio/sitespeed.io/tree/master/docs](https://github.com/sitespeedio/sitespeed.io/tree/master/docs) in another pull request. When we merge the PR the documentation will automatically be updated so we do that when we push the next release
+ * Update the documentation [https://github.com/sitespeedio/sitespeed.io/tree/main/docs](https://github.com/sitespeedio/sitespeed.io/tree/main/docs) in another pull request. When we merge the PR the documentation will automatically be updated so we do that when we push the next release
 
 ### Do a sitespeed.io release
 When you become a member of the sitespeed.io team you can push releases. You do that by running the release bash script in root: <code>./release.sh</code>
@@ -198,12 +198,12 @@ Before you do a release, remember to let your latest code change run a couple of
 Do the release:
 
 1. Make sure you have a clean repo: `git status`
-2. Read through the [CHANGELOG](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) and see that all changes are included and add the version + date at the top for the new release and commit the change.
+2. Read through the [CHANGELOG](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) and see that all changes are included and add the version + date at the top for the new release and commit the change.
 3. Run `./release.sh`
 4. Choose version
 5. Login into Docker, add your 2FA when prompted
-6. When a new browser window opens at GitHub with the release, copy/paste the changes from the [CHANGELOG](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md)  and add it instead of the commits and create the release.
-7. Commit the updated [version file](https://github.com/sitespeedio/sitespeed.io/blob/master/docs/_includes/version/sitespeed.io.txt) and the [configuration file](https://github.com/sitespeedio/sitespeed.io/blob/master/docs/documentation/sitespeed.io/configuration/config.md) if that's changed.
+6. When a new browser window opens at GitHub with the release, copy/paste the changes from the [CHANGELOG](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md)  and add it instead of the commits and create the release.
+7. Commit the updated [version file](https://github.com/sitespeedio/sitespeed.io/blob/main/docs/_includes/version/sitespeed.io.txt) and the [configuration file](https://github.com/sitespeedio/sitespeed.io/blob/main/docs/documentation/sitespeed.io/configuration/config.md) if that's changed.
 
 ### Do a Browsertime release
 When you become a member of the Browsertime team you can push releases. You do that by running the release bash script in root: <code>./release.sh</code>
@@ -218,12 +218,12 @@ Before you do a release, make sure the latest commits has a [green light in Trav
 
 Do the release:
 1. Make sure you have a clean repo: `git status`
-2. Read through the [CHANGELOG](https://github.com/sitespeedio/browsertime/blob/master/CHANGELOG.md) and see that all changes are included and add the version + date at the top for the new release and commit the change.
+2. Read through the [CHANGELOG](https://github.com/sitespeedio/browsertime/blob/main/CHANGELOG.md) and see that all changes are included and add the version + date at the top for the new release and commit the change.
 3. Run `./release.sh` (if all tests are ok on Travis feel free to run `./release.sh --yolo` to skip the tests)
 4. Choose version
 5. Login into Docker, add your 2FA when prompted
 6. When a new browser window opens at GitHub with the release, copy/paste the changes from the Changelog and add it instead of the commits.
-7. Commit the updated [version file](https://github.com/sitespeedio/sitespeed.io/blob/master/docs/_includes/version/browsertime.txt) and the [configuration file](https://github.com/sitespeedio/sitespeed.io/blob/master/docs/documentation/browsertime/configuration/config.md) in the sitespeed.io repo. Or make a PR if you do not have commit rights.
+7. Commit the updated [version file](https://github.com/sitespeedio/sitespeed.io/blob/main/docs/_includes/version/browsertime.txt) and the [configuration file](https://github.com/sitespeedio/sitespeed.io/blob/main/docs/documentation/browsertime/configuration/config.md) in the sitespeed.io repo. Or make a PR if you do not have commit rights.
 
 ### Contributing to the documentation
 The documentation lives in your cloned directory under *docs/*.

docs/documentation/sitespeed.io/docker/index.md

@@ -31,11 +31,11 @@ We have a three ready made containers:
 The Docker structure in the default container looks like this:
 
 [NodeJS with Ubuntu 18](https://github.com/sitespeedio/docker-node) -> [VisualMetrics dependencies](https://github.com/sitespeedio/docker-visualmetrics-deps) ->
-[Firefox/Chrome/xvfb](https://github.com/sitespeedio/docker-browsers) -> [sitespeed.io](https://github.com/sitespeedio/sitespeed.io/blob/master/Dockerfile)
+[Firefox/Chrome/xvfb](https://github.com/sitespeedio/docker-browsers) -> [sitespeed.io](https://github.com/sitespeedio/sitespeed.io/blob/main/Dockerfile)
 
 The first container installs NodeJS (latest LTS) on Ubuntu 18. The next one adds the dependencies (FFMpeg, ImageMagick and some Python libraries) needed to run [VisualMetrics](https://github.com/WPO-Foundation/visualmetrics). We then install specific version of Firefox, Chrome and lastly xvfb. Then in last step, we add sitespeed.io and tag it to the sitespeed.io version number.
 
-The [slim container](https://github.com/sitespeedio/sitespeed.io/blob/master/Dockerfile-slim) is based on [Debian Buster slim](https://github.com/debuerreotype/docker-debian-artifacts/blob/d6eeda93542f8e2a7d5f6e500b58fc4f12d055ce/buster/slim/Dockerfile). 
+The [slim container](https://github.com/sitespeedio/sitespeed.io/blob/main/Dockerfile-slim) is based on [Debian Buster slim](https://github.com/debuerreotype/docker-debian-artifacts/blob/d6eeda93542f8e2a7d5f6e500b58fc4f12d055ce/buster/slim/Dockerfile). 
 
 We lock down the browsers to specific versions for maximum compatibility and stability with sitespeed.io's current feature set; upgrading once we verify browser compatibility.
 {: .note .note-info}

docs/documentation/sitespeed.io/graphite/index.md

@@ -22,9 +22,9 @@ twitterdescription: Store your metrics in Graphite.
 [Graphite](https://graphiteapp.org/) store numeric time-series data and you can use that to store the metrics sitespeed.io collects. We provide an easy integration and you can use [our pre-made Docker container](https://hub.docker.com/r/sitespeedio/graphite/) and our [dashboard setup]({{site.baseurl}}/documentation/sitespeed.io/performance-dashboard/#up-and-running-in-almost-5-minutes) or use your current Graphite setup.
 
 ## Before you start
-If you are a new user of Graphite you need to read Etsys writeup about [Graphite](https://github.com/etsy/statsd/blob/master/docs/graphite.md) so you have an understanding of how the data is stored and how to configure the metrics. Also read [Graphite docs how to get metrics into graphite](https://graphite.readthedocs.io/en/latest/feeding-carbon.html#getting-your-data-into-graphite) for a better understanding of the metrics structure.
+If you are a new user of Graphite you need to read Etsys writeup about [Graphite](https://github.com/etsy/statsd/blob/main/docs/graphite.md) so you have an understanding of how the data is stored and how to configure the metrics. Also read [Graphite docs how to get metrics into graphite](https://graphite.readthedocs.io/en/latest/feeding-carbon.html#getting-your-data-into-graphite) for a better understanding of the metrics structure.
 
-In Graphite you configure for how long time you want to store metrics and at what precision, so it's good to check our default configuration ([this](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/graphite/conf/storage-aggregation.conf) and [this](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/graphite/conf/storage-schemas.conf)) before you start so you see that it matches your needs.
+In Graphite you configure for how long time you want to store metrics and at what precision, so it's good to check our default configuration ([this](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/graphite/conf/storage-aggregation.conf) and [this](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/graphite/conf/storage-schemas.conf)) before you start so you see that it matches your needs.
 
 
 ## Configure Graphite
@@ -33,7 +33,7 @@ The configuration depends on how often you want to run your tests. How long you
 
 Starting from sitespeed.io version 4 we send a moderated number of metrics per URL but you can [change that yourself]({{site.baseurl}}/documentation/sitespeed.io/metrics/).
 
-When you store metrics for a URL in Graphite, you decide from the beginning how long and how often you want to store the data, in [storage-schemas.conf](https://github.com/sitespeedio/docker-graphite-statsd/blob/master/conf/graphite/storage-schemas.conf). In our example Graphite setup, every key under sitespeed_io is caught by the configuration in storage-schemas.conf that looks like:
+When you store metrics for a URL in Graphite, you decide from the beginning how long and how often you want to store the data, in [storage-schemas.conf](https://github.com/sitespeedio/docker-graphite-statsd/blob/main/conf/graphite/storage-schemas.conf). In our example Graphite setup, every key under sitespeed_io is caught by the configuration in storage-schemas.conf that looks like:
 
 ~~~shell
 [sitespeed]
@@ -41,9 +41,9 @@ pattern = ^sitespeed_io\.
 retentions = 10m:60d,30m:90d
 ~~~
 
-Every metric that is sent to Graphite following the pattern (the namespace starting with sitespeed_io), Graphite prepares storage for it every ten minutes the first 60 days; after that Graphite uses the configuration in [storage-aggregation.conf](https://github.com/sitespeedio/docker-graphite-statsd/blob/master/conf/graphite/storage-aggregation.conf) to aggregate/downsize the metrics the next 90 days.
+Every metric that is sent to Graphite following the pattern (the namespace starting with sitespeed_io), Graphite prepares storage for it every ten minutes the first 60 days; after that Graphite uses the configuration in [storage-aggregation.conf](https://github.com/sitespeedio/docker-graphite-statsd/blob/main/conf/graphite/storage-aggregation.conf) to aggregate/downsize the metrics the next 90 days.
 
-Depending on how often you run your analysis, you may want to change the storage-schemas.conf. With the current config, if you analyse the same URL within 10 minutes, one of the runs will be discarded. But if you know you only run once an hour, you could increase the setting. Etsy has some really [good documentation](https://github.com/etsy/statsd/blob/master/docs/graphite.md) on how to configure Graphite.
+Depending on how often you run your analysis, you may want to change the storage-schemas.conf. With the current config, if you analyse the same URL within 10 minutes, one of the runs will be discarded. But if you know you only run once an hour, you could increase the setting. Etsy has some really [good documentation](https://github.com/etsy/statsd/blob/main/docs/graphite.md) on how to configure Graphite.
 
 In this example with retention of 10 minutes, the metrics you will send will be in Graphite with a 10 minute interval. If you have a larger interval for example one hour and send annotations on specific seconds, you can then see a larger missmatch between the annotation and when the actual metric got into Graphite. If you are sending metrics to Graphite on a per iteration basis the subsequent runs may be discarded as they arrive within the timeframe. Below is an example taking in closer to real-time metrics and falling back to the default retentions.
 
@@ -132,12 +132,12 @@ You need to create a new annotation setup in Grafana that matches the templates
 
 
 ## Dashboards
-We have [pre-made Grafana dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/master/dashboards/graphite) that works with Graphite. They are generic and as long as your [namespace](#namespace) consists of two parts, they will work. You can import them one by one or [inject them using Docker](https://github.com/sitespeedio/grafana-bootstrap-docker).
+We have [pre-made Grafana dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/main/dashboards/graphite) that works with Graphite. They are generic and as long as your [namespace](#namespace) consists of two parts, they will work. You can import them one by one or [inject them using Docker](https://github.com/sitespeedio/grafana-bootstrap-docker).
 
 ## Namespace
-The default namsespace when you send metrics to Graphite is *sitespeed_io.default*. You can change the namespace with `--graphite.namespace`. All premade dashboards are prepared to work with namespaces that starts with two parts: *first.second*. If you want more parts, the [default dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/master/dashboards/graphite) will break.
+The default namsespace when you send metrics to Graphite is *sitespeed_io.default*. You can change the namespace with `--graphite.namespace`. All premade dashboards are prepared to work with namespaces that starts with two parts: *first.second*. If you want more parts, the [default dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/main/dashboards/graphite) will break.
 
-When we use sitespeed.io we usually keep the first part (*sitespeed_io*) to separate metrics from other tools that sends metrics to Graphite.  We then change the second part: *sitespeed_io.desktop*,  *sitespeed_io.emulatedMobile* or *sitespeed_io.desktopSweden*. As long as your namespace has two parts, they will work with the [default dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/master/dashboards/graphite).
+When we use sitespeed.io we usually keep the first part (*sitespeed_io*) to separate metrics from other tools that sends metrics to Graphite.  We then change the second part: *sitespeed_io.desktop*,  *sitespeed_io.emulatedMobile* or *sitespeed_io.desktopSweden*. As long as your namespace has two parts, they will work with the [default dashboards](https://github.com/sitespeedio/grafana-bootstrap-docker/tree/main/dashboards/graphite).
 
 ## Warning: Crawling and Graphite
 If you crawl a site that is not static, you will pick up new pages each run or each day, which will make the Graphite database grow daily. When you add metrics to Graphite, it prepares space for those metrics ahead of time, depending on your storage configuration (in Graphite). If you configured Graphite to store individual metrics every 15 minutes for 60 days, Graphite will allocate storage for that URL: 4 (per hour) * 24 (hours per day) * 60 (days), even though you might only test that URL once.
@@ -177,7 +177,7 @@ If you are using Digital Ocean, you can setup the firewall rule in the admin. He
 ## Storing the data
 You probably gonna need to store the metrics in Graphite on another disk. If you are an AWS user, you can use and [setup an EBS volume](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html). If you use Digital Ocean you can follow their [quick start guide](https://www.digitalocean.com/docs/volumes/quickstart/).
 
-When your volume is mounted on your server that runs Graphite, you need to make sure Graphite uses the. Map the Graphite volume to the new volume outside of Docker (both Whisper and [graphite.db](https://github.com/sitespeedio/sitespeed.io/blob/master/docker/graphite/graphite.db)). Map them like this on your physical server (make sure to copy the empty [graphite.db](https://github.com/sitespeedio/sitespeed.io/raw/master/docker/graphite/graphite.db) file):
+When your volume is mounted on your server that runs Graphite, you need to make sure Graphite uses the. Map the Graphite volume to the new volume outside of Docker (both Whisper and [graphite.db](https://github.com/sitespeedio/sitespeed.io/blob/main/docker/graphite/graphite.db)). Map them like this on your physical server (make sure to copy the empty [graphite.db](https://github.com/sitespeedio/sitespeed.io/raw/main/docker/graphite/graphite.db) file):
  - `/path/on/server/whisper:/opt/graphite/storage/whisper`
  - `/path/on/server/graphite.db:/opt/graphite/storage/graphite.db`
 
@@ -185,10 +185,10 @@ If you use Grafana annotations, you should make sure grafana.db is outside of th
 
 ## Graphite for production (important!)
 
-1. Make sure you have [configured storage-aggregation.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/graphite/conf/storage-aggregation.conf) in Graphite to fit your needs.
-2. Configure your [storage-schemas.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/graphite/conf/storage-schemas.conf) how long you wanna store your metrics.
-3. *MAX_CREATES_PER_MINUTE* is usually quite low in [carbon.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/graphite/conf/carbon.conf). That means you will not get all the metrics created for the first run, so you can increase it.
-4. Map the Graphite volume to a physical directory outside of Docker to have better control (both Whisper and [graphite.db](https://github.com/sitespeedio/sitespeed.io/blob/master/docker/graphite/graphite.db)). Map them like this on your physical server (make sure to copy the empty [graphite.db](https://github.com/sitespeedio/sitespeed.io/blob/master/docker/graphite/graphite.db) file):
+1. Make sure you have [configured storage-aggregation.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/graphite/conf/storage-aggregation.conf) in Graphite to fit your needs.
+2. Configure your [storage-schemas.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/graphite/conf/storage-schemas.conf) how long you wanna store your metrics.
+3. *MAX_CREATES_PER_MINUTE* is usually quite low in [carbon.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/graphite/conf/carbon.conf). That means you will not get all the metrics created for the first run, so you can increase it.
+4. Map the Graphite volume to a physical directory outside of Docker to have better control (both Whisper and [graphite.db](https://github.com/sitespeedio/sitespeed.io/blob/main/docker/graphite/graphite.db)). Map them like this on your physical server (make sure to copy the empty [graphite.db](https://github.com/sitespeedio/sitespeed.io/blob/main/docker/graphite/graphite.db) file):
  - /path/on/server/whisper:/opt/graphite/storage/whisper
  - /path/on/server/graphite.db:/opt/graphite/storage/graphite.db
  If you use Grafana annotations, you should make sure grafana.db is outside of the container. Follow the documentation at [grafana.org](http://docs.grafana.org/installation/docker/#grafana-container-using-bind-mounts).

docs/documentation/sitespeed.io/index.md

@@ -13,7 +13,7 @@ twitterdescription: Documentation for sitespeed.io.
 
 <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.
+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/main/CHANGELOG.md) for the project.
 
 ## Start
  * [Introduction](introduction/) - start here if you are new to the project or web performance testing.

docs/documentation/sitespeed.io/installation/index.md

@@ -44,7 +44,7 @@ That will output the data from the run in the current directory. You can read mo
 
 Prerequisites: Install [latest NodeJS LTS](https://nodejs.org/en/download/) ([Linux](https://github.com/creationix/nvm)) and make sure you have [npm](https://github.com/npm/npm) or [yarn](https://yarnpkg.com/) installed. Also install Chrome/Firefox (you need them to collect metrics).
 
-Make sure you install without sudo using sudo. Checkout [Sindre Sorhus guide](https://github.com/sindresorhus/guides/blob/master/npm-global-without-sudo.md).
+Make sure you install without sudo using sudo. Checkout [Sindre Sorhus guide](https://github.com/sindresorhus/guides/blob/main/npm-global-without-sudo.md).
 
 #### npm
 If you prefer npm, just run:

docs/documentation/sitespeed.io/mobile-phones/index.md

@@ -99,7 +99,7 @@ You could also use [phuedxs](https://github.com/phuedx) [Pi Network Conditioner]
 
 ### Video and SpeedIndex
 
-You can also collect a video and get Visual Metrics. Running on Mac or without Docker you need to install the requirements for [VisualMetrics](https://github.com/sitespeedio/docker-visualmetrics-deps/blob/master/Dockerfile) yourself on your machine before you start. If you have everything setup you can run:
+You can also collect a video and get Visual Metrics. Running on Mac or without Docker you need to install the requirements for [VisualMetrics](https://github.com/sitespeedio/docker-visualmetrics-deps/blob/main/Dockerfile) yourself on your machine before you start. If you have everything setup you can run:
 
 ```bash
 sitespeed.io --android --video --visualMetrics https://www.sitespeed.io

docs/documentation/sitespeed.io/performance-dashboard/index.md

@@ -24,7 +24,7 @@ You need [Docker](https://docs.docker.com/engine/installation/) and [Docker Comp
 
 # Up and running in (almost) 5 minutes
 
-1. Download our Docker compose file: <code>curl -O https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/docker-compose.yml</code>
+1. Download our Docker compose file: <code>curl -O https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/docker-compose.yml</code>
 2. Run: <code>docker-compose up -d</code> (make sure you run the latest [Docker compose](https://docs.docker.com/compose/install/) version)
 3. Run sitespeed to get some metrics: <code> docker run --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io:{% include version/sitespeed.io.txt %} --graphite.host=host.docker.internal</code> (running on Linux? [Check how to access localhost]({{site.baseurl}}/documentation/sitespeed.io/docker/#access-localhost)).
 4. Access the dashboard: http://127.0.0.1:3000
@@ -32,12 +32,12 @@ You need [Docker](https://docs.docker.com/engine/installation/) and [Docker Comp
 6. To start from scratch, also remove the Graphite and Grafana data volumes by running `docker volume rm performancedashboard_graphite performancedashboard_grafana`.
 
 
-If you want to play with the dashboards, the default login is sitespeedio and password is ...well check out the [docker-compose.yml file](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/docker-compose.yml).
+If you want to play with the dashboards, the default login is sitespeedio and password is ...well check out the [docker-compose.yml file](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/docker-compose.yml).
 
 When you run this in production make sure to checkout [our production guidelines](#production-guidelines).
 
 ## Docker compose file
-We have prepared a Docker Compose file that downloads and sets up Graphite/Grafana and sitespeed.io with a couple of example dashboards. It works perfectly when you want to try it out on localhost, but if you want to run it in production, you should modify it by making sure that the metrics are stored outside of your container/volumes. If you prefer InfluxDB over Graphite, you can use that too, but right now we only have [one ready-made dashboard](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/master/dashboards/influxdb/pageSummary.json) for InfluxDB (thank you Olivier Jan for contributing to that dashboard!).
+We have prepared a Docker Compose file that downloads and sets up Graphite/Grafana and sitespeed.io with a couple of example dashboards. It works perfectly when you want to try it out on localhost, but if you want to run it in production, you should modify it by making sure that the metrics are stored outside of your container/volumes. If you prefer InfluxDB over Graphite, you can use that too, but right now we only have [one ready-made dashboard](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/main/dashboards/influxdb/pageSummary.json) for InfluxDB (thank you Olivier Jan for contributing to that dashboard!).
 
 ## Pre-made dashboards
 We insert ready-made dashboards with a Docker container using curl, making it easy for you to get started. You can check out the container with the dashboards here: [https://github.com/sitespeedio/grafana-bootstrap-docker](https://github.com/sitespeedio/grafana-bootstrap-docker)
@@ -125,10 +125,10 @@ To run this in production (=not on your local dev machine) you should make some
     - Run Grafana/Graphite on another server instance.
 2. Change the default user and password for Grafana.
 3. Change the default [user and password for Graphite](https://hub.docker.com/r/sitespeedio/graphite/).
-4. Make sure you have [configured storage-aggregation.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/graphite/conf/storage-aggregation.conf) in Graphite to fit your needs.
-5. Configure your [storage-schemas.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/graphite/conf/storage-schemas.conf) how long you wanna store your metrics.
-6. *MAX_CREATES_PER_MINUTE* is usually quite low in [carbon.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/graphite/conf/carbon.conf). That means you will not get all the metrics created for the first run, so you can increase it.
-7. Map the Graphite volume to a physical directory outside of Docker to have better control (both Whisper and [graphite.db](https://github.com/sitespeedio/sitespeed.io/blob/master/docker/graphite/graphite.db)). Map them like this on your physical server (make sure to copy the empty [graphite.db]((https://github.com/sitespeedio/sitespeed.io/blob/master/docker/graphite/graphite.db)) file):
+4. Make sure you have [configured storage-aggregation.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/graphite/conf/storage-aggregation.conf) in Graphite to fit your needs.
+5. Configure your [storage-schemas.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/graphite/conf/storage-schemas.conf) how long you wanna store your metrics.
+6. *MAX_CREATES_PER_MINUTE* is usually quite low in [carbon.conf](https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/docker/graphite/conf/carbon.conf). That means you will not get all the metrics created for the first run, so you can increase it.
+7. Map the Graphite volume to a physical directory outside of Docker to have better control (both Whisper and [graphite.db](https://github.com/sitespeedio/sitespeed.io/blob/main/docker/graphite/graphite.db)). Map them like this on your physical server (make sure to copy the empty [graphite.db]((https://github.com/sitespeedio/sitespeed.io/blob/main/docker/graphite/graphite.db)) file):
  - /path/on/server/whisper:/opt/graphite/storage/whisper
  - /path/on/server/graphite.db:/opt/graphite/storage/graphite.db
 8. Remove the sitespeedio/grafana-bootstrap from the Docker compose file, you only need that for the first run.

docs/documentation/sitespeed.io/plugins/index.md

@@ -35,7 +35,7 @@ The following plugins are enabled: assets,browsertime,coach,domains,ithubhtml
 ...
 ~~~
 
-The default plugins lives in the [plugin folder](https://github.com/sitespeedio/sitespeed.io/tree/master/lib/plugins). This is a good starting place to look at if you wanna build your own plugin.
+The default plugins lives in the [plugin folder](https://github.com/sitespeedio/sitespeed.io/tree/main/lib/plugins). This is a good starting place to look at if you wanna build your own plugin.
 
 ## Disable a plugin
 You can remove/disable default plugins if needed. For instance you may not want to output HTML and strictly send the data to Graphite.
@@ -173,11 +173,11 @@ The *context* holds information for this specific run that generated at runtime
 }
 ~~~
 
-You can checkout the [StorageManager](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/core/resultsStorage/storageManager.js),
-[messageMaker](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/support/messageMaker.js),
-[statsHelpers](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/support/statsHelpers.js) and [filterRegistry](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/support/filterRegistry.js) to get feel how you can use them.
+You can checkout the [StorageManager](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/core/resultsStorage/storageManager.js),
+[messageMaker](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/support/messageMaker.js),
+[statsHelpers](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/support/statsHelpers.js) and [filterRegistry](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/support/filterRegistry.js) to get feel how you can use them.
 
-The *options* are the options that a user will supply in the CLI, checkout the [CLI implementation](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/support/cli.js) to see all the options.
+The *options* are the options that a user will supply in the CLI, checkout the [CLI implementation](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/support/cli.js) to see all the options.
 
 ### processMessage(message, queue)
 The processMessage function in your plugin is called for each and every message that is passed in the application. So what's a message you may ask? Everything is a message in sitespeed.io.:) A message contains the following information:
@@ -287,7 +287,7 @@ queue.postMessage(
 );
 ~~~
 
-You can look at the standalone [GPSI plugin](https://github.com/sitespeedio/plugin-gpsi) or the [WebPageTest plugin](https://github.com/sitespeedio/sitespeed.io/tree/master/lib/plugins/webpagetest) as an example plugin that both sends run and pageSummary data.
+You can look at the standalone [GPSI plugin](https://github.com/sitespeedio/plugin-gpsi) or the [WebPageTest plugin](https://github.com/sitespeedio/sitespeed.io/tree/main/lib/plugins/webpagetest) as an example plugin that both sends run and pageSummary data.
 
 ## Let your plugin collect metrics using Browsertime
 
@@ -342,10 +342,10 @@ queue.postMessage(make('budget.addMessageType', {type: 'gpsi.pagesummary'}));
 ~~~
 
 ## Testing your plugin
-If your plugin lives on GitHub you should check out our [example Travis-ci file](https://github.com/sitespeedio/plugin-gpsi/blob/master/.travis.yml) for the GPSI plugin. In the example, we checkout the sitespeed.io project and run the plugin against the latest master (we also run it daily in the Travis crontab).
+If your plugin lives on GitHub you should check out our [example Travis-ci file](https://github.com/sitespeedio/plugin-gpsi/blob/main/.travis.yml) for the GPSI plugin. In the example, we checkout the sitespeed.io project and run the plugin against the latest main (we also run it daily in the Travis crontab).
 
 ## Example plugin(s)
-You can look at the standalone [GPSI plugin](https://github.com/sitespeedio/plugin-gpsi) or the [WebPageTest plugin](https://github.com/sitespeedio/sitespeed.io/tree/master/lib/plugins/webpagetest).
+You can look at the standalone [GPSI plugin](https://github.com/sitespeedio/plugin-gpsi) or the [WebPageTest plugin](https://github.com/sitespeedio/sitespeed.io/tree/main/lib/plugins/webpagetest).
 
 ## Find plugins
 We keep a list of plugins at [https://github.com/sitespeedio/plugins](https://github.com/sitespeedio/plugins). If you wanna add your plugin, send a PR!

docs/documentation/sitespeed.io/thirdparty/index.md

@@ -24,7 +24,7 @@ There are two ways two categorise first/third parties. If you use  `--firstParty
 
 One thing to remember is that a tool can have multiple categories. For example, it can be both a analytics tool AND a [surveillance](https://en.wikipedia.org/wiki/Surveillance_capitalism) tool.
 
-By default the third party information will be sent to Graphite/InfluxDb and if you are a Graphite user you can upgrade the page summary dashboard to [the latest version](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/master/dashboards/graphite/PageSummary.json). You will then get two new graphs.
+By default the third party information will be sent to Graphite/InfluxDb and if you are a Graphite user you can upgrade the page summary dashboard to [the latest version](https://github.com/sitespeedio/grafana-bootstrap-docker/blob/main/dashboards/graphite/PageSummary.json). You will then get two new graphs.
 
 The first graph shows you third party requests by category. Here can you see how many requests each category generates.
 
@@ -45,7 +45,7 @@ And then also see the exact tools that are used.
 ![Third party tools]({{site.baseurl}}/img/8.9/thirdparty-tools-html.png)
 {: .img-thumbnail}
 
-At the moment we are very liberate on categorising tools as surveillance and need your help to get it right. Do a PR to help us help by changing [https://github.com/sitespeedio/sitespeed.io/blob/master/lib/plugins/thirdparty/index.js#L34-L38](https://github.com/sitespeedio/sitespeed.io/blob/master/lib/plugins/thirdparty/index.js#L34-L38).
+At the moment we are very liberate on categorising tools as surveillance and need your help to get it right. Do a PR to help us help by changing [https://github.com/sitespeedio/sitespeed.io/blob/main/lib/plugins/thirdparty/index.js#L34-L38](https://github.com/sitespeedio/sitespeed.io/blob/main/lib/plugins/thirdparty/index.js#L34-L38).
 
 The new categorisation happens automatically.
 

docs/documentation/sitespeed.io/video/index.md

@@ -19,7 +19,7 @@ twitterdescription: Use the video in sitespeed.io
 ## The stack (easy with Docker)
 We use FFMpeg to record a video with 30 fps of the screen (but you can configure the number of frames per second). The easiest way is to use our Docker container with pre-installed FFMpeg and if you use the npm version, you can record a video too. Video works on Linux and OS X at the moment.
 
-When we got the video we use [Visual Metrics](https://github.com/WPO-Foundation/visualmetrics) (built by Pat Meenan) to analyse the video and get SpeedIndex and other visual metrics from the video. If you use our Docker container you get that for free, else you need to install all the [Visual Metrics dependencies](https://github.com/sitespeedio/browsertime/blob/master/.travis.yml) yourself. You need FFMPeg, ImageMagick and a couple Pythin libraries. Checkout Browsertimes [Travis-CI configuration](https://github.com/sitespeedio/browsertime/blob/master/.travis.yml) to see what's needed.
+When we got the video we use [Visual Metrics](https://github.com/WPO-Foundation/visualmetrics) (built by Pat Meenan) to analyse the video and get SpeedIndex and other visual metrics from the video. If you use our Docker container you get that for free, else you need to install all the [Visual Metrics dependencies](https://github.com/sitespeedio/browsertime/blob/main/.travis.yml) yourself. You need FFMPeg, ImageMagick and a couple Pythin libraries. Checkout Browsertimes [Travis-CI configuration](https://github.com/sitespeedio/browsertime/blob/main/.travis.yml) to see what's needed.
 
 We record the video in two steps: First we turn the background orange (that is used by VisualMetrics to know when the navigation starts), sets the background to white and let the browser go to the URL. The video is recorded lossless and then when the video has been analysed, we remove the orange frames and convert the video to a compressed mp4.
 
@@ -78,7 +78,7 @@ You can also configure to pickup your own defined elements with <code>--scriptIn
 ## Compare two video runs (combine two videos)
 One of the things we love with [WebPageTest](https://www.webpagetest.org/) is the video where you can compare two different runs. Since sitespeed.io is serverless, it is nothing you can do on the fly. Instead we created a simple tool you can use. Only thing you need is Docker!
 
-1. <code>curl -O https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/tools/combineVideos.sh<code>
+1. <code>curl -O https://raw.githubusercontent.com/sitespeedio/sitespeed.io/main/tools/combineVideos.sh<code>
 2. <code>chmod +x combineVideos.sh<code>
 3. Download the videos you want to compare, let us call them file1.mp4 and file2.mp4
 4. <code>./combineVideos.sh file1.mp4 file2.mp4 </code>

docs/documentation/sitespeed.io/webpagereplay/index.md

@@ -17,7 +17,7 @@ twitterdescription: Use WebPageReplay and sitespeed.io.
 * Lets place the TOC here
 {:toc}
 
-[WebPageReplay](https://github.com/catapult-project/catapult/blob/master/web_page_replay_go/README.md) is a 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. We have integrated WebPageReplay in both Browsertime and sitespeed.io Docker containers to make it easier to use.
+[WebPageReplay](https://github.com/catapult-project/catapult/blob/main/web_page_replay_go/README.md) is a 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. We have integrated WebPageReplay in both Browsertime and sitespeed.io Docker containers to make it easier to use.
 
 There also other replay proxies like [mahimahi](http://mahimahi.mit.edu/) but that version doesn't support HTTP2 by default. We will happily include other proxies in the future.
 
@@ -39,7 +39,7 @@ What's cool about how we include WebPageReplay is that the only thing you need t
 
 You can pass on any parameter to sitespeed.io/browsertime as usual.
 
-WebPageReplay tries to do each page load as deterministic as possible. It's done by making the JavaScript Date deterministic (see [deterministic.js)](https://github.com/sitespeedio/sitespeed.io/blob/master/docker/webpagereplay/deterministic.js). That means if you use JavaScript Date in you `--pageCompleteCheck` you need to change that. We do that by default.
+WebPageReplay tries to do each page load as deterministic as possible. It's done by making the JavaScript Date deterministic (see [deterministic.js)](https://github.com/sitespeedio/sitespeed.io/blob/main/docker/webpagereplay/deterministic.js). That means if you use JavaScript Date in you `--pageCompleteCheck` you need to change that. We do that by default.
 
 ## The metrics
 

docs/documentation/throttle/index.md

@@ -19,7 +19,7 @@ twitterdescription:
 
 **Throttle lets you *simulate slow network connections* on Linux and Mac OS X.**
 
-Throttle uses *pfctl* on Mac and *tc* on Linux (you also need *ip* and *route* for Throttle to work on Linux) to simulate different network speeds and is inspired by [tylertreat/Comcast](https://github.com/tylertreat/Comcast), the [connectivity setting in the WPTAgent](https://github.com/WPO-Foundation/wptagent/blob/master/internal/traffic_shaping.py) and [sltc](https://github.com/sitespeedio/sltc).
+Throttle uses *pfctl* on Mac and *tc* on Linux (you also need *ip* and *route* for Throttle to work on Linux) to simulate different network speeds and is inspired by [tylertreat/Comcast](https://github.com/tylertreat/Comcast), the [connectivity setting in the WPTAgent](https://github.com/WPO-Foundation/wptagent/blob/main/internal/traffic_shaping.py) and [sltc](https://github.com/sitespeedio/sltc).
 
 **What is Throttle good for?**
 
@@ -90,7 +90,7 @@ throttle stop
 ```
 
 ## Add delay on your localhost (Linux only at the moment)
-This is useful if you run [WebPageReplay](https://github.com/catapult-project/catapult/blob/master/web_page_replay_go/README.md) and want to add some latency to your tests.
+This is useful if you run [WebPageReplay](https://github.com/catapult-project/catapult/blob/main/web_page_replay_go/README.md) and want to add some latency to your tests.
 
 ```bash
 throttle --rtt 200 --localhost

docs/important/index.md

@@ -19,7 +19,7 @@ twitterdescription: Learn more on how we work with privacy, COC and sustainabili
 A couple of important things to know about our projects.
 
 ### Changelog and versioning
-We always keep a CHANGELOG in the root of directory of the project. [Here's](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md) the one we have for sitespeed.io. We always write down the changes we do in the project.
+We always keep a CHANGELOG in the root of directory of the project. [Here's](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md) the one we have for sitespeed.io. We always write down the changes we do in the project.
 
 We always use [semantic versioning](http://semver.org/) when we do a release.
 
@@ -27,10 +27,10 @@ We always use [semantic versioning](http://semver.org/) when we do a release.
 We take your online privacy really serious: Our [documentation site](https://www.sitespeed.io/), our [dashboard](https://dashboard.sitespeed.io) and our [compare tool](https://compare.sitespeed.io) do not use any tracking software at all (no Google Analytics or any other tracking software). We never use tracking software. None of the sitespeed.io tools call home. You can read more about privacy at our [Privacy Policy](../privacy-policy/) page.
 
 ### Code of Conduct
-When you create issues, do pull requests, use our Slack channel or contact us on email, please follow our [Code Of Conduct](https://github.com/sitespeedio/sitespeed.io/blob/master/CODE_OF_CONDUCT.md).
+When you create issues, do pull requests, use our Slack channel or contact us on email, please follow our [Code Of Conduct](https://github.com/sitespeedio/sitespeed.io/blob/main/CODE_OF_CONDUCT.md).
 
 ### Open Source
-We release our software under the [MIT License](https://github.com/sitespeedio/sitespeed.io/blob/master/LICENSE) or [Apache License 2.0](https://github.com/sitespeedio/browsertime/blob/master/LICENSE). Please respect it and respect our work: We ask you not to change the logo or the contribution to the project. Please do this to pay the respect to the many hours we put down into the project.
+We release our software under the [MIT License](https://github.com/sitespeedio/sitespeed.io/blob/main/LICENSE) or [Apache License 2.0](https://github.com/sitespeedio/browsertime/blob/main/LICENSE). Please respect it and respect our work: We ask you not to change the logo or the contribution to the project. Please do this to pay the respect to the many hours we put down into the project.
 
 ### Code and releases
 We try to have issues for everything we do (sometimes when there are small technical changes we miss that), we do PRs. Big PRs we always review them within the team.

docs/release-notes/1.3/index.html

@@ -27,6 +27,6 @@ Sitespeed 1.3 was relased the 15th of November 2012. The main goal with the rele
 	  <li>Added support for testing only one page (depth = 0), thanks <a href="https://github.com/tomsutton1984" target="_blank">@tomsutton1984</a> for the idea</li>
 	  </ul>
 <p>	
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>	
       </div>

docs/release-notes/1.4/index.html

@@ -65,5 +65,5 @@ Sitespeed 1.4 was released the 5th of December 2012. The main goal with the rele
 <p>Also the <a href="{{site.baseurl}}/documentation/">documentation</a> has been reworked.</p>
 
 <p>	
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>

docs/release-notes/1.5/index.html

@@ -52,5 +52,5 @@ Sitespeed 1.5 was released the 6th of January 2013 with the following changes:
 
 
 <p>	
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past and the next <a href="https://github.com/soulgalore/sitespeed.io/issues?milestone=15&state=open">milestone</a> what will come in the next release.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past and the next <a href="https://github.com/soulgalore/sitespeed.io/issues?milestone=15&state=open">milestone</a> what will come in the next release.
 </p>

docs/release-notes/1.6/index.html

@@ -88,7 +88,7 @@ twitterdescription: The new release contains a really easy way to identify which
   <p>The Java code used by sitespeed is now compiled for Java 1.6, so 1.7 is no longer the requirement.</p>
   <hr>
   <p>
-    See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in
+    See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in
     the past and the next <a
       href="https://github.com/soulgalore/sitespeed.io/issues?milestone=16&state=open">milestone</a> what will come in
     the next release.

docs/release-notes/1.7/index.html

@@ -91,5 +91,5 @@ http://peterhedenskog.com/music/
 </p>
 <hr>
 <p>	
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past and the next <a href="https://github.com/soulgalore/sitespeed.io/issues?milestone=17&state=open">milestone</a> what will come in the next release.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past and the next <a href="https://github.com/soulgalore/sitespeed.io/issues?milestone=17&state=open">milestone</a> what will come in the next release.
 </p>

docs/release-notes/1.8.1/index.html

@@ -29,5 +29,5 @@ twitterdescription: Yes box, here are some really nice bug fixes.
 
 <hr>
 <p>	
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>

docs/release-notes/1.8.2/index.html

@@ -33,5 +33,5 @@ twitterdescription: This release let you export the pages info as CSV, better er
 
 <hr>
 <p>	
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>

docs/release-notes/1.8.3/index.html

@@ -22,5 +22,5 @@ twitterdescription: This release fixes & makes thing clenar if there is problem
 <p>And there is one new small feature: You can now supply a test name that will be showed on all test result pages (using the parameter <em>n</em>). See an example <a href="{{site.baseurl}}/documentation/#name">here</a>.</p>
 <hr>
 <p>	
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>

docs/release-notes/1.8/index.html

@@ -54,5 +54,5 @@ The summary page used to report average values of all different metrics. That ha
 </p>
 <hr>
 <p>	
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>

docs/release-notes/2.0/index.html

@@ -62,5 +62,5 @@ twitterdescription: The 2.0 release is here! Test multiple sites with one go, co
 
 <hr>
 <p>	
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>

docs/release-notes/2.1.1/index.html

@@ -23,5 +23,5 @@ twitterdescription: This release fixes
 </ul>
 <hr>
 <p>
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>

docs/release-notes/2.1/index.html

@@ -47,6 +47,6 @@ twitterdescription: The 2.1 release makes it possible to break builds using Jenk
 
 <hr>
 <p>
-  See the <a href="https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in
+  See the <a href="https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in
   the past.
 </p>

docs/release-notes/2.2.2/index.html

@@ -20,5 +20,5 @@ twitterdescription: This release fixes a couple of small bugs.
 </ul>
 <hr>
 <p>
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>

docs/release-notes/2.2/index.html

@@ -28,5 +28,5 @@ twitterdescription: Sitespeed.io 2.2 release focus on packaging for Homebrew.
 </ul>
 <hr>
 <p>
-See the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changelog</a> for changes done in the past.
+See the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changelog</a> for changes done in the past.
 </p>

docs/release-notes/2.4/index.html

@@ -37,5 +37,5 @@ twitterdescription: Sitespeed.io 2.4 focus on adding extra value on the defaut s
 </ul>
 <hr>
 <p>
-See all the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changes</a> done in this release.
+See all the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changes</a> done in this release.
 </p>

docs/release-notes/2.5/index.html

@@ -41,5 +41,5 @@ twitterdescription: Sitespeed.io 2.5 makes it possible to test in multiple brows
 </p>
 <hr>
 <p>
-See all the <a href="https://github.com/soulgalore/sitespeed.io/blob/master/CHANGELOG">changes</a> done in this release.
+See all the <a href="https://github.com/soulgalore/sitespeed.io/blob/main/CHANGELOG">changes</a> done in this release.
 </p>

docs/release-notes/3.2/index.md

@@ -24,4 +24,4 @@ Interesting new stuff in the 3.1.x releases:
  * Upgraded BrowserTime that works as it should on Windows.
  * Send domain timings to Graphite and timings per request.
  * No robot removed from the HTML pages.
- * Many small bug fixes, checkout the [complete list](https://github.com/sitespeedio/sitespeed.io/blob/master/CHANGELOG.md).
+ * Many small bug fixes, checkout the [complete list](https://github.com/sitespeedio/sitespeed.io/blob/main/CHANGELOG.md).

docs/sponsor/index.md

@@ -20,7 +20,7 @@ There's a couple of ways you can help us building sitespeed.io:
 ## Why should you sponsor?
 Sponsorships will help us continue working on open source software, keeping the documentation updated and upgrade and add more test servers (we only run two at the moment) that makes sure our releases are as bug free as possible.
 
-At the moment we run two servers sponsored by Digital Ocean: One running Grafana/Graphite/InfluxDB and one instance that runs the latest commit in master for sitespeed.io and collect metrics using [https://github.com/sitespeedio/dashboard.sitespeed.io](https://github.com/sitespeedio/dashboard.sitespeed.io). 
+At the moment we run two servers sponsored by Digital Ocean: One running Grafana/Graphite/InfluxDB and one instance that runs the latest commit in main for sitespeed.io and collect metrics using [https://github.com/sitespeedio/dashboard.sitespeed.io](https://github.com/sitespeedio/dashboard.sitespeed.io). 
 
 We want to run at least one more instance to be able to test changes direct in Browsertime. That would help us a lot finding issues earlier. With sponsor money we could also choose to use other cloud providers and making it easier to deploy sitespeed.io.
 

lib/plugins/html/templates/footer.pug

@@ -5,4 +5,4 @@ footer
     | #{' '} #{version} #{' by '}
     a(href='https://www.sitespeed.io/aboutus/') the sitespeed.io team
     | #{' and '}
-    a(href='https://github.com/sitespeedio/sitespeed.io/blob/master/CONTRIBUTORS.md') contributors
+    a(href='https://github.com/sitespeedio/sitespeed.io/blob/main/CONTRIBUTORS.md') contributors