Clicky

LoadView Pricing

On demand. No commitment. Cancel at any time.


Price Per Load Test:

Each Virtual Machine: $4
HTTP Load: $0.01 per user per minute
Full Browser Load: $0.10 per user per minute
Flat monthly cost to store test result data: $9.99
Sign Up Now
No credit card required. Receive $20 load testing credit upon signup.

LoadView Pricing Calculation

Three Simple Steps to Build Your Custom Scenario


*This calculation is automatically done for you when you create a new test.


Don’t overload your own network and hardware.
Utilize a globally distributed cloud based load testing system.

Global Load Testing Locations

Sample Pricing Scenarios

The following examples illustrate a few simple tests.
Create your own free trial to setup a sample test of your own scenario to see what the cost will be. You can create multiple scenarios to price out different tests without a charge.

Small Homepage HTTP GET Request:

Load test a single URL with 200 simultaneous users for 20 minutes.

Assuming each instance can run 200 virtual users:
(2 VM x $4) + (100 users x 20 minutes x $0.01) = $28

Small Real Browser Interaction:

Load test the login portal of your website using a real Chrome/IE browser with 100 simultaneous users for 20 minutes.

Assuming each instance can run 10 virtual browsers:
(10 VM x $4) + (100 users X 20 minutes x $0.1) = $240

Medium Homepage HTTP GET Request:

Load test a single URL with 1000 simultaneous users for 20 minutes.

Assuming each instance can run 500 virtual users:
(2 VM x $4) + (1000 users x 20 minutes x $0.01) = $208

Multi-step API HTTP POST:

Load test multiple steps interacting with an API with 1000 simultaneous users for 20 minutes.

Assuming each instance can run 500 virtual users:
(2 VM x $4) + (1000 users x 20 minutes x $0.01) = $208

We Recommend that you run a small test scenario before running a large load test to make sure everything works as expected, because once we initiate a test, the base fee is fixed.
(We are committed to paying the cloud provider for the first 1 hour on every virtual machine initialized no matter how long the test actually runs).

FAQ Regarding Pricing


Is there a cost difference between Load Testing HTTP URL and Web Applications (full browser rendering)?

Yes. Basic HTTP requests simply generate traffic on the server while web application testing renders the page in a real browser, requiring much more resources on the servers generating the traffic. This means that an HTTP might be able to generate 100 to 1000 simultaneous users per virtual machine where a full browser test might only be able to generate 10 simultaneous users per virtual machine.

For example, a 10 minute test requiring 100 simultaneous users for HTTP would have a base cost of 1x$4 virtual machine + 1x$4 baseline server+ .01x100x10= $18.
The same 10 minute test run in a real browser might cost 10x$4 virtual machines + 1x$4 baseline server +.10X100X10= $144.

Also, full browser rendering uses the baseline server to capture video of the page loading which requires much more storage capacity for the test results.

Why do I need to calibrate my test before getting the exact pricing?

Calibrating a test automatically determines how much CPU% is used by the virtual machines for each simultaneous user. This tells us how many simultaneous users we can run per virtual machine. The number of virtual machines directly affects the cost of the test.

Why is calibration for load testing HTTP URL and web application is different?

Web application testing renders a webpage in a real browser, which takes much more system resources from the virtual machine than simply sending a GET or POST request to the web server.

Is there a monthly or annual commitment or fees?

There is no commitment and you can cancel at any time. There is a small data retention fee ($9.99/month) to retain all the data generated from load tests.

Why is the price so different when changing the User Behavior Delay?

As you increase the delay between users (simulating users pausing to read a page) the CPU of the virtual machine is freed up to process more user sessions, increasing the recommended number of users per virtual machine.