Advertisement IC Markets

Moving Averages Lag by Design, So Use Them for Context, Not Timing

Optimize MetaTrader 4, MetaTrader 5, cTrader, and TradingView for speed. Discuss Level II Market Depth (DOM), custom hotkeys, and volume indicators.
Post Reply
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

Moving Averages Lag by Design, So Use Them for Context, Not Timing

Post by Fairman »

Moving Averages Lag by Design, So Use Them for Context, Not Timing

A moving average is just the average of recent closing prices, redrawn on every new candle. That makes it a summary of the past, and it always trails price.

A 50-period average on the one-hour chart takes the last 50 closes into account. If price jumps 80 pips in two candles, the average barely moves, because 48 of those closes are old. The shorter the period, the faster it reacts and the more false signals it gives.

This is why crossover strategies tend to enter late. By the time a 20 crosses a 50, a good part of the move is often already over. In ranges, the same crossovers produce a string of small losses.

Where averages help is context. Price holding above a rising 200-period average tells you which side of the market has been in control. Many traders use that as a filter, taking only buy setups while price is above it and sell setups while it is below.

Practical step: add one average, such as the 50, and mark every time price crossed it over the last month. Count how many crosses led to a real move and how many just chopped.
It’s Fairman :geek:
Recommended broker for automated trading & scalping IC Markets
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

Re: Moving Averages Lag by Design, So Use Them for Context, Not Timing

Post by Fairman »

A worked example of how I use it for context. On the 1 hour chart, if the average is rising and price is holding above it, I only look for longs on the lower timeframe. If price keeps crossing a flat average back and forth, I treat it as a range and cut my targets. The average never tells me when to enter. One thing I'd add is to choose the period once and stick with it. Switching between a 20, 50 and 100 period average until one fits your view defeats the purpose. Pick one, test whether price behaves differently above and below it on your pair, and use it the same way every time.
It’s Fairman :geek:
LondonNewsTrader
Posts: 421
Joined: Mon Sep 21, 2026 9:30 am

Re: Moving Averages Lag by Design, So Use Them for Context, Not Timing

Post by LondonNewsTrader »

Fairman wrote: If price jumps 80 pips in two candles, the average barely moves, because 48 of those closes are old.
The flip side shows up fifty hours later, when those two release candles drop out of the window and the average shifts again with no new price action at all. On short periods this creates crossovers that are purely an artifact of an old spike leaving the calculation. An EMA reduces the effect because the weight of old closes decays gradually instead of falling off a cliff, which is one reason I prefer it for the 200-period context filter you describe.
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

Re: Moving Averages Lag by Design, So Use Them for Context, Not Timing

Post by Fairman »

The mistake I see most is using a crossover of two averages as an entry trigger on a low timeframe. By the time the lines cross, much of the move has already happened, and in ranges they cross back and forth all day. Lag is fine for context, terrible for timing. What works better for me is using the 50 or 200 period average on a higher timeframe as a filter, for example only buys when price is above the daily 50. Then use price action at a level for the actual entry. The average tells you which side, the level tells you where.
It’s Fairman :geek:
FXS Prop Desk
Posts: 1689
Joined: Wed Oct 07, 2026 9:52 am

Re: Moving Averages Lag by Design, So Use Them for Context, Not Timing

Post by FXS Prop Desk »

A slope or a position relative to the average gives a quick view of the trend without trying to time entries on crossovers.

For scalpers, the 50 or 200 on a higher timeframe works as a background filter, while entries come from price action on the lower timeframe. That combination avoids most of the problems with lagging signals.
FXS Official Team | The Idea Lab & Strategy
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Moving Averages Lag by Design, So Use Them for Context, Not Timing

Post by Shadow Trader »

The lag can be put in bars. On a steady trend, a simple 50 period average trails price by about 24.5 bars, half of the period minus one.

Say EURUSD climbs a smooth 4 pips an hour on the hourly timeframe. The 50 average then sits about 98 pips under price, even though nothing about the trend has changed.

Double the speed to 8 pips an hour and the gap doubles to about 196 pips. So distance from the average is really a measure of how fast the trend is moving, not of how stretched it is.

The chart shows the made up ramp with the average holding 98 pips behind once 50 bars are in. A filter like price more than 50 pips above the average would simply be switched on by any trend faster than about 2 pips an hour.
img_12920_r1.png
img_12920_r1.png (82.07 KiB) Viewed 244 times
On the EMA point above, an exponential average of the same length has the same 24.5 bar lag on a steady trend. It only behaves better around spikes, because old closes fade out instead of dropping off all at once.

Has anyone tried scaling targets by the slope of the average rather than by the distance from it? It seems a cleaner read on whether the trend has room left.
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Moving Averages Lag by Design, So Use Them for Context, Not Timing

Post by Shadow Trader »

One thing worth checking before settling on a period is how much history each choice covers. The 200 on the hourly timeframe and the 50 on the daily sound like similar trend filters, but they look at very different stretches of time.

Forex trades about 24 hours a day, so 200 hourly bars is a bit over 8 trading days, under two weeks. The daily 50 covers about 10 weeks, so a pullback lasting a fortnight can put price under the first while it stays well above the second.

The two filters will therefore disagree for long spells, and on those days the side you trade depends on which line you picked. Counting the disagreement days over a few months is a quick test of how much the choice matters on your pair.

Disagreement is also information in itself. When the short filter says down and the long one says up, the market is often in a correction inside a bigger trend, which is where chop tends to show up on the lower timeframe.

A simple rule is to trade only when both agree, and to cut targets or sit out when they do not. Has anyone compared results on agreement days against the rest?
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Moving Averages Lag by Design, So Use Them for Context, Not Timing

Post by Shadow Trader »

Moving averages smooth price at the cost of delay. A short average, such as five periods, lags less than a long one, but it still lags. By the time a crossover signals, part of the move has already occurred.

For scalping, this delay matters because targets are small. If the average reacts after half of a five-pip move, little remains. Exponential averages reduce lag modestly, and weighted variants reduce it further, but none eliminates it.

Measuring the effective lag, by comparing the timing of average turns to price turns, quantifies the cost. Some traders use price relative to the average as a filter rather than a trigger, entering on pullbacks within an established direction. Others replace averages with indicators less affected by lag, such as raw price breakouts from short ranges. Whatever method is chosen, the delay should be accounted for in expectations. An indicator that confirms a move after most of it has passed provides comfort but little profit.
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

Re: Moving Averages Lag by Design, So Use Them for Context, Not Timing

Post by Fairman »

The point about old spikes leaving the window is something I'd never have noticed. I've seen crossovers that appeared for no reason in the middle of a quiet afternoon and assumed it was just noise. If a 50 period average loses a 40 pip release candle that's 50 bars old, the average drops by roughly 0.8 pips with nothing happening, and a short-period cross can flip on that alone.

Here's how I see it. A 50 SMA at 1.0842 with a big bar of 40 pips leaving the window, shifts about 0.8 pips lower. If price is 0.5 pips under the average, it crosses over and my EA says buy. The "signal" came from the bar that dropped off, not from new buying.

So I agree with using an EMA, at least for the long period. The decay is gradual, so it avoids that cliff. For the 200 EMA as a context filter, I look only at whether price is above or below and the slope over the last hour, nothing more.

On a 0.4 lot trade with a 10 pip stop, one artifact signal costs 40 dollars, and my old EA did that about twice a week.

Do you use a different smoothing on the shorter averages, like a weighted one? And would you ever filter signals to avoid the fifty bars after a big release?
It’s Fairman :geek:
Post Reply