> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/time-lost.md).

# 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.

**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

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FCIp1Psm6ePfqXkXaeopG%2F2026.8_AppEx_TimeLost_59_Rk2Tn8.png?alt=media&#x26;token=a00bed5f-2730-4e0a-931b-6668343d2dbe" alt=""><figcaption></figcaption></figure>

### 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](/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/page-loads.md), [Reliability](/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/reliability.md), and [Transactions](/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/transactions.md) for more information on each metric.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexthink.com/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/time-lost.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.