LoadFocus.com is a cloud load testing tool which helps you load test your App & APIs with 1000's of concurrent users from multiple locations

Before running a load test for APIs, WebSites, Web or Mobile Applications on LoadFocus.com, you should check the tips below and understand which HTTP response codes you could receive and what do they mean. This article will help to analyze a load test report or a performance testing report.

General Tips

  • make sure the load tested URL is up and publicly available before running any load or performance tests
  • check the HTTP method (GET is the request done by browsers when accessing a website or an API endpoint)
  • start with a small number of clients (25-50 clients) and check the number of errors
  • try to increase the number of the clients gradually to understand how your API, Website or WebApp behaves
  • check the Time, Latency, Hits, Throughput and Errors for each test to check the performances of your system

If you receive 3xx redirection responses you need to check:

  • if the URL added for the load test is doing any redirects to another URL
  • if you are testing the redirection, try to do the load test on the final URL, after the redirects end
  • remove the “Follow redirects” checkbox next to the URL if you want to avoid redirecting your requests and do the load test on the URL added

If you receive 4xx client errors you need to check:

  •     the URL is correct and publicly available
  •     check the HTTP Method used: GET, POST, PUT or DELETE (GET is the request done by browsers when accessing a website or an API endpoint)
  •     the request headers, cookies, query params or basic HTTP auth params are set correctly

If you receive 5xx server errors you need to check:

  • the response code, usually if the load tested API, WebSite, Web or Mobile Application doesn’t handle the load properly you’ll start receiving 503 Service Unavailable responses.
  • try to reduce the number of clients (concurrent users) for your load test and check the boundaries of your system
If the tested APIs, WebSites, Web or Mobile Applications don’t handle the load properly you’ll start receiving 5xx (server errors) or other connection errors.
According to w3schools.com, here is a list of HTTP status messages that might be returned on running a load test for API Endpoints, WebSites, Web and Mobile Applications:

1xx: Information

100 Continue  The server has received the request headers, and the client should proceed to send the request body
101 Switching Protocols The requester has asked the server to switch protocols
103 Checkpoint Used in the resumable requests proposal to resume aborted PUT or POST requests

2xx: Successful

200 OK The request is OK (this is the standard response for successful HTTP requests)
201 Created The request has been fulfilled, and a new resource is created
202 Accepted The request has been accepted for processing, but the processing has not been completed
203 Non-Authoritative Information The request has been successfully processed, but is returning information that may be from another source
204 No Content The request has been successfully processed, but is not returning any content
205 Reset Content The request has been successfully processed, but is not returning any content, and requires that the requester reset the document view
206 Partial Content The server is delivering only part of the resource due to a range header sent by the client

Other: Connection Error

The URL added for the load test could not be accessed for one of the following reasons:
– the URL is not publicly accessible (we support only URLs which can be accessed publicly via Internet)
– the system crashed for some reason
For the load testing documentation please click here.