Analyzing the Results of Your Load Testing Reports

Load Testing is a type of performance testing used to test how well a system or application can handle a tremendous amount of users simultaneously. Traditionally (if we can say that about load testing), a tester needs to have pretty extensive knowledge in order to interpret the majority of the data generated by most load tests. More often than not, developers and QA managers come away from the trial of load testing software with little more than the number of users that will crash their system.

Analyzing Load Test Reports

Luckily, improvements in graphics and user interfaces in load testing tools like LoadNinja have made interpreting data much easier—if you know what to look for.

After you're done with actually load testing your application, and have improved your tests with our Load Testing Do's and Don'ts - well, you'll have to analyze your results. Here’s a list of the most important results to look at in your load tests and how you should be working with them.

Page Load Time

You absolutely want to know the average page load time for each page in your scenario. You might have a strict Service Level Agreement (SLA) that mandates how quickly pages must load, or may just want to know what this number is. It is also important to know if one page takes longer than others to load—this indicates a bottleneck in your application.

Response Load Time

Just knowing page load time, is not enough. If a page is slow, you need to know why. Being able to look at average response times for each response really gives you a detailed look into where the time is being spent. Once you've run your load tests, you can continuously integrate them with a monitoring tools.

Start Load Testing now with a LoadNinja Free Trial
Load Testing Tool for Websites and Web Apps

Errors and Warning

You need to know what errors and warnings were generated and at what level of load. This is especially important information to see in chart format. It is important to see which errors and warnings are generated and be able to see how that changes as load increases. A common error at high levels of load is “Server Error 500’s.”

Request and Response Throughput

It’s important to see the amount of data going to and coming from the tested system. This is especially important in a case where load is increasing, but bandwidth reaches and maintains a plateau. In this case, it becomes apparent that bandwidth is being throttled at some point in the process, possibly at the firewall, and often this can be fixed by changing a setting.


Because so many of today’s websites call out to a plethora of additional hosts for things like content delivery networks, ad servers, analytics servers, social media and syndicated content, it is important for these sites to be enumerated in your reports. It’s equally important to be able to view all of the calls to a particular host. If a host is called from your pages, the response time for those requests will add to the time it takes your pages to render. You must be aware of and possibly take action in the case where a certain call takes a long period of time to respond.

Related Resource

To get started with load testing, check out LoadNinja.

Your team can:

  1. Record and replay tests
  2. Test in real browsers at scale
  3. Debug in real time
  4. Get browser-based metrics (Navigations timings, response times, and more)

The trial's free for 14 days!

Start Load Testing with LoadNinja