What UserLimit tests
UserLimit runs browser scenarios under load to show how a website behaves as traffic increases, and what a report can and cannot establish.
The question UserLimit answers
Can visitors complete this path, at this workload, on this version of our site? A useful test starts with that question and ends with a decision: investigate a failure, change the site, repeat the test or proceed within the tested scope.
Scenarios, tests and runs
A Scenario defines the browser actions used to test an interaction with your website, such as opening a page and following a link. The scenario stores the browser actions needed to follow that path on a verified domain. Validation runs those actions in a single browser session to check that they can execute before they are used in a load test.
A Test combines one or more scenarios with traffic settings that determine how many sessions are requested, how their starts are distributed over time and which locations they use. Each run executes that configuration and produces a report of the recorded session outcomes, failures, timings and usage. Comparing reports from runs under similar conditions can help show how the scenario responds to increased traffic or changes to the website.
What UserLimit is suited to
UserLimit is suited to testing how visitors interact with a website, such as browsing a storefront or moving from a campaign landing page to a product page. A read-only scenario provides a way to observe performance under load without placing orders or making other persistent changes.
The same scenario can also be used to compare website releases. Keeping the workload and test location consistent makes the results easier to compare, although differences in caching and other environmental conditions can still affect them.
What UserLimit does not offer
UserLimit tests browser scenarios rather than standalone API endpoints. Reports include measurements for XHR and fetch requests made by the website, but those requests are not configured as separate endpoint tests or as a requests-per-second workload.
Imported Playwright source is converted into supported browser actions rather than executed as a complete test program. Assertions, helpers and arbitrary test logic therefore do not run as they would in Playwright. The compatibility reference describes the supported calls and conversion differences.
The browser sessions also do not provide a private-network agent or inherit your browser’s authenticated state. Targets need to be publicly accessible.
One scenario, several workloads
The same scenario can be used for a single validation session, a small baseline test and a larger workload representing expected peak traffic. Keeping the browser actions consistent while changing the session count or traffic pattern helps show how that scenario responds to increased load. The results apply to the actions included in the scenario; other parts of the website require their own test coverage.
What a report establishes
A report can show recorded execution, failures and timings for the selected conditions. Browser measurements describe the test conditions rather than the experience of all real visitors; see metrics and measurement. An accepted script, a completed click and an acceptable business outcome are different claims. Validation helps confirm that the saved actions run as intended. The report can then be compared with your performance targets.