Statistics
Last updated
Last updated
With IMQA WPM statistics, you can retrieve previous data of various subjects using periods and conditions for observance and analysis. You can analyze the user data distribution for each performance index along with the user’s environment, or obtain the overall web status and insight.
Distribution Analysis allows you to analyze the distribution of user data for each performance metric along with the user experience. After viewing the overall average performance in the Dashboard, you can drill down into specific bins with performance degradation in 30-minute increments.
The IMQA WPM Distribution Analysis page consists of the following:
❶ Timeline ❷ Performance rating graph ❸ User information ❹ Performance heat map
You can set the date and time (in 30-minute increments) you want to analyze. When you make changes, Performance Distribution Graph and User Experience will be updated as per your preferences.
❶ Timeline You can change the date and time (in 30-minute increments) you want to analyze. When changes are made, the performance heatmap is updated based on the selected criteria.
❷ Analysis Date Defaults to “Today." You can change the date by clicking [<] [>]. Can select a date up to 30 days ago.
❸ Selected time zone Displays the selected time zone. You can change to a different time zone.
❹ Current time zone Displays the time zone that includes the “current time”.
❺ Legend Color density is displayed in 4 steps according to the number of aggregated data by time zone.
Displays the user data distribution for the selected 30 minutes as a histogram. You can analyze User Experience and Performance Heat maps by selecting a bin in the Performance Distribution Graph area.
❶ Performance Metrics You can change the performance metrics to “Rendering Time” and “Response Time" When you change the metric, Performance Distribution Graph and User Information will be updated accordingly.
❷ Histogram The histogram shows the class on the horizontal axis and the frequency on the vertical axis. It creates classes by setting several sectors for aggregated data and expresses the frequency with the number of data belonging to each class. The histogram is useful for understanding or comparing the frequency status of an entire population.
Rendering Time
Rendering time(ms)
0 ~ 5,000ms
Number of collected data
Response Time
Response time(ms)
0 ~ 10,000ms
Number of collected data
❸ 50% baseline Displays the average performance baseline. Showing the median of the overall data distribution, it is useful for understanding overall performance. A baseline closer to zero indicates faster performance.
❹ 95% baseline Displays the baseline of bottom 5% performance. Shows where the bottom 5% of the overall data distribution begins, useful for identifying the lowest performing data. A baseline closer to zero indicates faster performance..
❺ Analyzable Bins You can select bins separated by a baseline to drill down into performance data. Filter user information by the selected bin and display a performance heatmap. You’ll see up to three bins. Bins can overlap because they are divided based on the location of the data. In this case, a bin with higher % is shown.
Bin 1: 0th to < 50th percentile in the total data distribution
Bin 2: 50th to < 95th percentile in the total data distribution
Bin 3: ≥ 95th percentile in the total data distribution
You can check the performance environment of the app user by referring to the performance rating graph. 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 web browser application
The information is displayed for the bottom 5% section of basic performance and the selected one-day user environment is displayed in percentage. This information is updated when a section is changed in the performance rating graph area.
Browser: Displays users’ browsers aggregated over the selected section.
OS: Displays the OS of the user aggregated from the selected section.
Page: Displays the page of the user data aggregated from the selected section.
User information is displayed based on the user’s User-Agent information when a user visits the website. IMQA WPM categorizes users by the OS and browser they use. OSs are typically categorized into Windows, macOS, Android, iOS, and Linux.
Browsers are generally categorized into Chrome, Safari, Microsoft Edge, Firefox, and Samsung Browser. An unspecified OS or browser may be labeled as “Unknown."
Displays the performance heat map that is related to the selected performance index standard. You can check the heat map for rendering time. For more information on the heat map by performance index, refer to “IMQA WPM User Guide > 4.6. Performance heat map”.
You can view page load times measured on individual pages or SPA-based web browser applications. If you click a desired cell in the heat map area or select a section by dragging the mouse, the “Detailed performance analysis” pop-up window will be displayed.
Rendering Time: Calculates the loading time taken until the HTML page fires an onload event or a DOM change as a bin.
Legend: Displayed in red if the section is more than the threshold, and blue if it is less than the threshold. Color density is displayed in 4 steps according to the ratio of the data collected in the same-time axis.
◼︎ More than the threshold ◼︎ Less than the threshold
You can see the HTTP response time requested by the page. If you click a desired cell in the heat map area or select a section by dragging the mouse, the “Detailed performance analysis” pop-up window will be displayed.
Response time: Calculates the HTTP response time as a section.
Legend: If the collected HTTP is in 4xx, 5xx status codes, it will be displayed in red. Otherwise, it will be displayed in blue. Color density is displayed in 4 steps according to the ratio of the data collected in the same-time axis.
◼︎ 4xx, 5xx status codes ◼︎ etc.
Performance Analytics displays the number of website accesses & visits and each performance metric as a time-series graph, and you can change bins to see where performance has dropped and how it is fluctuating from a macro perspective.
30 min: Shows performance for the last 30 minutes at 1-min intervals.
1 hour: Shows performance for the 1 hour at 1-min intervals.
3 hours: Shows performance for the last 3 hours at 1-min intervals.
12 hours: Shows performance for the last 12 hours at 1-min intervals.
24 hours: Shows performance for the last 24 hours at 1-min intervals.
Screen Analytics displays the visit rate and issue rate, as well as the bottom 5% and average for each performance metric for a page visited by website users. You can change bins to see at a glance performance degradation that occurred per page. Pages are sorted by the highest visit rate, and you can jump to “Performance Analytics by Page” by clicking the screen card.
You can check a user’s previous data on websige usage within a specific period from the User Statistics. You can inquire by period and conditions and get insights regarding website users through statistics by subject. You can check the status or identify patterns from a macroscopic perspective.
The IMQA MPM Distribution Analysis page consists of the following:
❶ Statistic Topic ❷ Data range / Search Condition ❸ Summary ❹ Usage records by criteria
You can select a detailed subject to analyze previous data. You can analyze various statistic indexes according to the selected subject.
❶ Detailed subject of statistics You can modify the detailed subject of statistics. Upon changing an index, you can view the statistics index for the corresponding subject.
You can view the statistics of app usage history from the current user statistics. Statistics on more subjects will be provided in the future.
You can select a period or search condition. Data based on the selected period and condition are retrieved.
Select the period for the retrieval. It is set to ‘Last 7 days’ by default. You can choose from ‘Today’, ‘Yesterday’, and ‘Last 7 days’.
Click [Search] to retrieve data based on the selected period and condition.
This is the summary of website usage history. Daily user count and run count are represented by a heat map on the monthly calendar. Here shows the data density.
Display criteria: Select the condition for the retrieval. It is set to ‘user count’ by default. Available options are ‘user count’ and ‘run count’. When changed, the heat map on the monthly calendar is updated.
Daily Avg: The user count and run count within the retrieved period are calculated into a daily average.
Range Total: Calculates the totals for the retrieved period.
Legend: You can view the maximum and the minimum user count and run count within the retrieved period.
Monthly calendar heat map: The daily user count and run count are visualized as a heat map on the monthly calendar. You can quickly view the figures as they are differentiated by four colors based on the maximum and the minimum numbers.
Through the monthly calendar heat map, you can quickly check the app usage status on which days the users and the number of runs.
This shows the summary of website usage history. You can view the top 5 screens with the highest views and visitors. The default order is by the highest number of visitors and views on pages. You can view the page information, user count and view count.
Visitors: Counts the number of users who have visited the page. The count refers to the number of users alone, excluding duplicates.
Views: Counts the number of visits for the page.
Check the usage by the top/lowest visited page and utilize it as a performance improvement index.
You can view the user count and session count of each page that corresponds to the retrieved period and conditions.
❶ Header(sort) The default order is by the highest number of users. You can also sort by the lowest number of users.
❷ Total Displays the total user count and run count from the retrieved results.
❸ Users & Session Displays the user count and visit count for each page
App Version: Displays the app version included in the search condition.
Users: Counts the number of users for the page. The count refers to the number of users alone, excluding duplicates.
Session: Counts accesses to your website on the selected date. This is the number of sessions that users have accessed and initiated on your website.
You can view the dates in which the page was most used by users and duplicate run count during the retrieved period by referring to the daily user count and run count by versions. Observe the daily changes here.
Displays the pages visited by users on your website that meet the view period and conditions. Sorted by default by the highest visitor count. You can view the page information, user count and view count.
❶ Header(sort) The default order is by the highest number of visitors. You can also sort by the lowest number of visitors.
❷ Total Displays the total user count and view count from the retrieved results.
❸ Screen usage Displays the page information, user count, and view count.
Page: Displays the names of pages. If the page name is too long, hover the mouse over the name to display the full name as a tooltip.
Visitors: Counts the number of users who have visited the page. The count refers to the number of users alone, excluding duplicates.
Views: Counts the number of visits for the page.
You can view the pages with the highest and lowest number of visitors and the number of visits during the retrieved period by referring to the usage record by pages. Check the usage by the top/lowest visited screen and utilize it as a performance improvement index.
