| UV (Unique Visitors) | The total number of users who visit the Mini Program page. Multiple visits by the same user are not counted twice. |
| Open Times | The number of times a mini-program is opened refers to the total number of times the onLaunch lifecycle event of the mini-program is triggered within a specific statistical period. Each time the mini-program is launched by the user from a non-running state (completely closed or not running in the background), the onLaunch event will be triggered and counted as one opening. |
| PV | The total number of visits to the Mini Program page. Jumps between multiple pages and repeated visits to the same page are counted as multiple visits. |
| Bounce rate | The number of PVs that leave the program on the current page / the total PV of the current page * 100% |
| JS error rate | (PV of the page with JS error / total PV) * 100% |
| onReady | Lifecycle function - listen for the completion of the first rendering of the page |
| First response | The time from the page opening to the completion of the first network request |
| Loading time | During the period from the onLoad of the page to the completion of the execution of the user's onReady callback. If there is a network request initiated, the loading time consumption is equal to the time point when the last request ends minus the time point when onLoad is triggered. If there is no network request, the loading time consumption is equal to the time point when onReady is triggered minus the time point when onLoad is triggered |
| Request time | The time from the initiation of the request to the end of the request response; calculation rule: return time point - initiation time point |
| Server time | The time consumed by the application server to process the request, that is, the application response time, is equal to the time from the request arriving at the application server to the completion of the application code execution and the output of the response information |
| Request error rate | (Number of network request errors/Number of network requests)*100% |
| Data volume transferred | Average data volume per network request (bytes uploaded + downloaded) |
| Callback time | Callback time refers to the time when the local code calls the data for corresponding processing after the data is transferred from the server to the client, which can be understood as local execution time |
| Network time | The time from when the network request is sent to when the server receives the request |
| Number of interface calls | Number of times the interface is called |
| Interface call success rate | (Number of successful interface calls/Total number of interface calls)*100% |
| Number of users affected by the interface | Number of users who have failed to call the interface at least once from the time the user opens the mini program to the time the user actively closes or times out of the mini program. |
| Number of users who failed to call the interface | Number of users who failed to call the interface from the time the user opens the mini program to the time the user actively closes or times out of the mini program, and one or more attempts have failed, and they have not succeeded when they leave. |
| Operation times | The number of times the specified operation is requested. Calculation rule: The operation is requested once and recorded once |
| Operation time | The time it takes to complete all requests in the specified operation. Calculation rule: When the operation is an Ajax request, the end time of the last ajax of the multiple Ajaxs corresponding to the operation - the start time of the operation click. |
| Operation availability | The ratio of successful operations to the total number of operations. Calculation formula: Operation availability = (successful operations/total operations) * 100% |
| Operation request time | The pure request time in the specified operation, excluding the blank time waiting for execution in the operation time. |
| Average server time | The average server time of multiple requests in a page or operation |
| Average request time | The average time of multiple requests in a page or operation |
| Failed operation | If any request in the operation is sent with an error, the operation is counted as failed. (For request errors, you can set network error status code filtering in the application settings). |
| Experience score | A score that measures the overall experience of the mini program, based on a comprehensive score of 7 items, including JS error rate, request error rate, request time, loading time, onready, freeze rate, and operation availability; The maximum score for each score is 100 points; Score = JS error rate score weight + onready score weight + loading time score weight + request time score weight + request error rate score weight + freeze rate weight + operation availability * weight; The indicator value of the time consumption is a customizable percentile value. |
| setData time consumption | The time difference from the call of setData to the triggering of the rendering completion callback (setData data does not exceed 256KB after JSON.stringify) |
| setData frequency | The number of times setdata is triggered per second. (WeChat officially recommends calling setData no more than 20 times per second) |
| Jam rate | PV of pages that exceed the setData time threshold / total PV of pages * 100% (setData is the most frequently used interface in mini-program development and the interface that is most likely to cause performance problems. The amount and frequency of setData data are the most likely to cause page jams. The jams we monitor here are only those caused by the long setData time.) |
| Bounce rate | The percentage of visits to this page as an exit page, that is, the number of exit pages / the number of visits. |
| Abnormal bounce rate | When the page has an exception (including JS error, request error, slow loading time, jam, etc.) and the number of visits as an exit page, that is, the number of abnormal exit pages / the number of visits. |
| Request frequency | The number of requests initiated per second through wx.request. (WeChat officially recommends that the number of requests initiated through wx.request should not exceed 10 per second) |
| Page online time | The average time a user stays on the page each time they visit, that is, the total time the page stays / number of visits |
| Page abnormality rate | Page abnormal PV / total page PV & 100%, the page is considered abnormal if any of the following 4 items occur: slow loading time, network error, js error, freeze. |