For the complete documentation index, see llms.txt. This page is also available as Markdown.

Time lost

The Time lost tab quantifies productivity lost to poor application experience, combining delays from page loads, transactions, and errors into a single metric. It considers delays due to:

  • Page loads – time taken for web pages to be ready for user interaction.

  • Transactions – time to complete a tracked user action.

  • Reliability – implied lost productivity from failed interactions.

This tab is available only when AHEAD is enabled for the application.

Time lost analytics use cases:

  • For IT teams: pinpoint where users lose the most time to prioritize performance fixes.

  • For business and application owners: correlate delays and errors with lost productivity across the workforce.

Interpreting the Time lost tab

Time lost

The Time lost widget shows the total time lost for the selected timeframe, broken down into:

  • Page loads – time lost to slow page loads.

  • Errors – time lost to reliability issues.

  • Transactions – time lost to slow or failed transactions.

The trend chart shows how time lost evolves over the period, split by category.

Page loads, Reliability, and Transactions

Below the chart, three widgets summarize the metrics feeding into Time lost:

  • Page loads: the percentage of frustrating page loads and the average page load time.

  • Reliability: the error ratio and the number of errors.

  • Transactions: the percentage of frustrating transactions and the average transaction duration.

Refer to Page loads, Reliability, and Transactions for more information on each metric.

Last updated

Was this helpful?