Back to home

Product guide

How to load test your site with Load Curl

From sign-in to live metrics — a visual walkthrough of the dashboard workflow at app.loadcurl.com. Paste a curl command or configure your request manually, set concurrency and duration, then watch real-time results.

Go to app.loadcurl.com to access the Load Curl app. This is where you configure API requests, set load parameters, and watch live metrics while a test runs.

If you already have an account, sign in. Otherwise, create a free account with your email — no infrastructure setup required.

On the sign-in screen, enter your email and password, or use Google to continue. New users can click Create account to register.

Once authenticated, you land in the dashboard where you can import HTTP requests, configure concurrency, and monitor real-time performance metrics.

Load Curl sign-in page with email, password, and Google login options
Sign in with email and password, or create a new account to get started.

Organization management is available on Pro and Enterprise plans. If your account requires an organization, open the Organization page from the sidebar.

You can create a new organization or accept an email invite from a teammate. After setup, return to the dashboard to continue.

  • Click Create organization on the Organization page.
  • Enter your company or team name — you become the organization owner.
  • Invite teammates from organization settings to share tests and results.
Organization page prompting user to create an organization or accept an invite
Organization page — create a workspace or accept an invite.
Create organization form with organization name field
Enter your organization name and click Create.

Use the Request builder to define the endpoint you want to load test. You can fill in the form manually or paste a curl or Postman snippet to populate fields automatically.

Set the HTTP method and target URL, optionally name your scenario, then fine-tune Params, Headers, and Body on the tabs below.

  • Method & URL — choose GET, POST, PUT, PATCH, or DELETE and enter your endpoint.
  • Scenario name — optional label to identify this test case in your history.
  • Params — query string key-value pairs sent with the request.
  • Headers — authentication tokens, Content-Type, and custom headers.
  • Body — JSON or text payload for POST, PUT, or PATCH requests.
Request builder with HTTP method, URL, scenario name, and Params tab
Request builder — set method, URL, and optional scenario name.

Params

Add query string key-value pairs sent with the request.

Params tab with key-value query parameter fields

Headers

Set authentication tokens, Content-Type, and custom headers.

Headers tab with key-value header fields

Body

Provide a JSON or text payload for POST, PUT, or PATCH requests.

Body tab with JSON payload text area

The fastest way to get started is to paste an existing curl command or Postman code snippet. Click Paste curl / Postman in the request builder — Load Curl parses the snippet and fills in method, URL, headers, params, and body automatically. Use the help icon on the button for a quick walkthrough and example.

Paste curl or Postman button with help panel showing three steps and an example curl command
Click the help icon for step-by-step instructions and a sample curl command.

In the Load test section, configure how much traffic to send and for how long. Start with conservative values on staging before testing production.

  • Concurrent users — number of virtual users hitting your endpoint at the same time.
  • Duration (seconds) — how long the test runs once at full load.
  • Ramp-up (seconds) — time to gradually add concurrent users (0 starts all at once).
  • Requests per second — throttle per-user request rate during the test.
Load configuration form with concurrent users, duration, ramp-up, and requests per second fields
Load configuration — concurrent users, duration, ramp-up, and requests per second.

When your request and load profile are ready, use the event controls to run the test. Status shows Idle before a run, then updates while workers are active.

  • Start Test — launches distributed workers against your configured endpoint.
  • Stop Test — ends a running test early if you see errors or need to abort.
  • Reset — clears the current run state so you can adjust settings and try again.
Load test controls showing status Idle with Start Test, Stop Test, and Reset buttons
Event controls — Start Test, Stop Test, and Reset.

While the test runs, live metric cards update in real time. A log panel below shows individual request activity and responses as workers execute.

After the test completes, review total requests, success vs. failed counts, average response time, and throughput (RPS) to understand how your API performed under load.

  • Total — cumulative requests sent during the run.
  • Success / Failed — breakdown of HTTP outcomes.
  • Avg Time — mean response latency in milliseconds.
  • RPS — current requests per second throughput.
  • Logs / response — per-request output streamed during the test.
Live metrics cards showing Total, Success, Failed, Avg Time, and RPS
Live metrics — total, success, failed, average time, and RPS.
Full load test view with configuration, controls, live metrics, and log panel
Complete load test view — configuration, controls, metrics, and logs in one screen.

Ready to test?

Open the dashboard, paste your endpoint, and run your first load test in under a minute. For API references, CI/CD integration, and advanced workflows, see the full documentation.