# Test your website. Understand the results. Create a real-browser scenario, run a controlled load test and see where the experience slows down or fails. Start small on a site you are authorised to test. ## What would you like to do? {#start} ### [Run your first test](https://userlimit.com/documentation/get-started/first-load-test.md) Verify your target, create a simple scenario and reach your first report. ### [Build a scenario](https://userlimit.com/documentation/journeys/create-and-import.md) Turn a visitor task into supported actions and validate the result. ### [Understand a report](https://userlimit.com/documentation/results/read-a-report.md) Check what ran, inspect failures and choose the next investigation. ### [Check product fit](https://userlimit.com/documentation/get-started/overview.md) Review conversion, execution limits and supported behavior. ## Put the result to work {#recipes} - [Test a storefront](https://userlimit.com/documentation/recipes/storefront.md) - [Prepare for a launch](https://userlimit.com/documentation/recipes/launch-readiness.md) - [Explain results to a client](https://userlimit.com/documentation/recipes/client-summary.md) ## The testing workflow {#workflow} A test begins with a verified domain and a scenario that represents how a visitor uses the site. Once the scenario has been validated, traffic settings determine the workload for a run. Its report can then be used to investigate failures, compare performance or plan a further test. The [Playwright compatibility](https://userlimit.com/documentation/reference/playwright-compatibility.md) reference describes the supported actions and how scripts are converted into scenario steps. ## Get the answer you need {#help} - [Usage and billing](https://userlimit.com/documentation/reference/usage-and-billing.md) - [Troubleshooting](https://userlimit.com/documentation/help/troubleshooting.md) - [Production safety](https://userlimit.com/documentation/help/production-safety.md) - [Support](https://userlimit.com/documentation/support.md)