Report
* Paid plan only
Last updated
* Paid plan only
Last updated
he IMQA MPM report page provides reports on the performance index measured for each app version. You can check the daily summary of the performance status and bottlenecks by performance index, or save in PDF or CSV format or print it.
The IMQA MPM report page consists of the following:
❶ Date / App version ❷ Report ❸ Download / Print
You can select a date to view and the app version. The report is viewed based on the selected standard.
Select a date to view the report. By default, the date is set to “today’s date”, and you can select up to 30 days.
Select an app version to view. By default, it is set to the “latest app version”.
Click [APPLY] to view the report according to the selected standard.
The report consists of the performance report and the bottleneck issues report. Performance report allows you to check the frequency of daily user data by each performance index section in percentage. For the WebView/hybrid app, the “WebView UI Rendering” is also displayed.
❶ Performance index Displays the name of the performance index and the number of aggregated data.
❷ Performance section Performance indexes are divided into 9 sections. The section in gray indicates the stable performance section and other sections indicate dangerous sections.
❸ Ratio by section Displays the ratio of aggregated data by section in percentage.
User frequency by performance index allows you to understand how many percent of users are experiencing performance issues to what extent. If most of the users are distributed in the threshold range, we can see that the app is used smoothly. If they are distributed widely, it means that the app is not optimized for various user environments. You can use this information as an improvement index to set the target performance of the app.
You can check the cause of app performance degradation by referring to the bottleneck issues report. It displays the bottom 5% screen and the user environment by performance index, and the information on the stack with performance degradation. For the WebView/hybrid app, the section related to WebView is also displayed.
You can check the bottom 5% screen of native UI rendering time, CPU and memory usage, as well as the user environment.
❶ Performance index Displays the name of the performance index and the bottom 5% section value.
❷ Screen Displays five screens of bottom 5% with poor performance and its ratio in percentage (%).
❸ OS Version Displays four OS versions of bottom 5% with poor performance and its ratio in percentage (%).
❹ Device Displays four devices of bottom 5% with poor performance and its ratio in percentage (%).
❺ Location/Carrier Displays four locations/carriers of bottom 5% with poor performance and its ratio in percentage (%).
You can check the main screens with degraded performance, and the environment and ratio of users who experienced performance degradation by referring to the bottom 5% by performance index. You can use it as a fragmented improvement index for users in various environments.
Displays 20 URLs with the slowest response time among daily user data. By default, data is sorted in the order of the slowest response time of bottom 5%. You can check request information, bottom 5%, and average.
❶ Header(sort) By default, data is sorted in the order of the slowest response time of bottom 5%. The data can also be sorted by status, average, and P95 (bottom 5%).
❷ Slow response time 20 Displays request information, bottom 5%, and average.
Method: Displays the HTTP method.
Host: Displays the host information.
Location/Carrier: Displays the location/carrier information of the requesting user.
Status: Displays the response code.
Path: Displays the requested URL.
Average: Calculates the average of all response time of the requested URLs.
You can check the URLs with degraded performance, and the environment of the user who experienced performance degradation by referring to the Slow Response Time 20. Check the error code and the response time of a specific URL request, and use them as an index to improve performance.
Displays 20 web pages with the slowest rendering time among daily user data. By default, data is sorted in the order of the slowest rendering time of bottom 5%. You can check screen information, bottom 5%, and average.
❶ Header(sort) By default, data is sorted in the order of the slowest rendering time of bottom 5%. The data can also be sorted by screen, page, average, and P95 (bottom 5%).
❷ Slow WebView UI rendering time 20 Displays page information, bottom 5%, and average.
Screen: Displays the name of the native screen to which the web page belongs.
Page: Displays the path of the web page.
Average: Calculates the average of all rendering time of the web page in question.
P95: Calculates the average of bottom 5% rendering time of the web page in question.
You can check the web page with degraded performance and the environment of the user who experienced performance degradation by referring to the Slow WebView UI Rendering Time 20. Check the rendering time of a specific web page, and use it as an index to improve performance.
You can save or print the report in PDF or CSV format.
Click [PDF Download] to save the “[IMQA_REPORT]Project name_Ver.app version_date.pdf” file in the “Download” folder.
Click [CSV Download] to save the “[IMQA_REPORT]Project name_Ver.app version_date.pdf” file in the “Download” folder.
Click [Print] to display the “Print preview dialog” window while keeping the report form.
