BROWSER stress test

Drives real headless browser sessions against your web stack to validate that captcha and JavaScript challenges hold up under sustained automated load.

Run BROWSER test → All methods

64 sessions

concurrent browsers

How it works

This method spins up real browser instances that fully render pages, execute JavaScript, and solve interactive challenges the way a genuine client would, then hammers the target with that traffic at scale. Because the requests carry authentic browser behavior, they test whether your captcha gates, JS challenge pages, and bot scoring can tell a real user apart from automation under pressure. Use it to confirm that challenge-based defenses stay effective and that your origin is never reached without passing them.

Parameters

concurrency1-64 sessionsNumber of simultaneous browser sessions driving the target.

rate8-128 rpsRequests issued per browser session per second after rendering.

duration30s-30mTotal length of the sustained test window.

proxy_pool10-5k egress IPsSize of the residential or datacenter egress pool used to distribute sessions.

Run it from the CLI

retro-cli

$ retro run browser --target https://example.com --rps 800 --duration 120

BROWSER FAQ

How is this different from a plain HTTP flood?+

It uses real headless browsers that render pages and run JavaScript, so it can pass challenge gates a raw HTTP request cannot, giving a truer picture of how challenge-based defenses behave.

What does a passing result look like?+

Your challenge or captcha layer keeps absorbing the sessions, origin CPU and response times stay flat, and legitimate users see no degradation throughout the window.