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

typeos

This commit is contained in:
soulgalore 2017-03-01 22:56:06 +01:00
parent fc87fe3603
commit 9ff1136d86
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -27,12 +27,12 @@ You then have network called cable that you can use from your Docker container b
$ docker run --privileged --shm-size=1g --network=cable --rm sitespeedio/sitespeed.io -c cable --browsertime.connectivity.engine external https://www.sitespeed.io/
~~~
You have more examples [here]({{site.baseurl}}/documentation/sitespeed.io/browsers/#change-connectivity) and would love feedback and PR on how to do the same on platforms not supporting tc.
You have more examples [here]({{site.baseurl}}/documentation/sitespeed.io/browsers/#change-connectivity) and would love feedback and PRs on how to do the same on platforms not supporting tc.
## Get that timeline
You can now turn on the trace log for Chrome when you analyze a page. The trace log will be saved to disk and you can drag and drop it into the Timeline in Chrome. This also works if you run Chrome on your Android phone. We also added support for doing the same with WebPageTest (you could turn on Timeline before but we didn't automatically fetch it).
As an extra bonus, there'a a Chrome trace message that is passed inside sitespeed.io when the trace is collected so your plugin can collect it and analyze the data. Look out from *browsertime.chrometrace* and *webpagetest.chrometrace* messages to pickup the trace. We are looking forward to the first plugin that will use it :)
As an extra bonus, there's a Chrome trace message that is passed inside sitespeed.io when the trace is collected so your plugin can collect it and analyze the data. Look out from *browsertime.chrometrace* and *webpagetest.chrometrace* messages to pickup the trace. We are looking forward to the first plugin that will use it :)
Turn on the log with <code>--browsertime.chrome.dumpTraceCategoriesLog</code>, unpack the file and drop it in your timeline in dev-tools in Chrome.
@ -43,7 +43,7 @@ Turn on the log with <code>--browsertime.chrome.dumpTraceCategoriesLog</code>, u
One important thing: Collecting trace logs can affect your metrics if you run on a slow machine.
## Easier to configure Chrome/Firefox
We added CLI options for setting Firefox preferences (<code>--browsertime.firefox.preference</code>), and Chrome browser CLI args (<code>--browsertime.chrome.args</code>).
We added CLI options for setting Firefox preferences (<code>--browsertime.firefox.preference</code>) and Chrome browser CLI args (<code>--browsertime.chrome.args</code>).
## Collect the HTML body in the HAR for Firefox
You can include the HTML in the HAR file by adding the flag <code>--browsertime.firefox.includeResponseBodies</code> so you can keep track of what is actually served from your server.