How fast is TradingView to MT5? Real latency of webhook execution

The EA polls on a timer. InpPollSeconds defaults to 1 second, so a TradingView alert usually reaches CTrade on about that cadence, plus TradingView's send time and the broker's accept. This page is not a lab study and it does not publish an average of customer fills. For swing and most intraday Pine strategies the default is enough. It is not an HFT bridge.

Where the time goes

1. TradingView fires the webhook (their queue, not yours).
2. PineConnector authenticates, maps, and enqueues — usually milliseconds.
3. The EA polls on InpPollSeconds (default 1 second). This dominates.
4. Broker accept / reject is extra and varies by symbol and session.

For an MT5 fill, the trade log stores latencyMs from signal created to the EA acknowledgement. Compare your own VPS and home PC rows. Exchange fills record their own timing and are a different path. Do not treat one demo ticket as a benchmark.

How to keep it honest

• VPS near the broker, terminal always logged in, AutoTrading on
• WebRequest allowed for the app domain (a blocked domain looks like "EA did not acknowledge")
• Do not stack three copiers on the same login

A ZeroMQ socket path is planned for 10–50ms as a later upgrade. Today's production path is WebRequest polling. If a vendor promises exchange-matching speed from a TradingView alert, they are selling a different physics.

Install the EA with the install guide, keep the brakes on from risk controls, then start a trial and read latencyMs on a demo fill.