Stop upgrading your router — fix these settings first

Published Aug 5, 2026, 2:00 PM EDT A seasoned mechanical design engineer turned tech reporter and reviewer, Chandraveer brings more than four years of consumer tech journalism experience to the table, with bylines at Android Police and iPhoneHacks. He's written about everything from UI and UX changes across various apps to emerging software and AI trends. At XDA, he showcases his versatility in the tech reporting space with articles rooted in personal experiences and frustrations. Chandraveer's passion for consumer tech spills over into hobbies such as mechanical keyboards, photography, and 3D printing. With an academic background in design and manufacturing, his insatiable curiosity spans beyond the digital domain. Chandraveer's downtime is an eclectic mix of reading fiction, practicing calligraphy, conceptualizing new products, and enjoying an expansive FLAC audio library. Every home networking upgrade typically starts with mulling over a router upgrade, because computing has conditioned us to think that new hardware typically brings performance improvements if you throw enough money at the problem. If you've graduated from using the ISP-issued router, you're already a step ahead. However, before pulling the trigger on new hardware, it's worth revisiting the firmware settings on your current gear. I spent the better part of a year enduring a maddening nightmare with my old router because the out-of-the-box experience was deceptively adequate at first. A few weeks in, any demanding task such as work calls on Google Meet, competitive online gaming, or even connection strength over long distances brought out its weaknesses. I was on the verge of throwing more money at a mesh node, but the fixes were surprisingly easy when you prefer 192.168.0.1 in a browser to the router's companion smartphone app. The myth of single-SSID simplicity Smart Connect is a marketing trap for real-world homes On my current router, entering that IP address in a browser while connected to the problematic network opens up the router config page. Here, you'll find advanced settings that are absent from the mobile app, as they are typically intended for network administrators. First off, I switched off Smart Connect. Hardware manufacturers market this as a friction-free convenience, claiming the router will intelligently steer your client devices to the optimal frequency depending on proximity and load. In a concrete structure like my home, high-frequency 5GHz signals rapidly degrade over long distances, while 2.4GHz signals penetrate dense obstacles easily at the cost of reduced bandwidth. With Smart Connect switched on, laptops and phones programmed to prefer 5GHz with their newer radios reach points of indecision in several rooms, where they cling to a weak 5GHz signal instead of switching to the other band for reliability. The solution entails splitting the Wi-Fi signal into distinct, suitably named SSIDs. This way, I can manually pin high-bandwidth devices to 5GHz when in line of sight, while relegating stationary, long-range hardware to the lower band. Next, I turned my attention to the channel width and frequency allocation, where default settings hamstring performance. Out of the box, most routers set channel widths to auto-negotiate to the maximum values — often 80MHz or even 160MHz on 5GHz, and 40MHz on 2.4GHz — to impress buyers with inflated numbers in the product listing. In real-world performance, a wider channel only opens up more frequencies to electromagnetic noise and adjacent network interference. It robs you of usable range because other routers in the vicinity use the same band. Fixing this requires an app like Wi-Fi Analyzer to audit the available spectrum wherever important client devices are situated. The visual heat maps revealed a crowded landscape of neighboring access points, all battling over overlapping channels such as 2, 4, and 9. By locking the 2.4GHz band strictly to a 20MHz channel width and selecting a non-overlapping standard channel — specifically channel 11, which showed the lowest ambient noise floor — I immediately restored network stability to the farthest corners of my home. On the 5GHz side, dropping the channel width from 160MHz to 80MHz reduced signal degradation at increasing distances without sacrificing data throughput. Checking impact of legacy devices on bandwidth Airtime Fairness sounds cool, but it doesn't work all the time Understanding how Wi-Fi routers communicate with clients further reveals that they transmit data sequentially, so at any point, requests to address queue up like jobs for a printer. The router allocates airtime to each client, but the default config typically programs transmission slots based on packet count rather than query-handling time, even if that time is sub-millisecond. This model works when all clients support the same Wi-Fi standards, but an older device with a lower data reception bitrate can hog airtime and delay other devices' request processing on the network. Packet loss also dents performance, like a smart speaker with poor signal reception repeatedly requesting retransmission. On other devices, it shows up as micro-stutters during video calls or latency spikes in my online games. Enabling Airtime Fairness forces the router to address requests by allocating equal time to each client device, rather than waiting on a slow client to finish receiving each data packet before moving on. Fast devices process massive amounts of data within their allotted window, while slow devices handle only as much data as they can in the same timeframe before yielding. On advanced routers like the TP-Link Archer AX73, you can assign two levels of priority to a few clients, so the router emphasizes their requests over others. If disabled by default, switching on Airtime Fairness makes a bigger difference than you'd imagine. Relegate your smart home devices to an isolated network Free up the main network for more important devices Glossing over smart home gadgets would be remiss when discussing Wi-Fi clients operating on older standards. Over the years, I'd accumulated an assortment of smart bulbs, ambient light strips, and smart speakers, all running on cheap microcontrollers with 2.4GHz Wi-Fi. Their setup flow typically encourages users to connect every IoT device to the primary home network alongside their laptops, NAS, and smartphones. Security risks like those uncovered with Eufy and Wyze security cameras notwithstanding, having IoT devices share Wi-Fi with important personal devices is a bad idea. These clients typically have persistent broadcast traffic, pinging local subnets, and attempting to establish peer-to-peer connections with other hardware across the LAN. Consequently, your router is stuck processing endless trivial packet requests that distract from high-priority data transfers like a 4K Netflix stream. Airtime Fairness helps limit the performance impact, but I configured a dedicated guest network on the 2.4GHz spectrum as a designated sandbox for all my smart home gear and guests' devices. Even mid-tier home routers now include settings to isolate these devices on a virtual LAN, with additional per-client controls to restrict peer-to-peer traffic, internet access, and discoverability. This way, I can ensure an LED light controller only communicates with light groups, and doesn't snoop through my primary network’s IP range. So, a compromised smart bulb firmware update or one with an unpatched vulnerability remains isolated to that device. Check settings before Amazon listings Living with a subpar home network was an embarrassing tax I paid for trusting factory defaults on capable hardware. By taking 20 minutes to split the frequency bands, lock sensible channel widths, enable Airtime Fairness, and quarantine IoT devices, I made my inconsistent wireless experience a low-latency network across two floors of solid concrete. Chances are, your router is in a similar soup and needs slight reconfiguration to improve the user experience without spending a cent.