What is XLT?
XLT (Xceptance LoadTest) is an open-source load and performance testing framework built by Xceptance GmbH, released in full under the Apache 2.0 license, with no paid edition. Xceptance charges for XTC, a SaaS that runs XLT tests on cloud load generators, and for support and training. It is Java-based, scripts tests in JUnit-style classes, and combines functional regression testing with load generation in the same scenario language — a Selenium-friendly model that has long been popular in e-commerce QA teams.
XLT runs from a controller machine and dispatches load to one or more agent machines (on-prem or cloud-provisioned). It targets teams that already invest in Java tooling, want full source-code control over their scenarios, and prefer self-hosted infrastructure over a SaaS dashboard.
When XLT is the right tool
XLT is a fair fit when these conditions hold:
- Java-centric QA team. Existing Selenium / JUnit muscle memory makes XLT scenarios feel native.
- Functional + load in one tool. The same script can validate user flows and replay them at concurrency for load.
- Self-hosted infrastructure. Strict data-residency or air-gapped requirements rule out cloud-only platforms.
- Open-source license preference. XLT is free under Apache 2.0, with no community/enterprise split, and the source is on GitHub.
If your team is comfortable provisioning agent machines and writing Java load scenarios, XLT delivers a powerful combined functional+load workflow.
Where XLT stops being enough
XLT's strengths come with friction that most modern web teams notice:
- Heavy Java setup. JDK, controller, agents, build tooling — non-trivial onboarding compared to paste-a-URL cloud tools.
- Agents to run or pay for. Self-hosting means provisioning and maintaining agent machines for realistic distributed load. XTC deploys cloud load generators for you instead, but adds a monthly fee plus machine hours.
- No bundled API monitoring. Continuous API uptime and SLA alerts need a separate tool.
- No Core Web Vitals tracking. Lighthouse and CWV monitoring are out of scope.
- Reporting model. Powerful but local; sharing results across non-engineering stakeholders takes extra work.
LoadFocus vs XLT — feature comparison
How LoadFocus compares against a typical XLT deployment. Prices from the Xceptance XTC pricing page, checked October 2026.
| Feature | LoadFocus | XLT |
|---|---|---|
| Cost | Free tier; from $29/mo ($19/mo billed yearly) | Free open source (Apache 2.0); optional XTC SaaS from $50/mo plus machine hours |
| Cloud-native execution | Yes (no agents to install) | With XTC (cloud load generators deployed automatically); self-hosted agents optional |
| JMeter cloud execution | Yes (up to 20,000 VUs on Enterprise) | Java/Selenium scripting |
| Browser-based load testing | No (protocol-level HTTP load; Playwright browser checks are part of API monitoring) | Yes (Selenium-based) |
| API monitoring | Yes | No |
| Core Web Vitals monitoring | Yes | No |
| Multi-region test locations | 25+ globally | Wherever you provision |
| Hosted dashboard | Yes | Local reports |
| CI/CD integration | Yes (API + GitHub Action) | Maven/Gradle integration |
| Pay-per-test pricing | Yes | Self-hosted infra cost, or XTC machine hours |
FAQ
Is LoadFocus a direct replacement for XLT?
For teams using XLT primarily for HTTP and browser load testing, yes. Teams that depend on XLT's Java-based functional + load combined scenarios may want to keep XLT for that workflow and use LoadFocus for cloud-scale distributed load and continuous monitoring.
Can we reuse our existing XLT scenarios?
XLT's Java JUnit-style scripts do not port directly. Most teams migrating choose to recreate the top user flows in JMeter or via the LoadFocus browser recorder — usually a few days for the critical scenarios, and a faster ongoing iteration loop afterward.
Does LoadFocus support self-hosted execution?
No — LoadFocus is cloud-native. If air-gapped or strict on-prem execution is a hard requirement, XLT remains relevant. Most non-regulated teams find cloud execution faster to set up and cheaper to scale.
What about pricing?
XLT itself is free and open source (Apache 2.0). The real cost is either self-hosted agent infrastructure plus the team time to maintain it, or an XTC subscription: Standard at $50/month or Bring Your Own at $500/month, plus machine hours from $0.30/hour. LoadFocus uses transparent monthly tiers from $29/month ($19/month billed yearly) with concurrent VUs and test minutes published upfront, including load testing, API monitoring and page speed on the same account.
How long does setup take?
Minutes. Sign up, paste a URL or upload a JMX, pick a load profile and run — no JDK, no controller, no agent provisioning.
Can it run in CI/CD?
Yes. LoadFocus exposes a REST API and a GitHub Action so load tests run on every merge with thresholds for response time, error rate and concurrency. XLT integrates via Maven/Gradle but needs agent machines available, either your own or the cloud load generators XTC deploys.
Try LoadFocus free
If you're running XLT today and want cloud-native load testing with API and page speed on the same account, LoadFocus is worth a parallel trial. Sign up at loadfocus.com/signup — no credit card — and run your first cloud load test in minutes.
