mirror
/
sitespeed.io
mirror of https://github.com/sitespeedio/sitespeed.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: link to the wpt repo

This commit is contained in:
soulgalore 2020-12-21 22:19:13 +01:00
parent d8e60acb77
commit 07244c8cae
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/_posts/2020-12-21-sitespeed.io-16.0-browsertime-11.0-coach.md
View File

@ -91,7 +91,7 @@ We have some bug fixes too, especially if you test on Android. You can check the
First off, we have a breaking change if you use the WebPageTest plugin. We moved that to a new repository.
### WebPageTest plugin got a new repository
We moved out the WebPageTest plugin to a new repository. It will still work as before, but you need install the plugin or run the WebPageTest container (```docker run --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io:16.0.0-webpagetest https://www.sitespeed.io --plugins.add /webpagetest --webpagetest.key KEY```):
We moved out the WebPageTest plugin to [a new repository](https://github.com/sitespeedio/plugin-webpagetest). It will still work as before, but you need install the plugin or run the WebPageTest container (```docker run --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io:16.0.0-webpagetest https://www.sitespeed.io --plugins.add /webpagetest --webpagetest.key KEY```):
There's a couple of reasons:
1. It's easier to focus on the core functionality with Browsertime. Some people [still](https://twitter.com/drewpost/status/1306206907313598469) think sitespeed.io is built on top of WebPageTest. That is not true. It's built on top of Browsertime, our own engine ([used by Mozilla](https://blog.mozilla.org/performance/2020/12/15/2020-year-in-review/) to test performance regressions). But you can use WebPageTest as complement directly from sitespeed.io as you can with Lighthouse and other tools.