Journey performance

Track web journey performance over time

Naosaki executes the same Robot regularly in a real browser and connects LCP, CLS, INP, duration and requests to the pages and steps it visits.

Web Vitals by URL

Three complementary views

Each measurement remains connected to the URL, step and journey execution that produced it.

LCP

Largest Contentful Paint

Measures the rendering of the largest visible content element for each visited URL.

INP

Interaction to Next Paint

Measures the responsiveness observed during interactions on journey pages.

CLS

Cumulative Layout Shift

Measures unexpected layout shifts during execution.

Execution context

Do not reduce a journey to one score

Status answers “did the journey complete?”. Performance measurements help the team examine how its execution evolves.

Analysis duration

Start, end and total timing place the performance of a complete execution in context.

Per-step measurements

Enriched steps preserve information including timing, request count and transferred size.

Request volume

Request count and size complement Web Vitals when reviewing journey behaviour.

Daily Stats

Stats aggregate duration, outcomes, steps and Web Vitals for the same Robot each day.

Review method

Compare a consistent context

A trend is easier to read when the Robot, its steps and the pages it visits remain identifiable from one execution to the next.

  1. 01

    Define a stable journey

    Document the expected outcome and important steps so that a comparable scenario can be repeated.

  2. 02

    Review pages and steps

    Examine Web Vitals by URL, then return to the duration and requests for the corresponding steps.

  3. 03

    Observe the evolution

    Use Analyses and daily Stats to compare executions of the same Robot over time.

Frequently asked questions

Does Naosaki measure real users?

No. Naosaki executes a defined synthetic scenario in a real browser. The measurements describe that Robot execution, not every visitor to the site.

Which Web Vitals are available?

Analyses preserve LCP, CLS and INP for each visited URL, with a value and rating. FID and TTFB are not part of the documented model.

How long is performance history retained?

Retention is configured per Compagnie. Naosaki therefore does not present one public duration as applying to every configuration.

Do Web Vitals indicate whether the journey succeeded?

No. Analysis status records the execution outcome. Web Vitals, duration and requests describe its performance and context.

Which steps do you want to track over time?

Tell us about the journey and its important pages. We will assess the checks, measurements and evidence to plan with you.