Configuring a load test requires you to select a load testing type. LoadView will replicate the test scenario to simulate virtual user load during testing. This article is intended to help you make a decision on which task type to use for your load test.

The choice depends on whether you want to test a web application, web page, web services performance, or web server limits.

Selecting Web Applications allows you to track load impact with scripted actions. Select Web Page if you need to test single web page performance by opening it in a real browser (Chrome, Microsoft Edge, mobile browsers/devices, etc.).  To test web resource limits by sending HTTP/S requests to the target URL without opening it in a browser, select the HTTP/S option.

For additional details, read our Comparison of HTTP vs. Real Browser Load Tests article.

Web Applications

Want to test the scalability of your web applications? Specifically, you may want to check if a large number of simultaneous users can browse the landing page, log into a website and submit a form, or add a product to the shopping cart without significant delays.

The Web Application test allows you to record user interaction steps on the target website, turn those steps into a script, and then reproduce it by emulating the specified number of concurrent users to your website.  Furthermore, this is the most comprehensive solution that utilizes real browsers to load and check all web elements responsible for user interaction. The test allows you to test browsing, web form submissions, and other types of user interaction with your web application. This allows you to determine which individual web elements are bottlenecks within overall performance. For additional details on configuring a Web Applications test, read more here.

Web Pages

If you want to test a single web page performance to ensure an outstanding user experience, you can select the Web Pages test.  You can think of this as a simplified version of the Web Applications task.  Modern web pages use a variety of web technologies (JavaScript, CSS, etc.) that define the user interface.  The task loads the page and renders all visible page content, including dynamic elements, in a real browser window to measure response times and display actual page performance.

The only limitation is the ability to test how load affects users’ interaction with the web page. For example, you can test a landing page with a login form to verify how it performs under extreme load, however, you cannot test the performance of web elements responsible for the form submission. For additional details on configuring a Web Page task, read more here.


The stack of the tasks is the simplest way to test web resources or API and SOAP-based web services performance. These tests allow you to check if a web resource can handle a particular load and ensure there are no significant delays in response time under load.

These types of tests will not tell you if your website user interface is sensitive to the load, but allows you to test and better understand your server or API performance. For additional details on configuring the tasks, read more in the corresponding articles: HTTP(S), SOAP, Rest WEB API.