# Understanding the URI Performance Information

The performance information for each URI and each of the three distribution diagrams is the same. The details of each element is as follows:

<table data-header-hidden><thead><tr><th width="228"></th><th></th></tr></thead><tbody><tr><td>Element</td><td>Meaning</td></tr><tr><td>Transaction count</td><td>Total number of transactions that have been processed for the section.</td></tr><tr><td>First transaction</td><td>The time spent in the very first transaction for this URI or the very first transaction in the case of all URIs (*). This first transaction is always isolated as startup time for some underlying services may cause delays that are not consistent beyond the first transaction and can therefore result in misleading data on small stress testing runs.</td></tr><tr><td>Lowest recorded</td><td>The lowest transaction time recorded for the selected URI</td></tr><tr><td>Max recorded after first</td><td>The highest transaction time recorded for the selected URI, excluding the first transaction. Please note that for the combined URIs (*) this is only excluding the very first transaction for any given URI. Hence it can be the second largest first transaction for a secondary URI.</td></tr><tr><td>Average</td><td>This is the average response time for the selected URI, including the first transaction.</td></tr><tr><td>Average without first</td><td>This is the average response time, excluding the first transaction. For small stress test runs, this is a more accurate reflection of the real end user experience.</td></tr></tbody></table>

The distribution diagrams show transactions below 100ms, below 1s and up to 20s. Transactions taking 20 seconds or more will all be included in the `>=19` seconds group. These distribution diagrams are especially useful when combined with the transaction counts in the rule sets.

<figure><img src="/files/RRdkmp8ZXfDg2uDAWLvw" alt=""><figcaption><p>Performance of <code class="expression">space.vars.X_Agent_Name_Single</code> alone</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tomorrowx.com/cap/product-reference/performance-data/understanding-the-uri-performance-information.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.