I currently work in QA at a small software company that develops web based training software. Most of the work I do is manual usability testing but recently I've been tasked with performance testing pages and features of the site as it has been running very slowly in certain areas. Currently the way I go about this is by timing the page loads either manually using the stopwatch on my phone or through the chrome devtools before and after any performance optimisation has been implemented.

I am 99% sure there must be a much better and more precise way of doing this and would really appreciate someone pointing me in the right direction as I'm struggling on researching this question on my own.


3 Answers 3


Firstly, I would say that the Chrome devtools is a reasonable strategy, if you perform the test more or less the same way and care only for an overall improvement in performance.

But if you want to scale or have more precise, you can use Sitespeed.io

You can just make a shell call and pass the correct parameters:

docker run --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io:9.8.1 https://www.sitespeed.io/

And it will give you plenty of information about the page:

enter image description here

Note that it considers page rendering time, differently from JMeter or Gatling, which are primarily service-focus tools.

You can also script more complex flows that a simple page landing.

  • Thanks that's exactly the kind of thing I was looking for! Sep 9, 2019 at 20:20

Before moving forward in a software testing company there are some of the questions you should ask and steps you should think before started with performance testing:

1.Identify the Objective of Load Testing Is your desired load testing objective to test the performance of an application during peak load times, or is the objective to test the stability of an application under a heavy load?

2.Determine the Type Of Application for Performance Testing It is important to know which type of application will be under test. Is the application that requires performance testing web-based, a desktop application or a mobile app?

3.Define the Test Plan This is an important step because a well-defined test plan can help prevent delays. Does your plan define the priority of APIs scenarios? Are all positive and negative test scenarios included?

4.Identify Special Software Or Plug-Ins Does the application have any special software or plug-ins involved? Does the application use 'Flash player' or 'Java Swing Objects'? This is important to know because these special software or plug-ins may need specialized performance testing software.


You can use Jmeter for load and performance testing.

  • 2
    JMeter is for service testing, it does not take into consideration frontend rendering time - which is the problem posted: "usability testing .... site as it has been running very slowly in certain areas." Sep 9, 2019 at 6:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.