Direct answer
Execution quality for cTrader-based forex execution is best assessed with observable, numeric execution outcomes and with checks for how those outcomes are produced. Focus on consistent measurements (e.g., fill rate, slippage, and how orders are filled), then compare results across comparable order types and market conditions. Also assume evidence limits: historical statements about execution cannot guarantee future behavior, and broker execution can change with market liquidity, volatility, and infrastructure.
Mechanics: what “execution quality” means
Execution quality describes how closely an order’s actual fill matches what you requested in time and price, and how reliably the platform can complete orders.
To assess it, distinguish stable mechanics from variable conditions:
- Stable mechanics are features of order handling, matching logic, and reporting (for example, whether market orders are filled immediately at available liquidity and how partial fills are recorded).
- Variable conditions are driven by the market and environment, such as spread widening, reduced depth, and fast price changes.
A practical definition that can be measured is: how different actual fills are from the reference you choose, and how often the platform can complete your request as intended.
Evidence and examples: which factors to measure
Use a consistent observation method, then compute summary statistics.
- Fill rate (completion reliability)
- For a defined time window and order type, measure the fraction of orders that are fully filled, partially filled, or not filled.
- Example assumption: if you submit 100 market orders of a fixed size during active hours, fill rate can be expressed as filled orders / submitted orders.
- Slippage (price deviation)
- Choose a clear reference price for each order (commonly the displayed quote at submission time, or another documented reference used by your testing setup).
- Compute slippage as: actual fill price − reference price (sign matters for direction).
- Summarize with mean, median, and distribution tails (worst cases). Tail behavior matters more during fast moves.
- Latency and responsiveness (time alignment)
- Execution quality can degrade when the delay between submission and fill is inconsistent.
- Measure time-to-fill for each order (from your client timestamp to the fill event timestamp as available), then summarize variability. High variability can increase slippage.
- Cost reality (all-in trading cost)
- Spreads alone are incomplete if there are commissions or other execution-related charges.
- Define all-in cost per trade as the effective spread plus commissions (and any documented fees), then compare it to your expected cost under normal liquidity.
- Order-type behavior
- Compare outcomes for different order types you can test in a controlled way (e.g., market vs limit) under similar conditions.
- Look for systematic patterns such as consistent partial fills for one type.
Limitations and risks: at least one material failure mode
A major failure mode is misleading conclusions caused by inconsistent measurement and shifting market conditions. If you compare execution stats from different volatility regimes, or use changing test sizes, your results may reflect market depth changes rather than execution quality.
Other limitations you should account for:
- Historical relationships don’t imply future results: execution can change when liquidity providers, volatility, or infrastructure changes.
- Outcome metrics can be incomplete: some brokers or platforms may handle orders in ways that are not fully visible to you (for example, how prices are sourced or how internal routing affects fills).
- Tail risk can dominate: averages can look acceptable while rare events create large slippage.
Verification and next question
To verify your assessment, replicate measurements using the same reference definitions and comparable test conditions, then check whether conclusions remain stable across multiple periods. When you see a difference, separate whether it is explained by market conditions (wider spreads, lower depth) or by execution behavior (higher slippage variance, lower fill rate, more partial fills).
A useful next question is: which reference price and timestamps define slippage and latency in your own testing method, and are they consistent across the periods you compare?