Point this at your own endpoint, set how many virtual users and for how long, and watch response times as the load runs.
What this actually measures: requests to a different domain than this page run in the browser's
no-cors mode. That lets Load Check time each round trip and catch network-level failures
(DNS errors, timeouts, connection refused), but the browser hides the real HTTP status code for
cross-site requests — so a 500 error page and a 200 OK both look "successful" here. Latency numbers are
real; error counts under-report anything your server returns as a non-2xx page.
For status codes at real scale, run the k6 script from a terminal or a cloud runner instead — happy to
give you that script.