The router your ISP gave you is fine. It is not great. It is fine. The problem is that most people leave it in the configuration the technician handed them, which is the configuration that maximizes the number of households where nothing breaks, not the configuration that gives you good Wi-Fi.
Here are the things almost every home network gets wrong, and the actual fixes. Each one takes about five minutes. Together they will probably make your internet feel new.

Mistake 1: Letting the 2.4 GHz radio pick its own channel
The 2.4 GHz band has three non-overlapping channels: 1, 6, and 11. Your neighbors are also using these channels. If your router is set to "auto," it picks whichever channel looks least crowded the moment you boot it, then stays there forever as the neighborhood gets busier.
The fix is to install a Wi-Fi scanner app on your phone (Wifi Analyzer on Android, AirPort Utility with Wi-Fi scanning enabled on iOS), walk around your home, and pick the least-busy of 1, 6, or 11. Lock your router to that channel manually.
If you live in an apartment building, this alone will probably fix half your problems. The default auto-channel logic is bad at handling dense environments.
Mistake 2: Running 5 GHz at 80 MHz width in an apartment
The 5 GHz band has more channels and is faster, but in dense environments the wide channels (80 MHz, 160 MHz) overlap with everyone else's wide channels. The result is constant noise, retransmissions, and counterintuitively worse throughput than a narrower channel would give you.
The fix in apartments is to drop your 5 GHz channel width to 40 MHz, or even 20 MHz if it is really dense. You lose theoretical max speed, but you gain real-world reliability. In a single-family house with no close neighbors, leave it at 80. In a 200-unit building, drop it.
Mistake 3: Mixed WPA2/WPA3 with old devices on the same SSID
Most routers offer a "WPA2/WPA3 mixed mode" that lets old and new devices connect to the same network. This is a usability win and a security loss. In mixed mode, the network falls back to WPA2 protections for compatibility with the oldest device on it, which is probably your smart bulbs or that one printer from 2017.

The fix is to run two separate SSIDs: a clean WPA3-only network for your phone, your laptop, and anything modern, and a separate WPA2 network with a different password for legacy gear. This also gives you the option to put the legacy network on a separate VLAN if your router supports it, which contains the blast radius if one of those old devices ever gets compromised.
Mistake 4: Putting everything on one network
Your laptop, your phone, your TV, your smart fridge, your robot vacuum, and that random WiFi-enabled outlet you bought on Amazon are all on the same network, which means they can all talk to each other. That is not what you want. The smart fridge does not need to be able to scan your laptop. The robot vacuum should not have line of sight to your work VPN client.
The fix is network segmentation: at minimum, a "main" network for your trusted devices, a separate "IoT" network for everything that talks to the cloud and that you do not fully trust, and a "guest" network for visitors. Most modern routers support multiple SSIDs and at least basic VLAN isolation. VLANs are the proper way to do this, and most decent routers (Asus, Ubiquiti, anything running OpenWrt) handle them well.
If your ISP-provided router does not support multiple isolated networks, that is a sign you should buy your own router. A $100 Asus or a $150 Ubiquiti UniFi is a substantial upgrade over almost any ISP rental.
Mistake 5: Using your router as the only access point
Your router lives in whatever closet the cable enters the house, which is almost never the center of where you actually want Wi-Fi. The signal degrades sharply through walls, floors, and household clutter. The far end of the house gets weak signal, slow speeds, and dropped calls.
The fix is a wired access point at the far end of the house, ideally with an Ethernet cable run through the wall. If you cannot run Ethernet, MoCA adapters use the existing coax cable lines in your walls and give you near-Ethernet speeds. Powerline adapters work in a pinch but are unreliable depending on your wiring.
Mesh systems (Eero, Orbi, Deco) are the easy answer for non-technical people. They use a wireless backhaul between nodes, which works well enough for most homes but adds latency and halves throughput on each hop. A wired access point will outperform any consumer mesh, every time.
Bonus: turn on band steering and DFS
Two settings most routers ship disabled: band steering and DFS. Band steering tells dual-band devices to prefer 5 GHz over 2.4 GHz when the signal is good enough, which keeps your fast devices off the slow band. DFS (Dynamic Frequency Selection) opens up additional 5 GHz channels (52 through 144) that most consumer gear ignores, which means much less neighborhood interference. Some weather radar systems use these channels, so DFS-capable equipment is required to vacate them if it detects radar, which it almost never does in a residential area.
Total time investment
Picking a 2.4 GHz channel: 5 minutes. Setting channel widths: 2 minutes. Splitting WPA2 and WPA3 SSIDs: 5 minutes. Setting up an IoT VLAN: 10 minutes if your router supports it cleanly. Adding a wired access point: 30 to 60 minutes if the cable run is reasonable.
That is an afternoon, total, and it is the difference between Wi-Fi that works and Wi-Fi that you fight. Most people never do any of it because the network was working "well enough" the day they set it up, and they never reconfigured. The defaults are not your friend. They are the defaults.




