Technical Indicators

Is Reducing Technical Indicator Lag Always Better?

Distinguish smoothing delays from waiting for a bar to close. Explore frequent changes in fast signals, misleading historical charts, and how to identify the actual decision time.

Technical indicators calculate from price and volume already received, so confirming a new move can take time. Shortening the period can speed up the response, but it also makes the indicator react more often to temporary changes. Understand smoothing lag in the calculation separately from the confirmation delay caused by waiting for a bar to close.

Reducing noise also dilutes recent changes

Averaging multiple prices reduces one or two fluctuations to make the overall path easier to see. The same process blends abrupt new changes with old values, so the line follows actual price with a delay. It is difficult to decide whether a longer or shorter average is better without specifying the time horizon you want to observe. If the purpose is to summarize a long-term trend, resistance to immediately changing direction on a short-term spike may serve that purpose. Lag is a characteristic to assess alongside the calculation’s purpose, rather than the name of an error.

Unconfirmed values appear sooner but can change

If an indicator using daily closes updates intraday, it is reflecting a current price that is not yet final. A crossover appearing in the afternoon can disappear before the close, leaving only final values on the completed chart. Save provisional signals within bars to understand why a real-time alert differs from the later chart. Using only confirmed bars reduces these changes but adds waiting time. When displaying a weekly indicator on a daily chart, also check whether it uses the value of a week that has not yet ended.

Attractive historical lines versus actionable records

Some tools draw markers for highs and lows confirmed later at earlier chart positions. Mistaking those markers for information available at the time removes the cost of lag from the calculation. Performance comparisons should start from the actual confirmation time rather than the low shown on screen. When comparing fast and slow settings, record repeated signals, execution costs, and losses during abrupt changes alongside signal delays. A display feature that shifts a line ahead of price also does not mean the data predicted the future; separate calculation time from plotted location. Include the cost of waiting in the validation results.

Worked example

Hypothetical example: If price is 100 won for four bars and becomes 120 won on the fifth, the 5-value simple average is 104 won. At the same point, the latest 2-value average is 110 won, a larger move. If the next bar’s price returns to 100 won, the 2-value average stays at 110 won; if the following bar is also 100 won, it falls to 100 won. Even a fast average does not simply copy price. Compare response speed and fluctuations across multiple bars.

What to check

  • Distinguish smoothing lag from waiting for bar confirmation.
  • Save the actual time when a signal first appeared.
  • Check whether unfinished bars from another timeframe are referenced.
  • After shortening a period, compare repeated signals and costs as well.

Sources and primary materials

This is educational material about research methods. For an actual company decision, verify the filings and primary sources for the relevant period.

  1. Fidelity — Exponential Moving Average (EMA) ↗
  2. TradingView Pine Script — Repainting ↗