Skip to main content
Skip table of contents

Troubleshoot

The Troubleshoot page uses the frustrating page loads metric to help you identify the web applications that are causing the most frustration in your organization. The dashboard supports troubleshooting slow web applications through relevant breakdowns, bar charts and a device pop-up.

Page load experience

Page load experience widget shows a gauge chart with a breakdown for good, average and frustrating page loads. Refer to the Speed documentation for more information about Page load times and Navigation timing API.

  • Click on the action menu of the widget to drill down to the Number of page loads by experience level. The system redirects you to the Investigations page to show the results of the NQL query.

Page load experience
  • Hover over the Good, Average and Frustrating labels to reveal the action menu. Click on it and select Copy to copy the value to your clipboard or drill down to Devices.

Page load action menu

Page load time and Employees

The Average page load time widget shows area charts for Backend, Device and App network, and Client categories. Click on the category in the legend to filter the line charts.

The number of employees represents those who performed at least one page-load action. It is mapped onto its own timeline for users to easily draw a visual correlation with the Average page load time widget above. Refer to the Speed documentation for more information about these categories and Navigation timing API.

  • Click on the action menu of the widget and choose from:

    • Page load performance over time

    • Employees over time

The system redirects you to the Investigations page to show the results of the NQL query.

Page load timeline action menu

Waterfall metrics to diagnose slow page loads

To troubleshoot web applications in more detail, you can use waterfall analysis metrics. These metrics help you pinpoint the exact sources of performance bottlenecks, identify error-prone elements, and highlight resource-intensive components within web applications. Waterfall metrics are available under the Resource analysis tab of the Web Applications Troubleshooting library dashboard.

2024-05-27_13-32-42.png

Refer to the Web Application Advanced Troubleshooting documentation for more information.

List of new waterfall metrics for web resources

These metrics are collected by the Nexthink Application Experience browser extension, which uses Performance Resource Timing API.

Name

NQL Syntax

Description

Longest resource during a navigation (name, type, size, and duration)

•longest_resource_url

•longest_resource_type

•longest_resource_load_time

•longest_resource_size

Longest resource refers to the resource that experienced the lengthiest loading time among all the necessary elements for rendering a web page. If a specific resource takes a significantly longer time to load compared to others, it may be affecting the overall loading speed of your web application. 

Largest resource during a navigation (name, type, size, and duration)

•largest_resource_url

•largest_resource_type

•largest_resource_load_time

•largest_resource_size

Largest resource refers to the resource that had the biggest file size to be fully loaded while loading a web page. When a user's browser needs to download and render large resources, it can lead to increased latency and slower page load times. Analysing large resources can help identify files that may be optimized or compressed to reduce their size.

Number of domains contacted

domains_contacted

Number of domains contacted indicates the number of unique domain names from which various resources (such as images, scripts, stylesheets, fonts, etc.) are being fetched.

These domains can include the application's own domain, as well as domains for third-party resources like analytics scripts, ads, content delivery networks (CDNs), and more.

Each unique domain contacted represents a separate server from which the browser needs to fetch resources, and this can impact overall page load times.

Number of resources

number_of_resources

Number of resources indicates the total number of resources (such as images, scripts, stylesheets, or other files) loaded during a navigation event. The more resources a web page has, the longer it may take to load and render in the browser. By analyzing the number of resources, you can identify opportunities to optimize the performance of your web application. For example, you might consider minimizing or combining CSS and JavaScript files, compressing images, or using caching techniques to reduce the number of requests made to the server.

Number of large resources

number_of_large_resources

Number of large resources indicates the number of resources (such as images, scripts, stylesheets, or other files) that are larger than 100KB, during a navigation event. When a user's browser needs to download and render large resources, it can lead to increased latency and slower page load times. Analysing large resources can help identify files that may be optimized or compressed to reduce their size.

Number of resource errors

number_of_resource_errors

Number of resource errors indicates the number of resources (such as images, scripts, stylesheets, or other files) that failed to load or encountered errors during a navigation event. Resource errors can indicate that certain files or assets are missing from the web application. This may result in broken links, missing images, or non-functional scripts.

Top breakdowns

Key pages and URLs

The first table shows key pages and URLs that resulted in the largest number of frustrating page loads. Use this list of URLs as a reference when configuring key pages for an application.

Click on the columns to sort the table by Frustrating page loads, % Frustrating page loads, Page load time, Page loads or Employees.

Click on the action menu of the widget to View page loads by URL. The system redirects you to the Investigations page to show the results of the NQL query.

When URL collection for an application is disabled, this breakdown presents only key pages.

Action menu for the Key pages and URLs widget

Hover over a value in the table to reveal the action menu. Click on it to view the drill-down options for relevant objects and fields. The system redirects you to the Investigations page to show the results of the NQL query.

APPEX-1708334447.png

Devices

The Devices table and the device pop-up are designed to answer 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?

Hover over the device name to activate the pop-up.

APPEX-1708097157.png

The pop-up shows a Page load time line chart of the selected device over time. The line chart includes the average page load times of the same web application on other devices within your company.

The pop-up gives you a side-by-side view of Page load time, Network time and Backend metrics for the selected Device and Company devices.

  • Click Filter at the top of the pop-up to filter the page for the selected device.

  • Click the link icon to open the Device View page for more troubleshooting options for the device.

Other breakdowns

Location

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

Location map

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

Location data is based on the geolocation feature, which must be enabled on the Product configuration page.

Organization

The Organization table shows data according to entities. Refer to the Product configuration documentation for more information on how to define entities for your organization.


RELATED TASKS

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.