by Tommy N. Updated Apr 24, 2026
Running an ethernet speed test is the fastest way to find out whether your wired connection is delivering the performance your internet plan promises. Unlike Wi-Fi, a direct cable connection eliminates wireless interference — so if your ethernet speeds still disappoint, the problem almost certainly lies with your router, ISP, or the cable itself.
In this guide you will learn exactly how to test your wired connection speed, what the results mean, and how to diagnose common causes of slow ethernet performance. Whether you are dealing with slow network speeds across the board or just want to confirm your gigabit plan is actually delivering gigabit rates, understanding your ethernet baseline is the essential first step — and it pairs naturally with checking your IP address configuration to rule out network-layer problems.
An ethernet speed test measures how quickly data travels between your device and a remote server over your wired connection. The test sends and receives packets of data in rapid succession, then calculates your download speed (data coming in), upload speed (data going out), and latency (the round-trip delay, measured in milliseconds). These three numbers together paint a complete picture of your wired connection quality.
The key difference between testing over ethernet versus Wi-Fi is consistency. Wireless connections fluctuate constantly due to signal interference, distance from the router, and competing devices on the same channel. Ethernet removes all of those variables. When you plug a cable directly into your router or modem and run a speed test, you get a clean measurement of what your ISP is actually delivering to your home — no wireless noise to muddy the results.
Speed test tools work by connecting to a nearby server (chosen to minimize latency) and performing a series of timed data transfers. The download test saturates your connection by pulling as much data as possible in a fixed window, while the upload test does the reverse. Because the results depend on the test server's own capacity and distance, it is worth running tests to multiple servers and averaging the results for the most accurate baseline.
A few technical factors shape what your ethernet speed test can actually measure. Your network interface card (NIC) has a maximum link speed — typically 100 Mbps, 1 Gbps, or 2.5 Gbps on modern hardware. Your ethernet cable category also imposes a ceiling: a Cat 5e cable supports up to 1 Gbps, while Cat 6 and above handle 10 Gbps over short runs. If either the NIC or the cable is the limiting factor, you will never see your full ISP-rated speeds no matter how many tests you run.
Follow these steps in order to get an accurate, reproducible wired speed measurement.
The cable you use matters as much as the connection itself. Here is how common ethernet cable standards compare for home and small-office use.
| Cable Category | Max Speed | Max Bandwidth | Best Use Case |
|---|---|---|---|
| Cat 5 | 100 Mbps | 100 MHz | Legacy only; not recommended |
| Cat 5e | 1 Gbps | 100 MHz | Basic home & office networking |
| Cat 6 | 10 Gbps (up to 55 m) | 250 MHz | Modern home, NAS, gaming PCs |
| Cat 6A | 10 Gbps (up to 100 m) | 500 MHz | Structured wiring, server rooms |
| Cat 8 | 25–40 Gbps | 2000 MHz | Data centers, future-proofing |
Before running any speed test, right-click your ethernet adapter in Windows Device Manager (or check System Information › Network on macOS) and confirm the link speed matches your cable and NIC rating — for example, "1.0 Gbps" for a Gigabit connection. If it shows 100 Mbps on a Gigabit cable, a damaged cable or a faulty port is already capping your speeds, and no amount of testing will improve the number until you address the physical layer first.
If your ethernet speed test results are significantly lower than your plan speed, the cause is usually one of a handful of well-understood problems. Start by ruling out the simplest physical issues before moving to software or router configuration, and always retest after each change so you know exactly which fix made the difference.
Cable quality and length are the most commonly overlooked culprits. A cheap or old Cat 5 cable between your device and router will hard-cap your speed at 100 Mbps even if everything else on your network is Gigabit-capable. Similarly, cables longer than 100 meters (328 feet) exceed the spec limit for ethernet and will cause packet loss and retransmissions that show up as degraded speed test results. If your cable runs through walls, check for kinks, staples driven through the sheath, or sharp bends at wall plates — all of which damage the internal conductors over time.
Router and modem issues are the next thing to check. A router with outdated firmware may have bugs affecting throughput, and a modem that has been running for months without a restart can develop memory leaks that degrade performance. Try a router reset or at minimum a power cycle (unplug for 30 seconds, then plug back in) before digging further. Also verify that your router's WAN port negotiated the correct link speed with your modem — some older routers default to 100 Mbps on their WAN interface even when Gigabit is available.
Pro Tip: Use our ping test tool alongside your speed test to check for packet loss and jitter. High packet loss (above 1%) on a wired connection almost always points to a bad cable, a failing NIC, or a congested port on your router — information that a raw speed number alone will not reveal.
This almost always means your ethernet cable, NIC, or router port is limiting your wired connection below its potential. Check that your cable is at least Cat 5e, confirm your NIC is showing a Gigabit link speed in device settings, and try a different LAN port on the router. It is also worth checking your router firmware for any known throughput bugs affecting wired ports.
For most home broadband connections, a ping below 20 ms to a nearby server is excellent, 20–50 ms is good for general use and gaming, and anything above 100 ms will noticeably affect real-time applications like video calls and online gaming. Wired connections consistently outperform Wi-Fi for latency because there is no wireless contention or retry overhead involved.
To test local network throughput without involving your ISP, use a free tool like iperf3 — run it as a server on one machine and as a client on the other, and it will measure the raw transfer rate between them. This method is ideal for diagnosing whether a slow NAS transfer or file share is a cable problem, a switch bottleneck, or a disk I/O limitation on the destination machine.
Ethernet cables are specified to work reliably up to 100 meters (328 feet) for standard Cat 5e through Cat 6A. Within that limit, cable length has a negligible effect on throughput for typical home connections. Beyond 100 meters, signal attenuation increases significantly, causing packet errors and retransmissions that reduce effective throughput — you would need a network switch or an ethernet extender to bridge longer distances cleanly.
Yes, absolutely. Budget routers often have slower CPUs that cannot process Gigabit traffic at line rate, especially when NAT, firewall inspection, or QoS features are enabled. If your speed test from a device plugged directly into your modem (bypassing the router) returns full speeds but the same test through the router does not, the router itself is the bottleneck. Updating firmware or upgrading to a router with a more capable processor will resolve the issue.
No — always disconnect your VPN before running a speed test if you want to measure your raw ISP connection. VPN encryption adds CPU overhead and routes your traffic through an additional server, which consistently reduces both throughput and latency. If you want to measure your VPN-connected speeds specifically, run one test with the VPN on and one with it off to see exactly how much overhead the VPN service introduces.
For authoritative networking standards and specifications, refer to the Internet Assigned Numbers Authority (IANA) or IETF RFC documents.
 |
 |
 |
 |
About Tommy N.
Tommy is the founder of RouterHax and a network engineer with over ten years of experience in home and enterprise networking. He has configured and troubleshot networks ranging from simple home setups to multi-site enterprise deployments, with deep hands-on experience in router configuration, WiFi optimization, and network security. At RouterHax, he oversees editorial direction and covers home networking guides, mesh WiFi system reviews, and practical troubleshooting resources for everyday users.
Promotion for FREE Gifts. Moreover, Free Items here. Disable Ad Blocker to get them all.
Once done, hit any button as below
|
|
|
|
