TradingView alerts to webhook: the latency chain nobody counts

[Amanhasnoname]

Plenty of traders send TradingView alerts to a webhook that places orders at a broker. It is convenient, and the latency chain is long. The alert fires after the bar condition is evaluated on TradingView's servers, then goes through a webhook, a relay service, and finally an API call to the broker.

Each step adds delay. The total can range from one to several seconds, sometimes more during busy periods. For a swing system, that is fine. For a scalper, it is a serious handicap.

Alert behavior has quirks. Alerts triggered "once per bar close" wait for the candle to finish. "Once per bar" fires at the first tick that meets the condition, but still goes through the chain. Alerts can be delayed or occasionally missed under heavy load.

Test the delay by comparing the alert's timestamp with the fill timestamp, and with the actual price move.

If the target is a few pips, the delay may cost more than the signal's edge. Consider local execution instead.

What is the measured delay from the alert condition to the broker fill?