What tick data is and where the delay comes from
Every time the price of an instrument changes at a broker's matching engine, that event is a tick. The broker's server sends that tick update to your trading platform. Your platform receives it and updates the chart. The time between the price changing at the broker and the chart updating on your screen is the tick data latency.
The source of the delay is the network path between the broker's server and your machine. The further you are from the broker's data centre, and the more variable your ISP's route, the older the price on your chart at any given moment. On a 100ms latency connection, your chart is always showing you the market as it was 100ms ago — a gap that is invisible on daily charts and significant on M1 charts during fast moves.
When tick data latency matters for trading decisions
For swing traders on H4 or daily charts, tick data latency is irrelevant. The price on screen is close enough to current to make no practical difference. For scalpers working M1 charts, tick data latency is the difference between entering when you think the move is happening and entering after the move has already happened.
News events compress this problem. During an NFP release, the price reprices multiple times per second. A platform receiving tick data 200ms late is showing prices that are significantly behind. The chart looks like a valid entry level. The actual current market is already past it.
How a proxy reduces tick data latency
A proxy node near the broker's data centre receives tick data updates faster because the path from the broker's server to the proxy node is short and direct. Your platform's feed travels from the broker to the proxy node — a few milliseconds at data centre interconnect speeds — and then through your residential connection to your screen. The variable transit section of the path is removed. Feed updates arrive at more consistent intervals, and the lag between market events and your chart updates is reduced.