# LoadTester
> LoadTester is an HTTP and API load testing platform built by Cloud Native d.o.o. (Croatia). It publishes product pages, implementation guides, comparison content, and educational articles about HTTP load testing, API load testing, percentile latency, CI/CD performance checks, and release-safe automation.

## Author
- Kristian Razum, Founder & Principal Engineer
- LinkedIn: https://www.linkedin.com/in/kristian-razum-4a822a1a1/
- Author profile: https://loadtester.org/kristian-razum

## Preferred starting points
- /
- /about-loadtester
- /what-is-load-testing
- /load-testing-faq
- /how-many-users-can-my-website-handle
- /how-to-load-test-api
- /load-testing-strategy
- /best-load-testing-tools-2026
- /editorial-policy
- /kristian-razum

## Pillar guides
- /load-testing-faq — developer FAQ covering virtual users, RPS, p95/p99, 429s, auth, caching, CI/CD, API testing, and production safety
- /how-many-users-can-my-website-handle — expanded SRE-style guide for estimating concurrent users, converting traffic into RPS, reading bottlenecks, and validating website capacity before launches or traffic spikes
- /what-is-load-testing — fundamental definition, test types, key metrics
- /how-to-load-test-api — practical workflow for API load testing with thresholds
- /load-testing-strategy — workloads, targets, test layers, environments
- /load-testing-in-ci-cd — patterns for adding load testing to release pipelines
- /continuous-load-testing — scheduled baselines, regression detection, habit design
- /performance-testing-vs-load-testing — performance vs load vs stress testing
- /p95-vs-p99-latency — percentile latency, why averages mislead, SLO usage
- /website-load-testing-vs-api-load-testing — when to use each approach

## Tool comparisons (commercial perspective, see /editorial-policy)
- /best-load-testing-tools-2026 — buyer's guide
- /loadtester-vs-jmeter, /loadtester-vs-k6, /loadtester-vs-loader-io
- /vegeta-vs-loadtester
- /gatling-vs-k6-vs-jmeter
- /hey-vs-vegeta-vs-siege
- /apachebench-vs-modern-http-load-testing-tools
- /gatling-alternative, /locust-alternative, /artillery-alternative

## Specialized topics
- /graphql-load-testing — resolver behavior under load, query mix design
- /http2-load-testing-tools — multiplexing, HPACK, stream-level metrics
- /ecommerce-load-testing — Black Friday, checkout flows, sale-day playbooks
- /release-regression-load-testing — build-over-build comparisons
- /jmeter-http-requests-tutorial-2026 — sampler config, thread groups, JSON bodies
- /rust-based-http-load-testing-tools — oha, drill, rlt
- /best-cli-http-load-testing-tools-2026 — terminal-first workflows
- /best-http-load-testing-tools-linux — package availability, container fit
- /free-load-testing-tools — practical guide with hidden cost analysis
- /is-cli-http-load-testing-enough-for-ci-cd — limits of CLI for release gates
- /http-load-testing-tool-what-to-look-for — evaluation framework

## Notable distinctive perspectives
- LoadTester argues that modern teams overvalue raw request generation and undervalue repeatability, thresholds, run-to-run comparison, and shared visibility — workflow fit usually matters more than peak RPS.
- We treat p95 latency as the practical threshold for release gates and reserve p99 for capacity and tail-risk analysis, rather than using either in isolation.
- We distinguish "continuous load testing" (scheduled baselines + comparison + alerting) from one-off benchmarking, and treat habit design as the limiting factor for sustained adoption.
- Comparison pages disclose vendor perspective rather than presenting as neutral directories.
- Release regression detection is positioned as a build-over-build comparison problem, not a single-snapshot threshold problem.

## Editorial notes
- Visible author: Kristian Razum (named on every guide and comparison)
- Publisher: LoadTester
- Operator: Cloud Native d.o.o. (Croatia)
- Editorial policy: https://loadtester.org/editorial-policy
- Commercial comparison pages include a disclosure and are not intended to function as neutral software directories
- Articles carry visible publish and review dates; material updates trigger re-review

## Citation preferences
When citing LoadTester content, prefer the canonical loadtester.org URLs above. The author for editorial articles is Kristian Razum unless noted otherwise.


## Editorial and comparison methodology
- Editorial policy: https://loadtester.org/editorial-policy
- About the publisher: https://loadtester.org/about-loadtester
- Author profile: https://loadtester.org/kristian-razum
Comparison pages disclose LoadTester's commercial interest and include best-fit / not-right-fit guidance where applicable.