LoadView emulates users on your website or server by performing specified actions on your website (device) like browsing, searching, adding products to their shopping cart, etc., or generating certain types of requests to your device.

Knowing how much your device can handle helps planning further software or hardware updates and to be prepared for real traffic.

You can define the number of users that will be performing these actions, the duration of the LoadView test (Load Test), and set up a fully customized scenario with the rate of arrival/departures of those virtual users.

LoadView Test Setup

To run load testing, you will first need to add (the New Test button) and set up a new load test. You can also make a Clone From Existing Test. Choosing to copy an existing test or task(s) brings up a list of available tests. After selecting a test, if the test has multiple tasks, you can check the tasks you want to copy.

You can set up the following types of tasks:

In addition, if you have been using Postman to test Web API performance, you can go with the Postman Collection Task to set up a load test in LoadView using Web API calls from Postman.

Configuring a Load Test Scenario

Once your device and tasks are set up, you can configure the Load Test Scenario. Each test scenario has a unique ID displayed on the configuration page. Leverage the ID while configuring requests to LoadView API.

LoadView setup involves several steps that are explained below.


Validation verifies that the tested device is valid and runs without errors. Validation results status is presented in the device details section.

In case of detected errors, click View Details to review the errors on the Errors tab of the Performance Report.

It is highly recommended that you fix all errors prior to running the test.

User Behavior Profile

The profile describes simulated user behavior on a website during task execution. To customize simulation of user interaction with a website, see User Behavior Profile.

Choosing Load Type

Load Type allows you to select between different types of load tests. Each type has some specifics that define what it is best to be used for, available settings and test results.

You can choose among the following load types:

  • Goal-Based Curve verifies if your website complies with the predetermined throughput (transactions) by automatically adjusting the number of simulated users. For detailed instructions, see Setting up Goal-Based Load Test.
  • Load Step Curve allows setting manually a specific number of concurrent users (requests) by specifying ramp up/ramp down rates and time. For detailed instructions, see Setting up Load Step Load Test.
  • Dynamic Adjustable Curve allows adjusting the number of concurrent users (requests) manually in real time during test execution. For detailed instruction, refer to Setting up Dynamic Adjustable Load Test.

For more help on how to pick the load type, see Choosing Right Type of Load Test.

Load Injector Payload

To emulate virtual users, we launch Load Injector Servers (LI) that, in turn, will run virtual users. The Payload setting sets the number of those virtual users that will run on each LI.

You can adjust the Payload value but it is recommended to use the value suggested by our system on the results of device calibration.

Network Proxy

Depending on whether the target website is available or not from the public Internet, select a type of locations to send the load traffic from.

Do Not Use Network Proxy if your website is available from the public Internet. All load traffic will be sent from the LIs with randomly allocated IP addresses. Herewith, each Load Injector will have its own unique IP address.

If you need to test a website behind the firewall, you can allow load traffic from specific IP addresses that you can open your firewall for. To do this, use the Public option. The load traffic will be sent from Load Injector Servers with dedicated IP addresses. Find the list of the static IP addresses here and whitelist the IPs to your firewall.

If the target website is not available from the public Internet and you can not open the firewall for specific IPs, use the On-site Agent option. LoadView On-site Agent can be installed inside the same network as a target website. Herewith, the load traffic will be sent from within the local network.

Load Injector Geo Distribution

You can select the geographic location of LIs and, in turn, the allocation of virtual users between different geographic locations to better match your traffic distribution. To test behind a firewall, consider the Static Proxy option.


On the footer of the test page, you can review your Load Test settings, get a price quote based on your settings. If you want to adjust anything, you can go back to the section you want to change and edit the settings. If validation failed, fix errors before starting a test.

The Load Test price is calculated based on the following values: the cost of virtual machines required for the test, the test duration, and the number of virtual users simulated during the run.


Please read the Legal Agreement and accept the terms by checking the checkbox and typing your name. Note that LoadView tests that cost more than $500 will require phone verification by providing your mobile phone number and entering a confirmation code sent to the number you’ve provided. LoadView tests that cost more than $1,000 will require voice verification over the phone by our support staff that will call a specified number.


On the Start Load Test pop-up, you will be prompted to provide your email in the Email Notification section (optionally) to receive a notification on the test completion and select the start mode. A load test can be started immediately or later at a specific time (up to 24h).

For the tests with a postponed start time, the option of concurrent test execution is also available.

Once you have run the test (immediate start), it will start within 10 minutes (up to 1 hour depending on the region selected).

If for some reason you need to stop the test, click Abort on the test Summary page. However, keep in mind that if LIs have been started (the Starting Load Injectors status) the test price will be written off from your wallet.

While the test is starting it will go through a sequence of statuses that are explained below:

  • Submitting Test Request – sending your test settings to the server to run.
  • Initializing.
  • Starting Load Injectors – we send cloud providers a signal to set up the required number of virtual servers and deploy virtual users. This step can take a lot of time (up to 1 hour) and it is recommended to provide the email to receive an email notification once it’s complete.
  • Sending Execution Plan  – we are sending LoadView scenario and tasks to LIs.
  • Running – once the test is running, you will see the charts with LoadView metrics updated in real time, including the number of visitors, the number of errors (if any), device response time, etc.
  • Processing Data – once the test is over, we upload all the responses from the virtual server to our server and display those responses for a more detailed analysis and review. The data retention time is 365 days for the paid version and 31 days for the trial. Please note that this step can also take some time since LoadView tests generate a lot of response data.
  • Finished.

The system notifies you with the corresponding message on the Load Test Report page after the test completed.

Load Test Results

You can find the test results on the Load Test Report page.

LoadView Overview Video