Connecting both Wi-Fi and Ethernet does not, by itself, add their advertised speeds together. The computer still needs to choose a path for traffic. Route preference, failover and deliberately configured aggregation are different concepts; two connected interface icons are not evidence of a bonded internet connection.
Imagine a laptop plugged into Ethernet while Wi-Fi stays enabled. A faster speed-test result after plugging in the cable may be useful, but it does not demonstrate that both connections contributed to that transfer. First establish which condition you changed and which network the application could reach.
Two links do not create one larger test result
Each interface has its own connection and configuration. A normal application session must reach its destination through the routes available to the operating system. You cannot calculate a usable total simply by adding a Wi-Fi link-rate display to an Ethernet link-rate display.
Those displays are not measurements of separate internet subscriptions either. Both interfaces may ultimately reach the same household router and the same broadband service. Our Wi-Fi versus Ethernet guide explains the comparison between access methods; the question here is what happens when they coexist.
How Windows expresses preference
Microsoft’s interface-order documentation explains route and interface metrics: the combined metric participates in selecting a preferred route. It describes a preference mechanism, not a promise to combine two interfaces’ throughput.
Do not copy an example metric from a server document as a universal optimisation for a home PC. A computer may have VPN routes, work resources or virtual adapters that make its configuration more complicated than two simple choices. The useful first step is to observe and document the existing arrangement, not force a route before understanding it.
How macOS exposes service order
Apple’s network service-order guide describes the order in which active services are tried and provides the Network settings → Set Service Order workflow. It also identifies a special priority boundary for VPN connections. Again, preference is not an instruction to add Wi-Fi and Ethernet rates.
Record the original order if you inspect or deliberately change it. On a managed Mac, ask the administrator about expected behaviour rather than overriding a service required for work. Do not infer the current application’s route solely from which icon looks active.
A comparison that answers a smaller question
You can investigate whether one connection arrangement works better for your task without proving every routing detail. Choose a quiet period and keep the computer, application and remote service the same.
- Write down the topology. Identify where Wi-Fi and Ethernet connect, including whether they reach the same router and internet service.
- Record the original state. Include VPN use, available interfaces and the symptom you are investigating.
- Compare one interface at a time when practical. Use supported controls and confirm that the intended connection actually works before judging its performance.
- Run the same ordinary task. Note completion, delay or failure. If you run a speed test, do so sequentially with the same service and label each condition.
- Restore the intended setup. Keep the result and any deliberate configuration choice documented.
Do not disconnect an interface carrying a remote-support session or an important work connection without a recovery plan. If the setup cannot safely be simplified, report that limit instead of making a confident claim about which interface “won.”
What the results do and do not mean
If one arrangement consistently helps the affected task, it is reasonable to prefer it for that use. That observation does not certify the other interface as defective, and it does not establish that a speed gain equals the sum of two links.
If local access changes while internet access remains similar, document that distinction. A file server on one network and a website on the internet are different destinations. For a local-transfer question, the NAS home-server guide helps separate local serving from remote access.
If the result is unexpectedly low on Ethernet alone, inspect that connection separately using the Ethernet troubleshooting guide. Keeping Wi-Fi enabled to hide the symptom may make it harder to reproduce, even if it restores immediate usability.
When genuine aggregation is the question
Some specialised systems deliberately distribute or aggregate traffic. Their requirements depend on the technology, endpoints and network equipment. That is a different project from leaving two ordinary laptop interfaces connected, and it should be assessed using the exact product’s documentation.
Before buying anything, define the goal: additional capacity for one transfer, resilience during an outage, or separating different devices’ traffic. Do not purchase an adapter merely because a link-rate sum looks attractive. A support request with the topology, intended goal and single-interface comparison gives someone enough information to distinguish those needs.
Also record whether both interfaces reach networks you are authorised to connect together. A home Wi-Fi network and a separately managed work connection are not automatically appropriate candidates for experimental aggregation or bridging. Ask the responsible administrator about that design.