CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage. Trade only with money you can afford to lose.
Open Exness Account →
Measured data

Sri Lanka — Execution - What to Check After a Fill

Compare the price obtained with the price shown when the order was sent, note the size and the hour, then judge it against measured fills of a comparable size rather than against a remembered one.

Open Exness Account →

Ordered walkthroughs  ·  What to prepare first  ·  What the screen should show

Execution figures are a post-fill check, not a pre-trade one. After an order fills, compare the price you got with the price you clicked, and read the difference as slippage rather than as an error. The measured figures here show what that difference looked like when real market orders were placed on the platform feed, broken down by order size, so a fill can be judged against something other than a feeling.

Why this is measured with trades

Execution quality is one of the account features Exness highlights, and it cannot be judged from quotes alone — only a real order shows the latency, the fill price and whether the platform rejects size. The probe opens and immediately closes positions of increasing size and records what actually happened.

Execution speed and fill quality vary with market conditions, liquidity and position size.

Measured round-trips by instrument and size

InstrumentLot sizeAvg executionSlowest fillAvg slippage (signed)Better / zero / worse fillsRejects
EUR/USD0.01151 ms187 ms-0.3 pts1 / 2 / 00
EUR/USD0.1151 ms172 ms-0.3 pts1 / 2 / 00
EUR/USD1146 ms172 ms-0.3 pts1 / 2 / 00
GBP/USD0.01141 ms156 ms+0.7 pts0 / 1 / 20
GBP/USD0.1130 ms140 ms+0.0 pts0 / 3 / 00
GBP/USD1135 ms156 ms+0.3 pts0 / 2 / 10
XAU/USD (Gold)0.01141 ms172 ms+0.0 pts0 / 3 / 00
XAU/USD (Gold)0.1151 ms172 ms+80.0 pts1 / 1 / 10
XAU/USD (Gold)1130 ms141 ms-72.3 pts2 / 1 / 00

Across 27 measured round-trips the average fill took 130–151 ms depending on instrument and size, with 0 rejected orders in total. Negative slippage means the fill was better than the quoted price at the moment the order was sent.

Slippage in points, signed: negative = filled better than quoted, positive = worse. ‘Rejects’ counts orders the platform refused at that size.

Where the execution figures come from

  • Real market orders (buy, then immediate close) placed in an Exness MetaTrader 5 terminal.
  • Latency timed in-terminal from order send to broker confirmation.
  • Sizes stepped 0.01 → 1.00 lot to expose size-dependent slippage.
  • Fills depend on market liquidity, account and conditions, and can differ.

The figures come from real market orders placed on the platform feed at the time of capture, broken down by order size. Compare your own fills against the same size band and the same kind of hour. Delays and slippage may occur, and no execution speed or precision is guaranteed.

Open Exness Account →

What a single fill can and cannot tell you

One fill is a sample of one. It can confirm that the order path works end to end - order sent, position opened, history recorded - which is the thing worth confirming on a new account or a new platform. It cannot describe execution behaviour on its own.

That is why the sequence here is to check the mechanics on the first fill and to judge behaviour only across several, at comparable sizes and comparable hours. The measured figures below serve as the reference for that comparison rather than as a promise about the next order.

Reading the figures without over-reading them

The numbers come from real market orders placed on the platform feed and are broken down by order size. A small sample is labelled as such, and a small sample should move an opinion only slightly.

Delays and slippage may occur, and no execution speed or precision is guaranteed. Read the figures as a description of what was measured at the time of capture, alongside your own fills, rather than as a specification the platform is committed to.

Keeping your own record

Two columns are enough: the price shown when the order was sent and the price it filled at, plus the size and the server hour. After a handful of entries the pattern in your own fills is more useful than any published table, because it covers the instruments and the hours you actually trade.

That record is also what turns a complaint into a question support can answer. A single surprising fill is hard to discuss; five fills with sizes and times attached is a specific thing to ask about.

Checking a fill after the order

  1. Read the fill price in the order history against the price shown when the order was sent. The difference is slippage.
  2. Note the size of the order. Slippage behaves differently by order size, and comparing a large fill against a small one proves nothing.
  3. Note the moment. A fill during a release or at the daily rollover is not comparable with one from a quiet hour.
  4. Compare against the measured figures below for the same size band, rather than against a remembered fill from another day.
  5. If a rejection came back instead of a fill, treat it as a margin or market-hours question first and re-check both before re-sending.
  6. Keep a short record of your own fills. Two or three of them are worth more than any table when a pattern is being judged.

Delays and slippage may occur. No guarantee of execution speed or precision.

Questions that come up mid-way

When is an execution check run?
After a fill. Compare the price obtained with the price shown when the order was sent, and record the order size and the hour so the comparison has context.
Is one fill enough to judge execution?
No. One fill confirms the order path works. Judging behaviour needs several fills at comparable sizes and comparable hours.
The order was rejected rather than filled. What next?
Check free margin and the trading session for that instrument before re-sending. Both produce a rejection that looks like an execution problem but is not one.
What do the measured figures represent?
Real market orders placed on the platform feed at the time of capture, broken down by order size. Delays and slippage may occur, and no execution speed or precision is guaranteed.

Where this walkthrough goes next