toc in the doc
This commit is contained in:
parent
64a66a0a4f
commit
895a55f6ed
|
|
@ -8,18 +8,22 @@ nav: documentation
|
|||
image: https://www.sitespeed.io/img/sitespeed-2.0-twitter.png
|
||||
twitterdescription:
|
||||
---
|
||||
# Browsertime
|
||||
|
||||
<img src="{{site.baseurl}}/img/logos/browsertime.png" class="pull-right img-big" alt="Browsertime logo" width="200" height="175">
|
||||
|
||||
# Browsertime
|
||||
{:.no_toc}
|
||||
|
||||
Access the Web Performance Timeline, from your browser, in your terminal!
|
||||
|
||||
Browsertime allows you to:
|
||||
|
||||
* Query timing data directly from the browser, to access [Navigation Timing](http://kaaes.github.io/timing/info.html), [User Timing](http://www.html5rocks.com/en/tutorials/webperformance/usertiming/),
|
||||
* Query timing data directly from the browser, to access [Navigation Timing](http://kaaes.github.io/timing/info.html), [User Timing](http://www.html5rocks.com/en/tutorials/webperformance/usertiming/),
|
||||
[Resource Timing](http://www.w3.org/TR/resource-timing/), first paint and [RUM Speed Index](https://github.com/WPO-Foundation/RUM-SpeedIndex).
|
||||
* Generate [HAR](http://www.softwareishard.com/blog/har-12-spec/) files
|
||||
* Run custom Javascript scripts in the browser and get statistics for each run.
|
||||
* Generate [HAR](http://www.softwareishard.com/blog/har-12-spec/) files
|
||||
* Run custom Javascript scripts in the browser and get statistics for each run.
|
||||
|
||||
* Lets place the TOC here
|
||||
{:toc}
|
||||
|
||||
## A simple example
|
||||
|
||||
|
|
|
|||
|
|
@ -9,11 +9,15 @@ image: https://www.sitespeed.io/img/sitespeed-2.0-twitter.png
|
|||
twitterdescription:
|
||||
---
|
||||
# PageXray
|
||||
{:.no_toc}
|
||||
|
||||
<img src="{{site.baseurl}}/img/logos/pagexray.png" class="pull-right img-big" alt="PageXray logo" width="365" height="200">
|
||||
|
||||
We love the HAR file, but it's hard to actually see what the page includes only looking at the file. PageXray converts a HAR file to a JSON format that is easier to read. We use the format internally in the coach and sitespeed.io.
|
||||
|
||||
* Lets place the TOC here
|
||||
{:toc}
|
||||
|
||||
## What do we collect?
|
||||
|
||||
* The size and the number of requests per content type
|
||||
|
|
|
|||
Loading…
Reference in New Issue