What to check before replacing a slow home router

A slow connection does not always mean the router has reached its limits. The problem may be weak wireless coverage, a damaged Ethernet cable, a busy upload, or an issue outside the house. Before replacing the router, establish where performance falls apart. A few controlled comparisons can separate a coverage problem from a connection problem and help you avoid buying equipment that changes very little.

Describe the slowdown precisely

Start by noting what feels slow and where it happens. A video call that freezes in an upstairs bedroom points toward a different problem than every device losing internet access at once. Slow page loading, low download speed, and high delay during a call are related symptoms, but they are not interchangeable.

Record whether the problem affects one device or several, whether it happens near the router, and whether it follows a predictable time of day. If only one laptop struggles while other devices work in the same location, inspect that laptop's software, wireless connection, and background activity before replacing shared equipment.

Establish a wired baseline

Connect a capable computer to a LAN port on the router with a known-good Ethernet cable. Temporarily disable that computer's Wi-Fi so the comparison uses the cable. Pause large downloads and backups elsewhere in the house, then run a speed test more than once. Use the same test service when comparing results to reduce unnecessary variation.

Check the negotiated Ethernet link speed as well. A connection limited to 100 Mbps can make a faster internet service look slow even if the router is functioning properly. The computer port, adapter, cable, and router port all deserve inspection. A damaged cable can sometimes establish a slower link rather than failing completely.

If wired performance is also poor, compare the result with your service plan and any provider outage information. The modem, fiber terminal, provider connection, and router are still possible causes. Avoid connecting a computer directly to the provider's equipment unless you understand the required setup and security implications; the provider's diagnostic procedure is a better starting point.

Compare nearby Wi-Fi with the problem room

Run the same test on the same wireless device close to the router, then repeat it where the problem occurs. A strong nearby result and a weak distant result suggest coverage or interference rather than a generally inadequate internet connection. Keep other network activity as similar as possible during the comparison.

Move the router into an open, elevated location if the wiring allows. Metal cabinets, large appliances, and placement behind a television can make coverage worse. A higher-frequency band may offer more speed nearby while reaching less effectively through walls. Let actual room tests guide your placement instead of assuming one band will be best everywhere.

Look for traffic that fills the connection

A household can experience sluggish browsing while a speed test still reports a respectable download number. Large cloud backups or file uploads can fill the upstream connection and increase delay for other traffic. Pause those tasks temporarily and see whether calls or page loading improve.

Some routers offer queue management or traffic-priority settings that can help under load, but their implementation and processing demands vary. Change one setting at a time and compare both responsiveness and throughput. Do not enable every optimization switch at once; a collection of unexplained changes makes it difficult to identify what actually helped.

Check the router's condition and configuration

Look for blocked ventilation, an unreliable power connection, and unexpected restarts. Use the specified power supply rather than an arbitrary replacement with a similar connector. A restart may temporarily restore service, but needing frequent restarts is a symptom to investigate rather than a satisfactory maintenance routine.

Check for supported firmware updates through the manufacturer's documented method, and save a configuration backup when available. Avoid a factory reset as the first experiment, especially if the connection requires provider credentials or special settings. Also identify whether a provider gateway and a separate router are both routing traffic. That arrangement can complicate some applications, although it does not automatically explain every speed problem.

Replace the limitation you have demonstrated

Replacement makes sense when the router lacks needed port speeds, cannot handle your connection under ordinary load, behaves unreliably after other causes are checked, or no longer receives necessary security support. Match the replacement to those specific shortcomings instead of treating a large wireless speed figure as a promise of whole-home performance.

If coverage is the main issue, an additional access point with a wired connection may address it more directly. A wireless mesh node needs a useful connection back to the network, so placing it inside the dead zone can disappoint. Keep your test notes and repeat the same room and wired comparisons after any change. Improvement should show up where the household actually experienced trouble.