Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit c190d32

Browse files
committed
Correct TTI and lighthouse score definitions
1 parent 648ecb5 commit c190d32

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

synthetics/browser-test/set-up-browser-test.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -378,11 +378,11 @@ There are many reasons why you might want to configure advanced settings for you
378378

379379
Collect interactive metrics
380380
---------------------------------
381-
Interactive metrics are on by default. You can turn off interactive metrics in advanced settings to speed up test durations. If you turn off interactive metrics then some metrics might be missing from your test. These are the type of interactive metrics Splunk Synthetic Monitoring collects:
381+
Interactive metrics are collected by default for each page in the test flow, but this can result in longer run durations depending on how long it takes for the page to become fully interactive. You can turn off interactive metrics in advanced settings to speed up run durations and see results faster. If you turn off interactive metrics then the following metrics might be missing from your test:
382382

383383
* First CPU idle: Time until the page is minimally interactive and responds to user input.
384-
* Time to interactive: Time from the start of the first request until receiving the first byte of the first non-redirect request. ``3xx`` redirects increases this time. This metric is available for HTTP Uptime tests, but not Port Uptime tests.
385-
* Lighthouse score: A weighted aggregation of several Browser test metric values calculated using v6 of the Lighthouse scoring algorithm. See :new-page:`https://web.dev/vitals/` in the Google developer documentation to learn more about Lighthouse scoring.
384+
* Time to interactive: This measures the time until the page responds to user input quickly. It is used to identify when the page is actually usable, not just when the page load looks complete.
385+
* Lighthouse score: A weighted aggregation of several Browser test metric values calculated using v10 of the Lighthouse desktop scoring algorithm. See :new-page:`https://developer.chrome.com/docs/lighthouse/performance/performance-scoring#lighthouse_10` in the Google developer documentation to learn more about Lighthouse scoring.
386386

387387

388388
.. _auto-retry:

0 commit comments

Comments
 (0)