WebSocket Load Tester
Open many simultaneous connections to a WebSocket server and measure how it holds up â connections, throughput, latency, and errors, live. Everything runs in your browser.
Need a single connection instead? Try the WebSocket Tester.
WebSocket URL
Connections (virtual users, max 300)
Stagger between opens (ms)
Send message every (ms, 0 = off)
Test duration (s, 0 = until stopped)
Message payload (sent by each connection)
0 / 50
Active connections
0
Opened
0
Failed
0
Msgs sent
0
Msgs received
0/s
Send rate
0/s
Receive rate
â
Avg latency
â
Min / Max latency
0
Errors
0.0 s
Elapsed
Receive rate (messages/sec, recent)
Run a test to see live throughput.
Latency is the round-trip time for echoed messages (it is meaningful when the server echoes what you send). All connections are made directly from your browser; nothing is proxied or stored on our servers. Use this only against servers you are authorized to test.
Frequently Asked Questions
Common questions about the WebSocket Load Tester.
What does the WebSocket load tester do?
It opens many WebSocket connections to a server at once, optionally sends messages on a set interval, and shows live metrics â active connections, send/receive rates, round-trip latency, and errors â so you can see how the server performs under load.
How many connections can I open?
You can request up to a few hundred, but browsers cap how many sockets open simultaneously, so very high counts may report failures. That is a browser limit on the client side, not necessarily the server's capacity.
Is anything sent through your servers?
No. Every connection is made directly from your browser to the target server. Nothing is proxied through or stored on our servers.
How is latency measured?
Latency is the round-trip time for echoed messages â the gap between sending a message and receiving the reply. It is accurate when the server echoes back what you send.
Is it OK to load test any server?
Only test servers you own or are explicitly authorized to test. Sending heavy load to a server without permission can be disruptive and may violate terms of service.