Detailed report of a step execution

You can access the detailed report of a step execution from the data of a specific report, by clicking on the “Details” button of a step.

On the execution report overview, the "Actions" dropdown menu allows you to edit the step or manage the alert thresholds relative to the given step. You can also execute the current User Journey or modify its implementation, but also manage the alerts relative to the whole journey or this specific step, and the related events.

A navigation bar gives you instant access to the overall user journey report, the previous and next step, if any.

The execution report then consists of 5 parts.

It starts by the step metrics summary composed of the resources breakdown (number of requests, weight) and web performance metrics (First Byte, Load Event Start, Fully Loaded, Start Render, Visually Complete et Speed Index).

You will then find the video recording of the main action of the step, giving you the ability to replay the loading while controlling the video speed.

Under the video, a downloadable filmstrip is displayed, giving you a visual breakdown of the loading of your tested step 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.

The report then feature a summary of the browser errors. This area indicates the number of errors or warnings issued by the web browser while recording the tested step. Actually, these information usually appear in the browser console (for developers). We are showing them here after having filtered them.

User journey step list

The detailed report then displays the sequence of actions composing the step (interactions and checks), before displaying the waterfall (network activity captured during the main action).

If the main action of the step is not successfully executed, additional information, useful for understanding the error, are available: the URL before and after the action, and a screenshot of the page where the error occurred.

User journey step list in error

Back to Table of Contents