"We’ve found that StressTester™ is very easy ...

we proved that the results it supplies are the same as the industry leader."

Darrall Pullen, CTO, PPG

"StressTester™ provides Tescom with a more Agile approach – we are able to reduce the time between test design and execution"

Marco Venzelaar, Tescom UK

"A job that would take 10 days to prepare in other tools, takes 2 or 3 days with StressTester™"

Head of Testing, Mission Testing

"There is no limit in functionality – it covers all that products 10 times its price provide!"

Darrall Pullen, CTO, PPG

"One of the strongest pros for StressTester™ is Reflective Solutions’ unprecedented customer support"

Will Smithee, Questcon USA

StressTester™ Learning Center - Tutorials

» Tutorials » Analysing Performance Test Results » How to Improve the Overall Transaction Time

« Which User Journeys Were the Slowest? | Identifying the Slowest Steps in a Page »
 

How to Improve the Overall Transaction Time

  • It may be that your business does not particularly care if certain web pages take multiple seconds to respond, the key metric is the total time to complete the transaction.
     
  • To identify where to focus effort to achieve a reduction in the overall time, we need to analyse the User Journey that implements the business transaction of interest.
     
  • Within the data table, double click the name of your User Journey.
     
  • This will switch the analysis into single User Journey mode; within which you can identify the slowest pages and steps of the selected User Journey.
     
  • Select all of the Step Groups (web pages) within the Steps Group window of the navigation panel and click Show Results or Refresh.
     
  • The graphs and data tables on the right-hand side of the screen will update.
     
  • The Average Response Comparison graph shows the average response of each selected web page compared to each other in a pie chart.  Alternatively, you could sort the data table by the Avg Response column.
     
  • Either way, you will be able to identify the pages where effort would be worthwhile (those taking the longest time at present) and those that are not worth focusing on.
     
  • If average response times are not as much as interest as maximum ones are, this tutorial will soon show you how to configure the graphs that are most important to you and display them in the GUI in the best way that works for you.

« Which User Journeys Were the Slowest? | Identifying the Slowest Steps in a Page »
 

Not seeing the StressTester™ information that you need - please email Support.