PDFs

On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
2 rates

Many of the metrics collected by Browser Synthetic are identical to those collected by Browser RUM. Additional synthetic-only metrics are defined in Browser Synthetic Metrics Defined.

Key Browser RUM metrics are displayed on the Geo, Sessions, and Pages dashboards. They can also be seen in the Metric Browser, just like RUM metrics, giving you the ability to view these metrics in the context of Ajax requests, iframes, applications, base pages, browsers, devices, and geographic locations.

There are also metrics for specific tests and, under the Synthetic Jobs heading, for Synthetic job health overall.  

Browser Synthetic Metrics Defined

Name
Definition
Availability

The ratio of OKAY sessions (successful) to all sessions, expressed per-million: 0 (for all failed) to 1,000,000 (for all succeeded). The ratio is calculated using the following: (# of successful sessions/# of total sessions) * 1,000,000.

Availability is represented in per-million instead of as a percentage because Controller metrics are given as integers, making expressing the availability as a percentage less precise. For example, although the availability percentage in actuality might be 99.99%, it would only be able to be expressed as an integer such as 100% or 99%.

To convert per-million to a percentage, just divide by Availability (ppm) by 10,000. For example, if Availability (ppm) is 999,800, then Availability (%) is 99.98%. Most Controller UI components display metrics as percentages, but the Metric Browser, which shows "raw data", shows the value per-million.

Billable TimeThe seconds that were billed against your Browser Synthetic license.
Broken SessionsThe number of sessions that completed with the session status BROKEN, indicating that the job has an error. You can find the error in the script console output.
Data Downloaded Before Fully LoadedThe bytes of data downloaded by the browser between the navigation start of a page and the navigation start of the next page or the end of the session. In particular, includes any resources loaded after the page load event.
Data Downloaded Before OnloadThe bytes of data downloaded by the browser between the navigation start for a page and the load event for that page.
DOM Elements per PageviewThe number of DOM elements present on a page at the time of the page's load event. Includes sub-documents in frames.
Failed SessionsThe number of sessions that completed with the session status FAILED, indicating the synthetic test has detected a problem with your site. See Session Status for more information.
Fully Loaded TimeThe time from the start of the initial navigation until 2 seconds of no network activity has passed after Document Complete. This will usually include any activity that is triggered by JavaScript after the main page loads. The Fully Loaded Time is given in milliseconds and percentiles.
Job ExecutionsTotal number of sessions (per browser, per location) for a given job.
Number of Resources Loaded Before Fully LoadedSee Data Downloaded Before Fully Loaded above.
Number of Resources Loaded Before OnloadSee Data Downloaded Before Onload above.
Ok SessionsThe number of sessions that completed with the session status OK, indicating the synthetic job ran successfully and returned data.
Pages per SessionThe number of pages per session.
Session DurationFor scripted jobs: the time needed to execute the script from the first line to the last line.
For URL jobs: the time from when the browser initiated the first HTTP request until the last resource was loaded.
Sessions with Resource Errors The number of sessions that had missing or inaccessible resources.
Session Visual Time (SVT)

This metric captures the time the browser spent loading pages. Relative to Session Duration, this excludes the script process time and the time your script was interacting with content on a given page.

Specifically, the Session Visual Time for a session is the sum of the Visually Complete Times for each page.

Speed IndexThis metric captures whether a page renders incrementally or all at once. For example, if two pages both take five seconds to finish rendering, but one is mostly rendered after a second, while the other is blank until the last moment. Then the first page will have a Speed Index close to 1000, while the second will have a Speed Index close to 5000 (the Visually Complete time in milliseconds). More information on how it is calculated is available in the WebPagetest documentation.
Start Render TimeThe time from the start of the initial navigation until the first non-white content is rendered in the browser display in milliseconds.
Visually CompleteThe time when an end-user would determine that the page is visually complete in the viewport. This time is calculated by using the last visual change to the page and is in milliseconds. The page represents the viewable content (the viewport) in a browser window. The default size for a browser window is 1024 x 768.
Warning SessionsThe number of sessions that completed with the session status WARNING, indicating the test ran successfully, but there were inaccessible resources. 



 

 



  • No labels