loady logoLoady.
Log in Start a free test
New featureReal-browser tests with page-speed scores

Load testing that tells you the truth

Point loady at your website, choose how much traffic to send, and get a clear verdict — how fast your site responded, what failed, and the exact moment it gave out.

Demo Start a free test
Loady.
New test Results Previous tests Domains API
Search
shop.example.com running
Requests/sec · 5,000 req/s requested · 90 s
Stop test
Holding 5,000 req/s — 3 generators live 47 s / 90 s
Requests
4,980 req/s
p99
212 ms
Average
84 ms
Errors
0.00 %
Traffic by region
Europe 1,690 req/s
US 1,650 req/s
Asia 1,640 req/s
shop.example.com 4,980 req/s

Trusted by engineering teams shipping under real traffic

odeao-labs kintsugi magnolia warpspeed sisyphus powersurge
Features

Everything you need to find your limits

Test your website the way real traffic hits it — and read the result without a manual.

  • Verdicts in plain language

    Every test ends with a clear answer: your site held up, or it didn’t — and why. Anyone on your team can read it.

  • Watch tests live

    See traffic flowing from every region while the test runs, and stop it at any moment.

  • A worldwide generator fleet

    Send traffic from Europe, the US and Asia at once. Results are merged, never averaged.

  • Compare results over time

    Save a good run as your reference point and see if your site got faster or slower.

  • Real-browser tests

    Load your pages in real browsers to see what visitors actually experience, with page-speed scores.

  • API and CI

    Start tests and fetch verdicts from your own tools — gate a deploy on a passed run.

Integrations

Verdicts where your team already looks

Post results to chat, open tickets on failures, and gate deploys from CI.

slackjirabitbucketconfluencezapierdiscordnotionzendesk
Ask about integrations
API

Run tests from your own tools

Everything you can do in the app works over the loady API: start a test, watch it live, and fetch the verdict when it finishes. Gate a deploy on a passed run, or schedule a nightly check — no dashboard required.

Learn more
POST /v1/tests Copy 
curl -X POST https://api.loady.net/v1/tests \
  -H "Authorization: Bearer $LOADY_TOKEN" \
  -d target=shop.example.com \
  -d rate=5000 -d duration=90s

# poll until the verdict is in
curl https://api.loady.net/v1/tests/r374f9ba10b
{ "verdict": "passed", "p99_ms": 343 }
Checkout capped at 3,200 req/s and the report showed the exact minute it gave out. We fixed it before launch weekend.
Ammar Foley

Ammar Foley

Platform Lead, Goodwell

Frequently asked questions

Everything you need to know about testing your website with loady.

Yes — three test runs a day against your own site, forever. No credit card required, and every run ends with the same full verdict as the paid plans.

No. You pick your website, choose how much traffic to send, and press start. The result is written in plain language — the technical detail is there for those who want it.

Nothing breaks permanently — the test simply shows where the limit is. The report tells you honestly at what traffic level your site struggled and when it began to slow down.

Yes — that is the best time. Run loady against your staging or pre-launch site to find your ceiling before real visitors do.

Most tests run for a few minutes. You watch the traffic live, and the verdict appears as soon as the run finishes.

Yes. Everything works over the loady API: start a test, watch it live, and fetch the verdict when it finishes — or gate a deploy on a passed run.

Still have questions?

Can't find the answer you're looking for? Please chat to our friendly team.

Get in touch

Our reviews

Hear first-hand from teams testing with loady.

We ran our first test in the free tier and hit our ceiling twenty minutes later. No sales call, no setup — just the number.
Nikolas Gibbons
Nikolas Gibbons Platform Engineer, Powersurge
The verdict said the bottleneck was our own API, and it was right. That honesty is why we stayed.
Marco Kelly
Marco Kelly SRE, Railspeed
We rehearse every launch with loady now. The report reads like a colleague explaining what happened.
Zaid Schwartz
Zaid Schwartz Founder, Wildcrafted
Our booking API held 40,000 req/s for the full run. The report gave us the number we put in front of procurement.
Lulu Meyers
Lulu Meyers Engineering Manager, Goodwell
The percentiles are merged, never averaged, so nobody argues with the numbers anymore.
Florence Shaw
Florence Shaw Head of Engineering, Quixotic
We pinned a reference run and now every deploy gets compared against it automatically.
Owen Garcia
Owen Garcia CTO, Solaris Energy
Reports our whole team can read — product managers included. That alone was worth it.
Harriet Rojas
Harriet Rojas Product Designer, Ikigai Labs
Real-browser tests showed us what visitors actually felt, not just what the servers said.
Stefan Sears
Stefan Sears UI/UX Designer, Magnolia
Gating deploys on a passed run took one afternoon to set up with the API.
Mathilde Lewis
Mathilde Lewis Project Lead, Eightball

Our blog

Latest blog posts

Plain-language guides to load, speed, and launch days.