Summary Report

• Max Users
  The maximum number of concurrent users generated at any given point in the test run is determined according to one-second intervals. First, the maximum number of concurrent users per second is calculated. Then the maximum number of users per minute is calculated by performing a Max Users calculation on all the values per second.
  Note: This does NOT refer to the total users, only the total users who ran simultaneously at any given moment. As a result, Max Users may not match your total users, which may be significantly higher.
  Example:
  • At location A, user A sends a request at 20:15:00
  • At location B, user B sends a request at 20:15:01
  • The maximum number of concurrent users at 20:15:00 is 1.
  • The maximum number of concurrent users at 20:15:01 is 1.
  • The maximum number of concurrent users at 20:15 is 1 because first the maximum number of concurrent users per second is calculated, then the maximum value per minute is calculated. In this case, it is also 1.
• Average Throughput (Hits/s)
  The average number of HTTP/s requests per second that are generated by the test. 
  Tip: Throughput for individual transactions (labels) is available on the Request Stats tab (hits/s).
  A note for JMeter tests: BlazeMeter counts unique requests that appear in the JTL file generated during the test. This means that if only high-level requests are present in the JTL file, the Hits/s figure relates only to the high-level requests. If while configuring the test, you select to include sub-samples in your runs, then HITS/s represents all high-level requests and sub-samples (images, CSSs, JSs and so on).
• Errors
  The ratio of bad responses out of all responses received.
• Average Response Time
  The average amount of time from the first bit sent to the network card to the last byte received by the client.
• 90 Percentile of Response Time
  The top average value of the first 90% of all samples. Only 10% of the sample is higher than this value.
• Average Bandwidth (MB/s)
  The average bandwidth consumption in MegaBytes per second generated by the test.

• The Test Duration (HH:MM:SS)
• The Test Start & End Times.
• The Test Type - JMeter Test, Multi-Test. URL/API Test, Webdriver Test.
• Locations: The geo-locations the load has originated from.
• Response Codes: A breakdown of the HTTP response status codes received during the test run.
• Internal notes about the report.

Graphs

There are two graphs that indicate the key performance metrics and their trends throughout the duration of the test.

• Load Graph
  Shows the maximum number of users vs hits/s vs errors rate. In the example above, you can see that while the load increased gradually until it reached its maximum, the hit/s increased rapidly and remained relatively high for the duration of the test and the error rate stayed at 0%.
• Response Time Graph
  Shows the maximum number of users vs response times, revealing how the size of the load affects the response times.

Generate an Executive Summary (Printable Report)

You can directly generate a printable version of a report using the Executive Summary button via the Actions menu.

Follow these steps:

1. Click the three dots next to your test report and select Executive Summary.
   
   A new page with the test report shows.
2. (Optional) At the top of the report, you can write your own summary and conclusions.
   
3. (Optional) To customize your report logo, click the edit icon in the logo.
   
   Note: If you have customized your account logo in Account Settings, the custom account logo will display.

In the Printable Executive summary you will find:

• Top 5 slow responses
• Top 5 errors
• Test setup details
• Graphs presenting users, response times, and hits per second
• Summarized aggregate report, filterable by labels
• Summarized error report

Jump to next section:

• Timeline Report