Know your limits before your users find them

Capacity Planning

Use repeatable traffic and data to estimate capacity for a particular workload. Virtual users in a script are not a direct count of real people; response times, pacing and user behavior affect the relationship.
Standalone k6 example
Adapt this script and run it with k6 against an approved target. loadtest.dev accepts declarative GET/HEAD plans; it does not execute these scripts.
Progressive load testing methodology
Estimate capacity for the measured workload
Cost-per-user infrastructure analysis
Auto-scaling validation
Baseline establishment for monitoring
Data-driven scaling decisions
capacity-test.js
import http from 'k6/http';
import { check, sleep } from 'k6';

// Gradually increase load to find the breaking point
export const options = {
  stages: [
    { duration: '2m', target: 50 },
    { duration: '2m', target: 100 },
    { duration: '2m', target: 150 },
    { duration: '2m', target: 200 },  // Highest concurrency in this example
  ],
  thresholds: {
    http_req_duration: ['p(95)<1000'],
    http_req_failed: ['rate<0.05'],
  },
};

export default function () {
  http.get('https://myapp.com');
  sleep(1);
}

Frequently asked questions

Related guides

Stress Test Your Website
Use a standalone k6 stress script to raise virtual-user concurrency, compare response times, and identify degradation under an approved traffic budget.
Soak Testing
Use an extended standalone k6 script to observe latency and error trends over time, alongside server metrics for memory and connection-pool behavior.
Spike Testing
Model a rapid traffic increase with standalone k6 stages, then observe latency, failed requests and recovery within your target’s approved load budget.

Use an HTTP plan with loadtest.dev

For estate apps, declare GET/HEAD requests to a verified hostname and submit a plan through the authenticated API.
loadtest.dev — Part of the Narduk Enterprises network