Editorial Policy & Review Process
LoadTester publishes educational guides, tool comparisons, and product-adjacent articles about HTTP and API load testing. This policy explains how those pages are created, reviewed, updated, and disclosed.
Publisher disclosure
This website is published by LoadTester, a commercial load testing product operated by Cloud Native d.o.o. Pages that compare LoadTester with other tools are not neutral directory listings. They are vendor-published comparisons written from the LoadTester point of view. We still aim to make those pages useful by stating the criteria, acknowledging where other tools are stronger, and avoiding claims that cannot be explained.
How comparisons are evaluated
Comparison pages are reviewed against practical engineering criteria rather than only feature checklists. Typical criteria include setup effort, scripting model, distributed execution, CI/CD fit, threshold support, hosted versus self-managed operation, team usability, reporting, and the type of workload each tool is best suited for.
- Setup friction: how quickly a team can move from intent to a runnable test.
- Repeatability: whether the tool supports recurring release or regression checks.
- Operational burden: whether teams must maintain workers, dashboards, storage, and scheduling themselves.
- Decision quality: whether the output supports clear pass/fail or regression decisions.
- Best-fit honesty: whether the page explains cases where a competing tool is a better choice.
How educational guides are reviewed
Educational pages are checked for technical accuracy, clear terminology, practical examples, and alignment with the way teams run HTTP and API load tests. When a page discusses concepts such as p95 latency, virtual users, RPS, smoke tests, soak tests, or CI thresholds, the goal is to explain the engineering decision behind the metric rather than only define the term.
Use of product evidence
When a page recommends LoadTester, it should connect the recommendation to concrete product behavior: browser-based test setup, HTTP request configuration, live metrics, threshold checks, run comparison, scheduling, or CI/CD-oriented workflows. Pages should not rely only on generic marketing statements such as “easy to use” or “modern.”
Corrections and updates
Pages are updated when product capabilities change, competing tools materially change, pricing or plan assumptions become outdated, or a reader points out an error. Material updates should be reflected with a visible review or modified date. Minor spelling or formatting fixes do not require a new review note.
Authorship
LoadTester articles and comparison pages list visible authorship through Kristian Razum and review by the LoadTester editorial team. The author profile explains the technical areas behind the site: HTTP load testing, percentile latency, CI/CD performance gates, release regression detection, and tool evaluation.
How pages demonstrate E-E-A-T
LoadTester does not treat E-E-A-T as a decorative author box. Each serious guide or comparison should make the source, basis, limits, and reader benefit visible.
- Experience: pages should include practical workflow observations, runnable examples, screenshots, or implementation trade-offs.
- Expertise: pages should explain why a recommendation follows from setup, scenario design, thresholds, reporting, CI/CD, and operational burden.
- Authoritativeness: pages should link to author, company, editorial, and primary-source documentation where useful.
- Trust: pages should disclose commercial interest, name where LoadTester is not the right choice, and avoid unsupported superiority claims.
External references and limitations
Where possible, articles should prefer primary sources such as official tool documentation, public repositories, product pages, or reproducible examples. Some pages are intentionally product-positioning pages rather than academic benchmarks. In those cases, the page should make its perspective clear and avoid pretending to be independent research.
Contact and correction path
Readers who find outdated or incorrect information should use the company contact path on the About LoadTester page or contact the founder through the public author profile. Corrections that materially affect a recommendation should be reflected in the page content, not hidden only in private notes.