Configure the results

UPDATE 21 AUG 2025

Before obtaining the final ecoscore of a digital service, it is necessary to configure the results just obtained.

Configuring the results involves 3 steps in SaaS :

• Define critical steps

• Configure PAUSEAFTERLOAD variable time

• Define functional domains (optional)

Define critical steps

Critical steps are the entry points for the application's sub-courses, or “must-haves”. Consequently, their number of visits is theoretically higher than that of other steps. This makes it possible to assess whether or not the quality of the journey is strongly impacted by bad critical steps. These steps have a higher weighting in the ecoscore calculation (0.7 vs. 0.3 for non-critical steps).
They may include loading the home page, a login action or loading the results of a product search. By convention :

• If a loading step is identified as critical, so is the pause step that necessarily follows it.

• A functional journey comprises between 3 and 5 critical steps.

To fill them in on SAAS, go to Analysis, then to the Steps tab in the menu. All our steps are shown here. Click on the Modify step pencil (), then change the Criticality menu to Yes. To save changes, press Modify. Repeat for all steps considered critical.

Open

Our CHRGT_home step here is Critical, and will therefore have more weight in the ecoscore calculation.

Once these changes have been made, you can recalculate the ecoscore. To do this, go to the Versions management tab in the menu, then click on the Recalculate metrics and scores arrow (). Reload the page for the changes to take effect.

Open

The arrow on the right allows you to recalculate metrics and scores.

Configure PAUSEAFTERLOAD variable time

This step is mandatory when the GDSL script used for measurement includes the variable PAUSEAFTERLOAD with a defined duration. It is normally located at the end of each loading, action and scroll step. You can find more information about GDSL best practices here. To get the right performance score, we need to remove these artificially added seconds.
To do this, go to Analysis, then to the Steps tab in the menu. All our steps are shown here. Click on the “Modify step” pencil (), then change the post-loading time from 0 to 1 (or other if a time other than 1sec has been chosen). To save changes, press Modify. Repeat this for all steps which include a PAUSEAFTERLOAD before the end of the measurement.

Open

Once these changes have been made, you can recalculate the ecoscore. To do this, go to the Versions management tab in the menu, then click on the Recalculate metrics and scores arrow (). Reload the page for the changes to take effect.

Define functional domains

Functional domains

This step, although not mandatory to obtain a final ecoscore, provides an intermediate vision between the metrics of the entire journey and the unit metrics of the individual steps. It consists in grouping steps into sub-journeys in order to analyze their impact at the wanted level of granularity.

Division example

Let's take the example of a complete journey consisting of “Buying a product on an e-commerce application”. This journey can be divided into several functional sub-journeys:

If different technologies are used, or if different teams are working on different parts of the app (one for the connection, one for the catalog, one for the payment tunnel), this split allows to :

• Check that the same best practices are being implemented everywhere.

• Identify if any part of the journey requires special optimization.

On Saas

Open

To define functional areas, go to Saas, in the analysis, to the Domains menu. You can then view the functionalities created in your analysis, delete them and add new ones by clicking on the Add button. Then, simply add the name of the functional domain you want, and you'll be able to add the steps you want to it. You can also add steps to a functionality from the Steps tab in the menu.

Open

Domains tab

Once functional domains are configured, go to Vision by domain tab to compare them through their impact.

This page has 2 tabs :

• Comparison by metrics and features

• Comparison by steps, metrics and features

The first allows to see which functional domains have the greatest impact according to each metric, while the second adds a step-by-step view and a different visualization.