ποΈ Functional recommendation index
| Module |List of features| Recommendation index |
ποΈ Public Operation
Switch access mode
ποΈ Application Overview
Click Web>Overview in the left navigation bar to enter the application list page.
ποΈ Page Analysis
Page The analysis provides the performance analysis data of all pages in the application, and can perform performance evaluation, trend chart and quantile chart analysis, region analysis, summary waterfall chart analysis and page exception tracking on the performance of each page.
ποΈ Blank Screen
Blank screen trend
ποΈ Operation Analysis
Operation user experience analysis is mainly used to monitor and analyze the response time and availability of the user's click operation on the page. Optimizing the user experience of operation is conducive to improving the conversion rate of key steps of users.
ποΈ Region Analysis
The regional operator analysis module can see the trend of PV, UV, user experience score, slow page ratio, FCP, LCP, DCL, full loading, operation time, operation availability, number of operations, HTML loading, DNS, connection establishment, SSL , first package, remaining package, JS error rate and other indicators corresponding to the application under different regional operators. Customers can timely adjust and optimize the performance in different regions based on this data, so that users can get the best application user experience in different regions and different network environments.
ποΈ Request Analysis
Request analysis is mainly used to analyze the performance and errors of network requests in the application. It can analyze two types of requests: Ajax requests and static resource requests. You can analyze the request response time, proportion of slow requests, error rate, number of users affected by slow requests, and number of users affected by error requests for each application/domain name/path/parameter.
ποΈ Browser Analysis
The browser module can help to analyze the UV ratio, PV ratio, full loading, slow page ratio and JS error rate of different browsers accessing the application, help to determine which browsers have more problems with the program, formulate test priorities and focus on optimization .
ποΈ JS Error Analysis
JS error analysis is mainly used to analyze the JS errors that occur when a page is accessed, and to count and analyze the causes of JS errors.
ποΈ User Tracing
User tracing can filter abnormal data based on all users, VIP user group and all VIP users, and then trace the access records of slow full load, slow FCP, slow LCP, slow DCL, operation, failed operation, request and JS error of users through public network IP, user ID, session ID, device ID and JS TraceID. It can also restore the scene of the situation and analyze the root causes of poor user experience.
ποΈ Module Analysis
Module user experience means that the tone listening cloud supports the custom selection of domain names/URLs from any one or more embedded applications to form a module, so as to monitor the user experience of the module. The module analysis starts from the module dimension, and intuitively displays the alarm status, module name, user experience score, PV, UV, slow page percentage, full load, FCP, LCP, DCL, JS error rate, operation time and operation availability of the module in real time.
ποΈ Page Analysis Tool
The page analysis tool is implemented by Google's open source automation tool Lighthouse to improve the quality of web applications. When Lighthouse is given a URL to analyze, it runs a series of tests against the page and then generates a report on the performance of the page. Users can refer to the failed test to see what can be done to improve the application.
ποΈ Application Settings
Set the rejection threshold of abnormal data. The unit is second, and the default is 120 seconds. When it is not enabled, the default filtering rule will take effect. When the rule is DCL or full load is greater than 10 times of FCP and any of the four indicators of FCP, LCP, DCL and full load is greater than 60 seconds, the page performance data will be filtered. When it is enabled, the filter rule is FCP, LCP, DCL, and Full Load. If any of the four indicators is greater than the set value, the page performance data will be filtered, and the filter rule will be disabled by default. The page performance data conforming to the filtering rules will be eliminated and will not participate in the calculation of page performance indicators, but the JS errors occurring on the page will still be retained and participate in the calculation of JS error rate.
ποΈ Source Map
Source Map is an information file that stores the mapping between the source code and the corresponding position of the compiled code, which is convenient for developers to locate the above code errors. In effect, it is a JSON key-value pair that stores location information using VLQ encoding and specific rules. In short, it can be understood that Source Map builds a bridge between the code before processing and the code after processing.
ποΈ Probe Configuration
The system can dynamically send some advanced configurations to the probe. Refer to the following for detailed configuration items and descriptions.
ποΈ Cross-origin configuration
Background introduction
ποΈ JSON Path
Expression Description