EVM WebSocket Response Test
Measure one connection and one validated EVM RPC response from this browser. This is not an execution or provider-stability benchmark.
Browser Probe
Connection-open time and eth_chainId response time are measured separately.
Ethereum Network
Public WS 1
wss://ethereum-rpc.publicnode.comConnection open
---
RPC response
---
Pending
Public WS 2
wss://ethereum.publicnode.comConnection open
---
RPC response
---
Pending
BNB Network
Public WS 1
wss://bsc.publicnode.comConnection open
---
RPC response
---
Pending
Polygon Network
Public WS 1
wss://polygon-bor.publicnode.comConnection open
---
RPC response
---
Pending
Add Custom Endpoint
Review with Simulation
Use simulation to inspect a proposed execution before signing. A simulation result does not guarantee a later chain outcome.
Run in Simulation ModeMeasurement Scope
Browser EnvironmentMeasured here
Local Desktop AgentNot measured here
This tool does not measure desktop-agent latency or compare browsers with local execution. Labels do not verify the intended chain.
Interpretation Guide
- Open time includes browser connection setup; it is not event-notification freshness.
- RPC response time starts when eth_chainId is sent. A valid reply is not evidence of complete event delivery or sustained uptime.
- An error or timeout describes this attempt only. Repeat controlled samples before drawing conclusions.
Design a Reproducible Test
Keep workload and observation windows comparable. Record errors and reconnects separately; avoid universal quality thresholds.