What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The most useful home test is an end-to-end wired LAN throughput test. Connect two capable devices through the exact Ethernet path you want to check, keep both devices off Wi-Fi, and run iPerf3. Start iperf3 -s on one device, run iperf3 -c SERVER_IP -t 20 from the other, repeat in reverse with -R, and use several parallel streams with -P 4 or -P 5 when a single stream does not fill a fast link.
This measures the complete selected path under repeatable conditions. To determine whether the cable is the limiting variable, first record negotiated speed and duplex, then repeat the same test with a short known-good cable and alternate ports. An Internet speed test cannot isolate your Ethernet cable because it also measures the router, WAN, ISP, and remote server.
As an Amazon Associate I earn from qualifying purchases.
What a cable-speed test can—and cannot—prove
An Ethernet cable has no independent speed readout. A cable is one part of a link that also includes two network-interface controllers, connectors or wall jacks, switch ports, drivers, operating-system networking, and the traffic-generation software. The practical question is therefore not “What speed is printed on the jacket?” but “How quickly can this complete path move data between these two endpoints under controlled conditions?”
Recommended Free Tools
For a home or small-office diagnosis, iPerf3 is the most useful first instrument. It sends sustained traffic between two local devices and reports throughput, retransmissions, and other run details. Because both endpoints are on your LAN, the Internet and your ISP are outside the measurement.
#1 Best Overall
- Multifunctional Network Cable Tester: TESMEN TLP-123A Supports RJ45 and RJ11, enabling rapid detection of line connectivity, short circuits, open circuits, miswiring, and cable shielding status. An essential tool for troubleshooting line faults and network maintenance, it effectively boosts your work efficiency
- Convenient and Efficient: Featuring one-button operation and a test speed adjustment gear on the main control unit for enhanced flexibility. Clear LED indicators provide intuitive test result displays, making it easy for both professionals and home users to operate
- Portable and Durable: Compact and lightweight design for easy portability. Constructed with high-quality plastic housing for robust structure, ensuring both durability and stability. Ideal for home wiring, IT equipment setup, electrical maintenance, and LAN DIY projects
- Detachable design: The main control unit and remote unit can be separated and used independently, allowing you to test both ends of long cables. This makes it ideal for wall-mounted ports, long-distance cabling, or structured cabling systems, perfect for homes, offices, or professional IT environments
- What you will get: 1 * TLP-123A Network Cable Tester, 1 * user manual, 2 * AAA batteries
An Internet speed test answers a different question: how quickly one device can reach a remote test server through the local network, router, access connection, ISP, and wider Internet. A slow result may be caused by any of those components, so it cannot identify a defective patch lead or wall run.
Choose exactly what you are testing
One patch cable
Connect the two test devices through that cable and nothing else between them except the necessary ports or a small switch. This is the cleanest test of a removable lead, but the NICs and ports still influence the result.
A wall run or permanent link
Include both wall outlets, their patch leads, and every termination you want to evaluate. Do not replace only the questionable section during the first run; otherwise you may accidentally test a different path.
The complete route to a device
If the real problem is a desktop connected through a wall jack, patch panel, and switch, reproduce that route exactly. Record the switch model and port, because a switch port can negotiate at a lower rate even when the cable itself is sound.
Prepare the endpoints and record negotiation
- Use two wired endpoints. Laptops, desktops, or servers must both use Ethernet for every run. Disable Wi-Fi or disconnect it so the operating system cannot select a wireless route.
- Check capabilities. Confirm that both NICs or USB Ethernet adapters, the switch ports, and their drivers support the rate you are trying to verify. A 100-Mb/s adapter cannot demonstrate gigabit performance, regardless of the cable category.
- Stop competing traffic. Pause cloud synchronization, game downloads, backups, video uploads, and virtual-machine traffic. Keep CPU-heavy jobs off the two test devices.
- Record negotiated speed and duplex at both ends. Use the operating system’s wired-link status, the switch management interface, or the port LEDs and documentation. Cisco describes auto-negotiation as the exchange of speed and duplex capabilities between link partners and recommends leaving it enabled on compliant devices.
Negotiation is an observation, not a complete cable verdict. A link that negotiates at 100 Mb/s when the hardware is expected to run at 1 Gb/s is an important isolation clue, but you still need to inspect both ends, patch leads, terminations, port settings, and duplex agreement.
Run the iPerf3 test step by step
1. Install or open iPerf3 on both devices
Use the current iPerf3 package available for each operating system, and make sure the firewall allows the test connection on the local network. The commands below assume the executable is available as iperf3.
2. Start the server
On endpoint A, open a terminal and run:
iperf3 -sLeave this terminal open. Note endpoint A’s wired IPv4 address; call it SERVER_IP in the examples below. Use the address assigned to the Ethernet interface, not a Wi-Fi address or a public Internet address.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #2
- VERSATILE CABLE TESTING: Cable tester for data (RJ45) terminated cables and patch cords, ensuring comprehensive testing capabilities
- LARGE BACKLIT LCD: Backlit LCD display enables easy reading of pin-to-pin wiremap results, even in low-lit areas
- COMPREHENSIVE FAULT DETECTION: Test for Open, Short, Miswire, Split-Pair faults, Cross-over, and Shield, providing thorough fault detection
- INTUITIVE USER INTERFACE: User-friendly interface with three buttons and simple, easy-to-identify test responses, ensuring a smooth testing experience
- MULTIPLE TONE GENERATOR STYLES: Tone on a single wire, wire pair, or all 8 conductor wires using the multiple style tone generator (solid/warble); requires probe Cat. No. VDV500-123 (sold separately)
3. Run a 20-second client test
On endpoint B, run:
iperf3 -c SERVER_IP -t 20The client connects to endpoint A and sends traffic for 20 seconds. Save the reported average throughput, retransmission count, and any error or warning lines. A single short run is only a snapshot, so keep the conditions unchanged for repeat tests.
4. Test the reverse direction
Run the same test with the server still on endpoint A:
iperf3 -c SERVER_IP -t 20 -RThe -R option makes endpoint A send toward endpoint B. Comparing both directions can reveal an endpoint, driver, duplex, or port problem that a one-way test hides.
5. Add parallel streams when one stream underfills the link
For faster Ethernet connections, a single TCP stream may not generate enough traffic to reach the path’s capacity. Intel notes that multiple application sessions can be necessary on high-bandwidth links. Repeat the forward and reverse tests with four streams:
iperf3 -c SERVER_IP -t 20 -P 4If the result still does not fill the negotiated link, try five streams:
iperf3 -c SERVER_IP -t 20 -P 5Keep the stream count consistent when comparing cables. Do not treat a higher result from a different command as proof that the cable changed; it may simply show that the original test design was the bottleneck.
6. Repeat runs and save the conditions
Run each mode more than once and record the date, endpoints, interface names, negotiated speed and duplex, switch port, cable or path, stream count, duration, average throughput, retransmissions, and errors. Consistent results are more informative than the best result from a single run.
Rank #3
- VERSATILE CABLE TESTING: Cable tester tests voice (RJ11/12), data (RJ45), and video (coax F-connector) terminated cables, providing clear results for comprehensive testing on unenergized Ethernet cables (not designed to test PoE)
- EXTENDED CABLE LENGTH MEASUREMENT: Measure cable length up to 2000 feet (610 m), allowing for precise cable length determination
- COMPREHENSIVE FAULT DETECTION: Test for Open, Short, Miswire, or Split-Pair faults, ensuring thorough fault detection and identification
- BACKLIT LCD DISPLAY: Backlit LCD screen displays cable length, wiremap, cable ID, and test results, ensuring easy readability in various lighting conditions
- EFFICIENT CABLE TRACING: Trace cables, wire pairs, and individual conductor wires using the multiple style tone generator (requires analog probe Cat. No. VDV500-123, sold separately), simplifying cable tracing tasks
Use a known-good cable and alternate ports as controls
After the baseline, change one variable at a time. First replace only the cable under examination with a short, known-good cable of suitable category. Keep the endpoints, switch port, commands, duration, and stream count identical. Then restore the original cable and move both ends to different known-good ports if available.
| Controlled change | If throughput or negotiation improves | What remains possible |
|---|---|---|
| Replace only the cable | The original cable, plug, jack, or termination becomes more likely. | A marginal port or connector may have been disturbed during the swap. |
| Move one endpoint to another switch port | The original port, configuration, or port hardware becomes more likely. | The cable may still be marginal. |
| Swap the two endpoints | An endpoint NIC, driver, CPU, or adapter becomes more likely. | The path can still contain a physical fault affecting one direction. |
| Change nothing and repeat | Stable values support a repeatable result. | Congestion, power management, or background traffic may still vary over time. |
If the result changes only when the cable changes while every other condition stays fixed, the cable or its terminations is the leading suspect. If every cable performs poorly on one port or one computer, investigate that component before discarding more cables.
Interpret the result without inventing a pass/fail number
A 100-Mb/s negotiation on gigabit-capable hardware
This is an isolation clue, not a final diagnosis. Inspect both link partners, reseat or replace patch leads, check wall-jack and patch-panel terminations, try another switch port, and verify that speed and duplex are not being forced incorrectly. Cisco’s troubleshooting guidance specifically calls for checking both ends, trying another port or patch cable, and correcting speed or duplex mismatches.
Throughput is low but the negotiated rate looks right
Check the iPerf3 design before blaming the cable. A single stream can underfill a high-bandwidth connection; compare the one-stream result with -P 4 or -P 5. Also check CPU utilization, USB adapter limits, driver versions, switch configuration, and other traffic. A negotiated rate describes the link’s signaling mode, not the application throughput delivered by every workload.
Forward and reverse results differ sharply
Look for a duplex mismatch, a faulty or overloaded NIC, asymmetric driver behavior, a bad termination affecting one pair, or a switch-port issue. Repeat after swapping endpoints and ports. If the asymmetry follows one device, focus on that device; if it follows the physical path, inspect the cable and terminations.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Retransmissions or errors rise during the run
Record them rather than reporting only the average speed. Physical noise, damaged pairs, loose plugs, a marginal jack, duplex problems, driver faults, or congestion can all reduce useful throughput. Repeat with the known-good cable and a different port to separate path faults from endpoint or switch behavior.
The file copy is slower than iPerf3
A file transfer adds disk speed, filesystem behavior, CPU load, encryption, memory pressure, and the file-sharing protocol. Use iPerf3 to establish the in-memory network baseline first. A slower copy does not by itself prove that the Ethernet cable is slow.
Rank #4
- Multi-Function Network Cable Tester: Supports RJ45 (CAT5, CAT5e, CAT6, CAT6A, CAT7) and RJ11 telephone cables. Quickly detects continuity, short circuits, open wires, miswiring, and cable shielding status, ensuring your LAN or phone lines are correctly wired and ready to use.
- Fast/Slow Mode with LED Indicators: Switch between fast and slow scan speeds to identify wiring issues more precisely. LED lights on both master and remote units show wire order, making it easy to spot errors like open pairs or misaligned pins at a glance.
- Split-Type Design for Long-Distance Testing: Master and remote units can be detached and used separately, allowing you to test both ends of a long cable run, ideal for wall-mounted ports, long runs, or structured cabling. Perfect for home, office, or professional IT setups.
- Compact, Lightweight & Durable: Ergonomically designed with sturdy ABS housing, this pocket-sized tester is ideal for on-the-go network engineers, DIYers, and electricians. It’s your go-to toolkit for cable maintenance, upgrades, or new installations.
- Safe & Easy to Use: Simple one-button operation makes testing quick and hassle-free. LED indicators clearly show wiring status, while the G light instantly identifies shielded (FTP/STP) or unshielded (UTP) cables. Supports safe testing of telephone lines with typical voltages under 48-72V, ideal for both home and professional use.
What each testing method actually measures
| Method | Measures | Equipment | Reporting and repeatability | Best use |
|---|---|---|---|---|
| Internet speed test | End-to-end path from a device to a remote server, including WAN and ISP. | One device and an Internet connection. | Convenient, but results vary with remote-server load, ISP conditions, and other traffic. | Checking Internet service, not isolating a cable. |
| iPerf3 between two wired endpoints | Sustained traffic over the selected local path. | Two capable computers or servers and iPerf3. | Repeatable command-line runs with throughput, retransmissions, and error information. | Home and small-office troubleshooting. |
| Wiremap or continuity tester | Opens, shorts, crossed pairs, and some wiring faults. | Dedicated handheld tester and remote unit, depending on model. | Fast fault indication, but no sustained-throughput measurement. | Finding basic termination and pinout problems. |
| Qualification tester | Whether an installed link can support specified services or rates. | Dedicated qualification hardware. | Service-capability results rather than a computer-generated traffic average. | Checking installed links for technologies such as 100BASE-TX, VoIP, or Gigabit Ethernet. |
| Certification analyzer | Standards-based cabling measurements compared with TIA or ISO limits. | Calibrated certification analyzer and appropriate test adapters. | Formal pass/fail reports suitable for acceptance evidence. | Contractual, warranty, or structured-cabling certification work. |
Fluke Networks distinguishes qualification from certification: qualification determines whether an existing link can support certain speeds or technologies, while certification compares measured cabling performance with standards limits. Neither replaces an end-to-end iPerf3 test when the question is how a particular pair of computers performs in its normal software environment.
When a dedicated tester is worth using
Use a wiremap or continuity tester for basic wiring faults
If a new wall outlet never negotiates correctly, a wiremap tester can quickly identify an open pair, short, crossed pair, or incorrect termination. It cannot demonstrate sustained gigabit or faster throughput, so follow it with a qualification, certification, or iPerf3 test as appropriate.
Use qualification equipment for many installed links
When you need to check dozens of existing runs, dedicated qualification hardware is faster and more consistent than carrying two computers from outlet to outlet. Fluke describes qualification as determining whether cabling can support technologies such as 100BASE-TX, VoIP, and Gigabit Ethernet.
Use certification analysis for acceptance evidence
New structured-cabling installations, warranty claims, and contractual handovers may require standards-based reports rather than an informal throughput number. Certification analyzers compare measurements with TIA or ISO limits. Fluke states that its DSX series supports structured-cabling certification for deployments up to 40 Gigabit Ethernet; the applicable test limit and adapter depend on the cabling standard and installation.
Consider LinkIQ for mixed physical and network checks
Fluke’s LinkIQ qualifies 10BASE-T through 10GBASE-T and combines frequency-based measurements, wire mapping, ping, and nearest-switch diagnostics. It is useful when you need more than continuity but do not yet require a full certification report.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common outcomes
Both ends show 100 Mb/s instead of the expected 1 Gb/s
- Confirm that both NICs and the switch ports are gigabit-capable.
- Leave auto-negotiation enabled on compliant devices and remove inappropriate forced settings.
- Replace both short patch leads, not just the permanent run.
- Try a different switch port and inspect every jack or patch-panel termination.
- Run iPerf3 again, then compare with the known-good cable.
One computer reaches the expected result, the other does not
Swap the computers without changing the cable path. If the problem follows the computer, inspect its NIC, USB adapter, driver, CPU load, and power-management settings. If it remains with the path, continue with port and termination checks.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOne stream is slow but parallel streams are much faster
The result may reflect TCP or endpoint limitations rather than a cable fault. Use the same parallel-stream count for all cable comparisons, and report both the single-stream and parallel results so another reader can reproduce the test design.
Best Value
- EASY WIRE TRACING: Simple analog tone generator and wire tracing probe for open-ended, non-active low-voltage wires, making wire tracing hassle-free (<60v)
- OPTIMIZE SIGNAL FOR BEST RESULTS: Separate wires when possible and use proper grounding to improve tone detection and accuracy
- ALLIGATOR CLIPS INCLUDED: Comes with alligator clips for easy connection to unterminated wires, providing convenience during testing
- RJ45 TO RJ45 TEST CABLE: Includes an RJ45 to RJ45 test cable for seamless connectivity during testing and wire mapping
- COMPREHENSIVE WIRE MAPPING: Toner and probe together perform a pin-to-pin wire map test, ensuring thorough wire mapping and identification
The link repeatedly drops or renegotiates
Reseat connectors, replace detachable patch leads, inspect for damaged clips or bent contacts, try another port, and check switch logs if available. A cable that passes a brief continuity check can still be marginal under sustained traffic; repeat the iPerf3 run after each controlled change.
iPerf3 cannot connect
Verify that the server process is still running, the client is using the server’s wired IP address, both devices are on the same reachable LAN, and the local firewall permits iPerf3 traffic. Test basic reachability with a normal local ping, then return to the throughput test. A connection failure is not evidence that the cable has a particular speed.
How to report a meaningful result
Write the result as the throughput of a tested path under stated conditions, not as a universal capability of every cable carrying the same category label. Include:
Free tools Windows power users keep installed
One-click scans. No signup required.
- the exact path: patch cable, wall run, jacks, patch panel, and switch port;
- cable category marking and approximate length if known;
- endpoint models, NIC or USB-adapter models, operating systems, and driver versions when relevant;
- negotiated speed and duplex at both ends;
- iPerf3 command, duration, direction, and parallel-stream count;
- average throughput, retransmissions, and reported errors;
- background-traffic controls and whether Wi-Fi was disabled;
- results with the known-good cable and alternate ports.
This format lets you distinguish a physical-path observation from an endpoint limitation. It also prevents a one-time result from being presented as a laboratory certification.
Why Cat5e or Cat6 on the jacket is not a speed test
Category markings describe a cabling specification, not the throughput that every installation will deliver. The installed link may include lower-grade patch leads, poor terminations, damaged pairs, unsuitable connectors, a limited NIC, a 100-Mb/s switch port, or a configuration mismatch. Endpoint and switch capabilities therefore belong in every cable-speed diagnosis.
The published material used for this guide does not contain an independent laboratory measurement of your particular cable. Report what your two endpoints measured on the selected path and under the recorded conditions. Do not generalize that number to every cable with the same Cat5e or Cat6 label.
Practical testing sequence
- Define whether you are testing a patch lead, a permanent run, or the complete route.
- Connect two capable devices through that exact route and stop background traffic.
- Record negotiated speed and duplex at both ends with auto-negotiation configured appropriately.
- Run iPerf3 for 20 seconds in the forward direction.
- Repeat with
-R, then use-P 4or-P 5for faster links when needed. - Swap only the cable for a known-good one and repeat the identical commands.
- Try alternate switch ports and swap endpoints if the result remains unclear.
- Escalate to wiremap, qualification, or certification equipment when the required evidence exceeds an end-to-end software measurement.
An iPerf3 Blog LAN guide published May 23, 2026 and updated August 8, 2026 also recommends iPerf3 for local-network testing and emphasizes that two LAN endpoints keep the Internet out of the measurement. The appropriate conclusion is therefore specific: state how fast this tested setup moved data, identify which controlled changes altered the result, and name the component that remains the most plausible cause.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
