User Journey detailed execution report

You can access the data of the detailed report of a given execution of a scenario:

  • From the User Journey monitoring data overview, by clicking on a specific dot of one of an non-aggregated graph
  • From the list of the execution reports related to the User Journey, by clicking on the “view” button
  • From the list of your scenarios, you can access directly the last execution of each one of them.

On the execution report, the "Actions" drop-down menu allows you to execute, enable/disable, modify, or duplicate the current User Journey monitoring, but also to manage the alerts for cumulative results of an execution and related events.

The execution report then consists of 4 parts.

It starts by a reminder of this execution configuration: the URL defining the starting point of the scenario, and the device and location used during this specific run.

The execution report then features the step-by-step breakdown of the content (number of requests, weight) and web performance metrics (First Byte, Start Render, Fully Loaded, and Speed ​​Index). For every metric, you will be able to get both the value related to a step and the cumulative value, for all the steps.

Speaking of steps, the following area is a reminder of all executed steps and actions during the User Journey monitoring. Actions, successful and failed checks are properly highlighted to ensure that you can effectively analyze any problems that may happen during execution. A “Details” button will give you access to the detailed report of a step execution.

User journey step list

Finally, a downloadable step-by-step filmstrip is displayed, giving you a visual breakdown of the loading of your tested steps frame after frame at regular intervals. Each image in this filmstrip is assigned a specific rate that qualifies the completion of the step rendering relatively to its final visual state. The "100%" rate indicates that the "Visually Complete" state has been reached.

Note that the Speed ​​Index calculation is based on these rates in order to account for the progressiveness of the page rendering.

Back to Table of Contents