Skip to content

Commit

Permalink
Remove legacy browser metrics
Browse files Browse the repository at this point in the history
These are no longer being emitted by the browser module. Web vitals are
the primary way to determine how well the website is performing.
  • Loading branch information
ankur22 committed Jun 19, 2023
1 parent fd489a2 commit 29767f6
Show file tree
Hide file tree
Showing 3 changed files with 0 additions and 22 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -69,22 +69,6 @@ Apart from the Core Web Vitals, the browser module also reports [Other Web Vital
| webvital_first_contentful_paint | Measures the time it takes for the browser to render the first DOM element on the page, whether that's a text, image or header. Please refer to [First Contentful Paint](https://web.dev/fcp/) for more information. |
| webvital_interaction_to_next_paint | An experimental metric that measures a page's responsiveness. Please refer to [Interaction to Next Paint](https://web.dev/inp/) for more information. |

### Legacy browser metrics

<Blockquote mod="note" title="">

As of [k6 version 0.44.0](https://github.com/grafana/k6/releases/tag/v0.44.0), k6 now natively supports [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals). In future releases, to align with recommended practices, we will remove the following browser metrics to focus on the web vital metrics. Please refer to [#831](https://github.com/grafana/xk6-browser/issues/831) for more information.

</Blockquote>

Apart from the usual HTTP specific metrics that k6 already tracks, the browser module tracks the following browser specific performance metrics on top:

| Metric Name | Description |
|--------------------------------|--------------------------------------------------------------------------------------------------------------|
| browser_dom_content_loaded | Emitted when the page is loaded but scripts have just started to be executed. |
| browser_first_paint | Emitted when the browser renders the first pixel on the page. |
| browser_loaded | Emitted when the page is fully loaded. |


## Built-in WebSocket metrics {#websockets}

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -92,9 +92,6 @@ default ✓ [===============================] 1 VUs 00m01.9s/10m0s 1/1 iters,

✓ header

browser_dom_content_loaded.............................: avg=63.74ms min=2.11ms med=21.66ms max=167.44ms p(90)=138.28ms p(95)=152.86ms
browser_first_paint....................................: avg=72.62ms min=41.31ms med=72.62ms max=103.94ms p(90)=97.67ms p(95)=100.8ms
browser_loaded.........................................: avg=63.16ms min=6.52ms med=15.98ms max=166.98ms p(90)=136.78ms p(95)=151.88ms
checks.................................................: 100.00% ✓ 1 ✗ 0
data_received..........................................: 5.8 kB 659 B/s
data_sent..............................................: 2.6 kB 291 B/s
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -41,9 +41,6 @@ In future releases, the `browser_*` metrics will be removed in favor of the web
</Blockquote>

```bash
browser_dom_content_loaded.............................: avg=63.74ms min=2.11ms med=21.66ms max=167.44ms p(90)=138.28ms p(95)=152.86ms
browser_first_paint....................................: avg=72.62ms min=41.31ms med=72.62ms max=103.94ms p(90)=97.67ms p(95)=100.8ms
browser_loaded.........................................: avg=63.16ms min=6.52ms med=15.98ms max=166.98ms p(90)=136.78ms p(95)=151.88ms
webvital_cumulative_layout_shift.......................: avg=0 min=0 med=0 max=0 p(90)=0 p(95)=0
webvital_cumulative_layout_shift_good..................: 1 0.113248/s
webvital_first_contentful_paint........................: avg=415.35ms min=302ms med=415.35ms max=528.7ms p(90)=506.03ms p(95)=517.36ms
Expand Down

0 comments on commit 29767f6

Please sign in to comment.