# Page loads

Slow performance is a common employee complaint that can stem from the device, network, infrastructure, or application. With software as a service (SaaS) apps, the issue might also lie outside the company’s network.

The **Page Loads** dashboard uses the **Frustrating** page loads metric to surface the most problematic web apps. **Page Loads** supports troubleshooting through breakdowns, bar charts, and a device-level pop-up.

Refer to [Understanding the Page loads metric](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/page-loads/understanding-the-page-loads-metric.md) documentation for more details on soft and hard navigation estimations.

## **Leveraging Page loads Insights**

The **Insights** panel on the right uses an algorithm to highlight the most frustrating pages by quantifying impact, identifying possible root causes, and evaluating backend, network, and client times. When you select a different time frame, you may see different insights.

For deeper analysis:

* Open the **Insights** right-side panel suggests relevant **Investigations** drill-downs.
* Alternatively, use the **Investigate more** right-side panel, which offers predefined drill-down options. These links direct you to investigation results that are relevant to the current dashboard context.

Nexthink provides insights for [Key pages and collected URLs](#key-pages-and-urls) defined in the web application configuration.

{% hint style="warning" %}
If the system cannot find any insights, it displays a *No insights found!* message in the **Insights** panel.
{% endhint %}

<figure><img src="/files/fnOzYd4Lq2WBHeUrKL8U" alt=""><figcaption></figcaption></figure>

***

## Interpreting the Page loads dashboard

The **Page loads** dashboard contains the following widgets grouped into the sections:

* [#performance](#performance "mention")
* [#top-breakdowns](#top-breakdowns "mention")
* [#other-breakdowns](#other-breakdowns "mention")

{% hint style="info" %}
Refer to [Understanding the Page loads metric](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/page-loads/understanding-the-page-loads-metric.md) documentation for more details on soft and hard navigation estimations.
{% endhint %}

<figure><img src="/files/Ke3bLU57IdVNKfYJmUkF" alt=""><figcaption></figcaption></figure>

### Performance

The **Performance** section presents an overview of the application in terms of page load experience and page load time.

<details>

<summary>Page load experience</summary>

The **Page load experience** widget shows a gauge chart with a breakdown for **good**, **average** and **frustrating** page loads.

These border values correspond to the [configured thresholds](/platform/user-guide/applications/configuring-applications/configuring-web-applications/thresholds.md) for the web application.

</details>

<details>

<summary>Page load time &#x26; Employees</summary>

Use this section to identify the changes in terms of performance over time

* The **Average page load time** widget shows area charts for **Backend**, **Device and App network**, and **Client** categories.
* The **Employees** chart represents the number of employees who performed at least one page-load action, regardless of whether the application tab was in focus or visible to the employee. This timeline is mapped with the **Average Page Load Time** chart above for easy visual correlation.

</details>

### Top breakdowns <a href="#top-breakdowns" id="top-breakdowns"></a>

The **Top breakdowns** section presents key pages, URLs, and devices with the highest number of frustrating page loads.

#### Key pages & URLs <a href="#key-pages-and-urls" id="key-pages-and-urls"></a>

Web applications contain various pages and modules with different performance characteristics. Explore the two tabs in this section to display data by:

* Configured **Key pages** in Nexthink for the web application that cause the most frustration.
* **URLs** that cause the most frustration. Use this list of URLs as a reference when configuring key pages for the web application.

Quickly find any key page or URL of interest using the widget search bar.

{% hint style="warning" %}
When [URL collection](/platform/user-guide/applications/configuring-applications/configuring-web-applications.md#configuringwebapplications-collectingurls) for an application is disabled, the **Key pages & URLs** breakdown only displays key pages configured in Nexthink.
{% endhint %}

<figure><img src="/files/tQGVREpgHh2S18dFYuwt" alt=""><figcaption></figcaption></figure>

#### Devices <a href="#devices" id="devices"></a>

The **Devices** table displays the devices with the most significant number of frustrating page loads.

Hover over the device name to activate a pop-up with detailed information to answer to the following questions:

* *Is this a new issue, or has the page always been slow?*
* *Is it a device-specific issue, or does it affect other devices as well?*

The pop-up displays the **Page load times** of the selected device compared with those of other devices across the organization, including **Client**, **Network**, and **Backend** times. You can:

* **Filter** page for the selected device.
* Click the link icon to open the **Device View** page for more troubleshooting options for the device.

<figure><img src="/files/lz6gCyFe9OYkyqiYwdSK" alt=""><figcaption></figcaption></figure>

### Other breakdowns <a href="#other-breakdowns" id="other-breakdowns"></a>

The **Other breakdowns** section includes **Location**, **Organization** and **Technical** widgets.

#### Location <a href="#location" id="location"></a>

Identify the locations where employees experience **Frustrating page loads** using the interactive map. Hover over the locations to reveal more information.

The **Location** widget table shows key metrics based on the **County**, **State** and **Location type** of the devices.

{% hint style="info" %}
Location data is based on the geolocation feature, which must be enabled on the [Product configuration](/platform/user-guide/administration/system-configuration/product-configuration.md) page.
{% endhint %}

<figure><img src="/files/hmFZOrMQ2NZoyHMinth8" alt=""><figcaption></figcaption></figure>

#### Organization <a href="#organization" id="organization"></a>

The **Organization** table displays metrics by your organization's classification. Select the organization level from the dropdown list.

Refer to the [Product configuration](https://docs.nexthink.com/platform/latest/product-configuration) documentation for more information on how to define entities and custom classification for your organization.

#### Technical <a href="#technical" id="technical"></a>

The **Technical** table shows key metrics broken down by technical device properties, such as **Browser and version** or **Operating system**.

<figure><img src="/files/leWjA0MtZAqAkQv48VW0" alt=""><figcaption></figcaption></figure>

***

RELATED TOPICS

* [Understanding the Page loads metric](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/page-loads/understanding-the-page-loads-metric.md)
* [Troubleshooting slow page loads](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/page-loads/troubleshooting-slow-page-loads.md)


---

# 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.nexthink.com/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/page-loads.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.