Get the Guide See Current Sale

The Windows Default That Delays Every Order to Your Broker

Why are my orders slow when my speed test passes?

Because a speed test barely tests upload. A Windows setting called Large Send Offload hands packet-splitting to your network adapter, and on cheap adapters it does that job badly — delaying everything leaving your machine. Orders go out. Speed tests do not notice.

Key takeaways

  • A speed test is almost entirely a download test. It pushes a large block down, sends a brief burst back up, and finishes before a transmit-side fault has a chance to show.
  • That is why the line can be perfect, the phone on the same network can be fine, and the trading machine still stumbles on the way out.
  • Large Send Offload is the usual culprit. Windows turns it on by default. It moves the work of splitting data into packets from the processor to the network adapter.
  • On a quality adapter that is a sensible trade. On the cheap adapter built into most consumer motherboards, it introduces delay on exactly the traffic that matters — outbound.
  • Disable LSO in the adapter's advanced properties. It is free, reversible and takes a minute.
  • Leave RSS alone. Receive Side Scaling helps and turning it off makes things worse. TCP Checksum Offload is worth testing; RSS is not.
  • The root cause is usually the adapter itself. Settings can work around weak hardware only so far — at some point the network card is the problem.

Picture this: you fire an order to your broker, and it stumbles out the door. Meanwhile, your speed test comes back clean, big download numbers, green lights everywhere. Your phone sitting two feet away uploads a photo to the cloud in seconds, but your trading PC chokes every time you submit an order ticket. Same router. Same network. Same house. Either the laws of physics took the day off, or something's lying to you. And it is not your internet provider. It is your speed test.

This exact scenario played out in a real support call we handled this week. A trader called us completely baffled by his sluggish uploads. His phone flew. His Ookla speed test passed a dozen times in a row. His internet company swore the line was perfect. Here is the thing: they were both telling the truth. The line was fine. The phone was fine. The problem was buried deep inside his trading computer in a setting that Windows quietly turns on by default. And a standard speed test will never, ever catch it.

Why Speed Tests Lie to Traders

Speed tests have a blind spot: they are almost entirely a download test. The way a tool like Ookla works is simple: it slams a big chunk of data down to your computer for a few seconds, then sends a tiny, short burst back up. That upload phase is brief. It is forgiving. It is over before anything has a chance to break down.

If your trading computer has a problem on the transmit side, meaning on the way out, a speed test will sail right past it and hand you a passing grade. It is like a mechanic who only test drives your car downhill. Of course it runs great. He never asked it to climb anything.

For a trader, the transmit side is the side that matters most. Every order you fire, every cancel, every modify, that is your trading computer talking out to your broker. If your outbound path is broken, your speed test can show a beautiful 400 Mbps download all day long while your live orders limp out the door half a second late. And half a second late at the market open is a fill you did not want, or a fill you never got.

The Hidden Culprit: Large Send Offload (LSO)

The setting responsible for this problem is called Large Send Offload, or LSO. Here is what it does in plain English: when your computer sends data, that data gets chopped into small numbered packets before it goes out. LSO says, do not make the processor do that work; hand it off to the network card instead. In theory, it is a great idea. Less CPU overhead. The problem is when the network card is bad at the job.

A lot of cheap onboard network chips, commonly branded as Realtek or Killer, have buggy LSO implementations. Instead of cleanly segmenting your outbound data, they mangle it into garbage segments and shove them out the door. Your download stays perfectly fine because LSO only touches outgoing traffic. That is precisely why this customer saw broken uploads while everything else looked spotless.

The Fix: How to Disable LSO on Your Trading Computer

Follow these steps exactly to disable Large Send Offload on your Windows trading computer:

  1. Click the Start button in the bottom-left corner of your screen.
  2. Type Device Manager and click it when it appears.
  3. Find Network adapters in the list and click the arrow to expand it.
  4. Right-click on your network card (it will say something like Realtek, Killer, or Intel) and choose Properties.
  5. Click the Advanced tab at the top.
  6. Scroll through the list and find Large Send Offload v2 (IPv4) — set the value to Disabled.
  7. Find Large Send Offload v2 (IPv6) — set that to Disabled as well.
  8. Click OK.

After making these changes, do not just run another Ookla test. Actually test a real sustained upload. Send a large file to Google Drive, upload a screen recording to Loom, something that pushes a long outbound stream. That is the only honest way to confirm the fix worked.

What About TCP Checksum Offload and RSS? Do Not Touch RSS.

Search this problem online, and you will find plenty of videos telling you to disable three things at once: LSO, TCP Checksum Offload, and something called RSS (Receive Side Scaling). That spray-and-pray approach is lazy, and one of those recommendations can actually hurt your trading performance.

    LSO — yes, that's the real fix about 90% of the time. TCP checksum offload — low stakes; if disabling LSO alone doesn't fully do it, you can try turning that one off too; there's no real harm. But RSS? Leave it alone. Here's the thing: RSS is a receive-side feature. The name literally says it: receive-side scaling. It has nothing to do with sending data, so it cannot logically be causing your upload problem.

    Now picture your trading setup at the open: full order book, tick data, market data pouring in like a fire hose, and you just funneled all of it onto one lonely core while the rest sit idle. You just kneecapped your own market data feed trying to fix a problem you never had. Leave RSS enabled. There is no debate on this one.

    The Real Root Cause: Cheap Hardware in Your Day Trading Setup

    Toggling settings forever is not a sustainable way to run a professional trading operation. The root cause of this whole mess almost always comes down to one thing: a cheap onboard motherboard network chip running buggy default behavior.

    There is a significant difference between a consumer tower assembled with the lowest-cost components a manufacturer could source and a trading computer built specifically for how traders actually use hardware. A quality network card with a mature, well-tested implementation rarely throws this kind of tantrum in the first place.

    Back in my day, old-school traders had one phone line and a single screen, and somehow we got our orders in. Now this guy's got a fiber optic connection screaming into the house, six monitors, but a $400 tower and a 40-cent network chip in there choking on its own homework. That's the whole problem. The fast part of the setup is fine. The cheap part is sabotaging it.

    When Settings Are Not Enough: Know When the Machine Is the Problem

    Now, before we go any further, let's find out if your machine can even keep up with your orders in the first place. Run the free CPU benchmark test specifically for traders, and it spits back plain numbers that tell you whether your hardware is fast enough to fire orders cleanly or whether it's quietly costing you your fills. Run it tonight before the market opens tomorrow, and in 5 minutes you'll know for certain whether your computer is the thing standing between you and your fills.

    Build a Trading Computer That Does Not Sabotage Your Execution

    And look, if you've gone through every one of these steps and your orders are still limping out the door, that's not a setting anymore; that's the machine itself telling you it cut a corner that's now costing you money on every fill.

    That's the exact phone call I take every single day from traders who are flat-out done fighting their own hardware. Pick up the phone right now and give my team at EZ Trading Computers a call at 800-387-5250. Tell us what you trade and how many screens you run, and we'll spec you a machine with a quality network card built in from the ground up, so a 40-cent chip never costs you another execution.

    You're a great trader. You shouldn't have to be a network engineer too. That part's our job. And if you're not ready to call yet, no problem; at least don't walk into a $3,000 purchase blind. Grab my free Complete Guide to Trading Computers.

    May the trend be with you.

    Frequently Asked Questions

    What is Large Send Offload and should I disable it?

    It is a Windows feature that hands the job of breaking data into network packets from your processor to your network adapter, to save processor time. On server-grade hardware it works well. On the inexpensive adapter integrated into most consumer motherboards it introduces delay on outbound traffic, which is precisely the traffic carrying your orders. For a trading machine, disable it: open Device Manager, find your network adapter, open Properties, then Advanced, and set Large Send Offload to Disabled.

    Why does my speed test look fine when my trading is slow?

    Because the test and the problem measure different directions. A speed test spends most of its time downloading and only a moment uploading, and that upload burst is too brief and too forgiving to expose a transmit-side fault. Your orders are outbound. A test that barely exercises outbound will pass while every order you send is being delayed.

    Should I disable TCP Checksum Offload?

    It is worth testing, unlike Large Send Offload which is worth disabling outright on consumer hardware. Turn it off, use the machine for a session, and see whether order entry feels different. If it makes no difference, turn it back on. Change one setting at a time so you know which one did what.

    What is RSS and should I turn it off?

    Receive Side Scaling spreads incoming network traffic across several processor cores instead of loading one. For a trading machine taking in continuous market data, that is exactly what you want. Leave it enabled. It appears on lists of settings to disable, and following that advice makes a trading computer worse, not better.

    Can a bad network adapter really affect trading?

    Yes, and it is one of the most overlooked components in a trading machine. The adapter integrated into a budget motherboard is built to a price, and it shows under sustained load rather than in a quick test. Settings can work around a weak adapter to a point. Past that point the fix is better hardware, not more tuning.

    Eddie Z
    Eddie Z
    Founder, EZ Trading Computers & EZBreakouts
    Eddie Z is a full-time day trader who has spent 39 years on Wall Street, starting on the floor of the NYMEX in 1987. Since 2010 he has built more than 20,000 computers for traders — only for traders. Almost everyone else in this business came from the technology side and later discovered traders. Eddie came the other way round, and still has his own money on the line at 9:30 every morning.