Help Center> > User Guide > Browser >Browser Summary

Browser Summary


The Application Performance Management (APM) browser function provides intuitive performance data of the frontend from multiple dimensions, including user experience, throughput, and error, helping you quickly locate performance bottlenecks and optimize performance.

Previously, people paid more attention to server performance than frontend performance. In the Internet era when user experience is of crucial importance, user experience at the frontend still cannot be monitored even though backend services are running stably. If exceptions occur at the backend, you can quickly locate and rectify faults based on logs. However, when user experience at the frontend is not satisfactory, you may not be aware of that in uncertain application scenarios. You can only optimize the frontend based on surveys and user feedback. Such methods are inefficient or even ineffective.

To solve the problem, Huawei provides the APM browser function. This function enables you to establish relationships with all users around the world and monitor their experience in real time. The Browser Summary page displays user experience in real time, helping you quickly optimize performance and achieve business success.


Monitoring Metrics

User Experience

APM uses the Application Performance Index (Apdex) to measure user experience. APM classifies requests into satisfied, tolerating, and frustrated requests based on the response time, and quantifies user experience using certain formulas, helping you obtain basic application information.


Throughput refers to the total number of network requests in a specified period.

TP99 Latency

TP99 latency refers to the minimum time meeting requirements of 99% requests.

Example: Assume that there are 100 requests, and the time consumed by the requests is 1s, 2s, 3s, 4s...98s, 99s, and 100s. To meet the requirements of 99% requests, at least 99s is required. Therefore, TP99 latency is 99s.

Calculation: Sort all requests by the consumed time in ascending order. TP99 latency = Time consumed by the Nth request. N is the rounding value of 99% x Total number of requests.


Errors refer to the number of network request failures.

Page Loading Time

When you click a hyperlink or access a URL through the address bar, the page loading process starts, and the entire process ends until the page is rendered in your browser. APM records each time point of the page loading timeline, calculates the time consumed in each phase, and displays the result in a cumulative chart, helping you quickly locate frontend performance bottlenecks. The entire loading process is divided into four phases based on services, as shown in the following figure.

The following table lists the methods of calculating the time consumed in each phase.

Reported Field


Calculation Method



Time consumed by the network

(requestStart - navigationStart) + (responserEnd - responseStart)



Time consumed by DOM processing

domContentLoadedEventEnd - responseEnd



Time consumed by page rendering


Time consumed by first page rendering


Time consumed by backend services

responseEnd - requestStart


You can optimize the performance based on metrics in different phases.

Related Operations

You can click on the left of the Browser Summary page and perform the following operations.




Browser Summary page


Click on the left of the Browser Summary page to add, delete, or reset a widget.






Click on the left of the Browser Summary page to delete or zoom in a widget.

Zoom in