| UV (Unique Visitors) | Total number of users who visited the mini program pages, with the same user visiting multiple times counted only once |
| Open Count | Total number of times the mini program was opened. The process from a user opening the mini program to actively closing it or timing out is counted as one time. |
| PV (Page Views) | Total number of page visits to the mini program. Navigation between multiple pages and repeated visits to the same page are counted as multiple visits. |
| Bounce Rate | Number of PVs where the current page is exited from the program / Total PV of the current page * 100% |
| JS Error Rate | (PV of pages with JS errors / Total PV) * 100% |
| onReady | Lifecycle function - Listens for the first rendering completion of the page |
| First Response | Time from page opening to the completion of the first network request |
| Loading Time | The time for page request rendering to complete without further user operations or scheduled tasks. Calculated as the time period from the completion of onLoad to onReady lifecycle execution, including the longest rendering callback time of all setData and requests sent followed by setData. Calculation method: Maximum value of (the latest setData rendering callback time before onReady callback ends) and (the latest setData rendering callback time triggered in request callbacks sent before onReady callback ends) - onLoad trigger time |
| Request Time | Time from request initiation to request response completion; Calculation rule: Return time point - Initiation time point |
| Server Time | Time consumed by the application server to process the request, i.e., application response time, equal to the time from when the request reaches the application server until the application code completes execution and outputs response information. |
| Request Error Rate | (Number of network request errors / Number of network requests) * 100% |
| Data Transfer Volume | Average data transfer volume per network request (upload + download bytes) |
| Callback Time | Callback time refers to when data is transmitted from the server to the client, and the local code processes this data accordingly. It can be understood as local execution time |
| Network Time | Time from when the network request is sent until the server receives the request |
| API Call Count | Number of times the API is called |
| API Call Success Rate | (Number of successful API calls / Total number of API calls) * 100% |
| API Affected User Count | Number of users who experienced at least one failure when calling this API during the process from opening the mini program to actively closing it or timing out. |
| API Failed User Count | Number of users who were unsuccessful in calling this API during the process from opening the mini program to actively closing it or timing out. This includes users who tried once or multiple times but failed, and had not succeeded by the time they left. |
| Operation Count | Number of times the specified operation was requested. Calculation rule: When an operation is requested once, it is recorded as 1 time |
| Operation Time | Time for all requests in the specified operation to complete. Calculation rule: For operations with Ajax requests, it's the end time of the last Ajax in the operation - the start time of the operation click. |
| Operation Availability | Proportion of successful operations to total operations. Calculation formula: Operation availability = (Number of successful operations / Total number of operations) * 100% |
| Operation Request Time | Pure request time in the specified operation, excluding idle waiting time in the operation time. |
| Average Server Time | Average server time for multiple requests within a page or operation |
| Average Request Time | Average time for multiple requests within a page or operation |
| Failed Operation | If any request within an operation encounters an error, the operation is counted as failed. (Request errors can be filtered by network error status codes in the application settings). |
| Experience Score | A score measuring the overall experience of the mini program, based on a comprehensive evaluation of 7 items: JS error rate, request error rate, request time, loading time, onready, stutter rate, and operation availability. Each item has a maximum score of 100 points. Score = JS error rate score * weight + onready score * weight + loading time score * weight + request time score * weight + request error rate score * weight + stutter rate * weight + operation availability * weight. The metric values for time-based indicators are percentile values that can be customized. |
| setData Time | The time difference from calling setData to the completion of rendering callback (** The data in setData should not exceed 256KB after JSON.stringify**) |
| setData Frequency | Number of setData triggers per second. (WeChat official recommendation: The number of setData calls per second should not exceed 20 times) |
| Stutter Rate | PV of pages exceeding the setData time threshold / Total page PV * 100% (setData is the most frequently used interface in mini program development and also the most likely to cause performance issues. The amount of data and frequency of setData are the most common causes of page stuttering. The stuttering monitored here only includes stuttering caused by long setData time.) |
| Bounce Rate | The proportion of visits where this page serves as the exit page, i.e., exit page count / visit count. |
| Abnormal Bounce Rate | The proportion of visits where this page experiences abnormalities (including JS errors, request errors, slow loading time, stuttering, etc.) and serves as the exit page, i.e., abnormal exit page count / visit count. |
| Request Frequency | Number of requests initiated through wx.request per second. (WeChat official recommendation: The number of requests initiated through wx.request per second should not exceed 10) |
| Page Online Duration | Average time users spend on this page per visit, i.e., total time spent on this page / number of visits |
| Page Abnormality Rate | Page abnormal PV / Total page PV * 100%. A page is considered abnormal if it experiences any of the following: slow loading time, network errors, JS errors, or stuttering. |