How to Increase Wi-Fi Speed at Home: Test Each Change and Keep Only What Helps

Most tips on how to increase Wi-Fi speed come as a list of ten things to try at once. If you try them all together, you can’t tell which one worked, or whether any of them did. Microsoft’s guidance on Wi-Fi and home layout gives a better rule. Run a speed test before you change anything, test at several places in the home, write the results down, and test again after each change.

This article applies that rule strictly. You start with a wired test to see what speed is actually reaching the house. Then you make one change at a time, repeat the same test from the same seat, and decide whether to keep or undo each change before trying the next. This matters because several things limit Wi-Fi at the same time: distance, walls, interference, the band, the router, your phone or laptop, and the plan itself. Cisco Meraki’s engineering documentation also notes that real wireless throughput is typically 50% or less of the advertised data rate. Measuring each change shows you which of those limits your home is actually hitting.

Check the plan before you test anything

Your plan sets the highest speed you can reach, so find out what it is first. The FCC’s home network tips start in the same place: check what speed you subscribe to before you judge the results. In Nigeria, the plan type matters as much as the headline speed. For example, MTN’s router broadband page lists capped plans, “unlimited speed based” plans and “unlimited volume based” plans. It also shows how to check your bundle balance with 4614# or 312500#, the myMTN app, or myMTN Web. Read the terms of the plan you’re actually on, because they decide the ceiling your Wi-Fi is working under.

Test in stages so each result points somewhere

NETGEAR’s knowledge base describes a three-stage test, and each stage isolates one part of the connection:

• Laptop plugged into the modem with a cable: this shows whether you’re getting the speed you pay for. If it’s low, the problem is the service or the modem.
• Laptop plugged into the router with a cable: this shows whether the router passes that speed through. NETGEAR says that if the modem result is much higher than the router result, the router may need upgrading or may be “throttling your speeds because of custom configuration.”
• Over Wi-Fi, close to the router: NETGEAR says Wi-Fi speeds here “should be similar to or only slightly slower than your speeds over Ethernet.” If they’re much slower, the router or device may not support current Wi-Fi standards, or there may be interference.

Many Nigerian homes use a single 4G or 5G router that works as both modem and router. In that case the first two stages collapse into one wired test. If your laptop has no Ethernet port, the FCC suggests a USB Ethernet adaptor.

Real cases show why the wired test matters. In one r/nbn thread, a poster on a 100/20 plan got only 65–80 Mbps. Once they confirmed Ethernet was fine, the problem was narrowed to their home Wi-Fi. In an older Super User question, the result pointed the other way. The wired desktop measured only 10 Mbps, the laptop on Wi-Fi 3 Mbps and a phone 7 Mbps. That wired figure matters because no Wi-Fi setting can push a device past what the cable itself delivers.

Make the test repeatable

A speed test is an estimate, not a certified measurement. FAST.com, which Netflix runs, describes its result as “an estimate of your current Internet speed.” It also shows latency both unloaded and loaded with traffic. The difference between the two is called bufferbloat, and it can explain why video calls stutter even when the download figure looks fine. NETGEAR’s steps use Speedtest.net and advise switching to a closer server if the automatic one is far away. Pick one tool and one server and use them for every test.

Keep everything else the same too. The FCC notes that several people streaming and video-calling at once can slow even a fast router. Microsoft suggests ending processes that use a lot of bandwidth, which you can find in Task Manager. Intel’s Wi-Fi guidance adds that in crowded areas, performance drops and recovers on its own as neighbours use their networks. From that, it follows that you should test at roughly the same time of day each time, ideally the time your Wi-Fi usually struggles.

Watch the units as well. Speed tests report megabits per second (Mbps). File-copy windows often show kilobytes or megabytes per second, and one byte is eight bits. In one Super User case, a 256 KB/s file copy on a 2.4 GHz link was reported next to a signal Windows called “excellent.” Comparing figures in different units gives you a misleading picture.

The one-change checklist

This checklist is the method for the rest of the article. Every later section adds one change to it.

1. Write down the ceiling. Note your plan’s speed and terms, and your wired test result. The wired figure is the most your Wi-Fi can deliver.
2. Choose your test spots. Pick one spot in the router’s room, a few steps away but not right beside it. Then add each room where you actually use the internet. Mark exactly where you’ll sit or stand.
3. Fix the method. Use the same device, the same tool, the same server and roughly the same time of day. Hold the device the same way each time.
4. Quiet the network. Pause large downloads and streaming on other devices before each test.
5. Record the baseline. At each spot, run several tests and note the lowest and highest download results. Also note the band you’re on and the signal reading (the next two sections show how to find both).
6. Make one change only. That might be moving the router, switching band, changing channel, changing channel width or changing one device setting.
7. Retest exactly as before. Same spots, same number of runs, same conditions.
8. Decide. Keep the change only if the new results sit clearly outside the range your baseline runs already covered. Undo it if they don’t, or if another room got worse.
9. Only then move on to the next change.

A plain log is enough. Copy a line like this into your notes app for every test:

Date | Change tested | Spot | Band | Signal (dBm) | Download (low–high) | Upload | Keep or undo

Find Out What’s Actually Limiting Your Wi-Fi Speed

Your baseline log already tells you where to look. Here is how the common patterns read:

• Wired result well below your plan. The limit is upstream of your Wi-Fi. The FCC advises contacting your provider about outages or troubleshooting, and notes that “a simple router reboot” sometimes fixes the problem. FAST.com’s own guidance says that if tests often show less than you pay for, ask your ISP about the results. No Wi-Fi change will fix this.
• Wired result fine, Wi-Fi near the router far below it. NETGEAR’s test notes point to the router’s Wi-Fi, older Wi-Fi standards on the router or device, or interference.
• Fast near the router, slow in far rooms. Distance and walls are the likely cause. Placement and band are the next things to test.
• One device slow while others are fine. Microsoft’s troubleshooting steps say that if another device connects fine, “the source of the problem is likely due to your device.”

Each pattern points to a different fix. That’s why a household that buys a router for a device problem, or tweaks channels when the plan is the limit, sees no change.

Know what the router can realistically deliver

Speeds printed on router boxes can mislead. Cisco Meraki’s documentation explains that an advertised maximum is “a theoretical total maximum data transfer rate (both transmit and receive).” Its list of limiting factors covers distance, signal-to-noise ratio, interference, physical obstructions, nearby networks and device capabilities. The FCC’s practical version of this: search your router’s model number to see whether it can deliver your subscribed speed. If it can’t, you may need to buy a new router or rent an upgraded one from your provider.

Update firmware, but know what comes after

Firmware is the router’s own software. Apple’s recommended router settings say automatic firmware updates deliver “important improvements to the stability, performance, and security of your router.” Apple also advises backing up your router’s settings before you change any of them. Some vendors ask for more. ASUS recommends restoring factory default settings after a firmware update and then setting the router up again. That wipes your Wi-Fi name, password and any custom settings. So before updating, write down your network name, password and admin login, and find your provider’s setup details. Treat a firmware update as one change in your log like any other, and test before and after.

Test Router Placement Changes With Signal Readings by Room

A speed test shows what you get. A signal reading shows why, and it helps you tell whether moving the router helped one room at another room’s expense.

Read signal in dBm, not bars

Signal strength at your device is reported as a negative number in dBm. Oscium (formerly MetaGeek) explains that the closer the number is to zero, the stronger the signal. It also notes that the bars most operating systems show “not granular enough for troubleshooting.” Oscium’s suggested reference points are:

• about −67 dBm for very reliable video calls and streaming
• about −70 dBm as the minimum for reliable email and browsing
• about −80 dBm, where “packet delivery may be unreliable”

Oscium calls these “suggestions only.” ASUS uses its own bands: −20 to −70 dBm is good, −71 to −80 is fair, and −81 or lower is weak.

Signal and speed are different things. Oscium states that “strong RSSI does not guarantee good performance,” because interference can still slow a strong connection. That’s why every log line records both signal and speed.

To see dBm, you need a Wi-Fi analyser app. Microsoft points Windows users to analyser apps in the Microsoft Store. Oscium says its own inSSIDer is free on Windows and macOS. On Android, apps can only scan so often. Android’s developer documentation limits each foreground app to four scans in a two-minute period. The WiFiAnalyzer project explains that when this limit kicks in, Android returns the previous results, so the display “appears frozen, then jumps.” When you walk into a new room, wait for a fresh reading before writing anything down.

Move the router, then walk the same route again

For router placement, the sources agree on the basics. Microsoft suggests cutting the number of walls between router and device, moving the router towards the middle of the home and higher, and avoiding corners and spots under desks. It also warns about metal objects such as filing cabinets. The ACMA adds keeping the router off the floor and away from furniture and thick walls. Microsoft also notes that the strongest signal is usually “a few feet from your access point, but not right next to it,” and that the way you hold or position the device can cost some signal.

Measure one move at a time. Record dBm and speed in every room, move the router, then walk the same route and repeat the same tests. The rule for deciding is my own synthesis of the thresholds above. Keep the new position if your problem rooms moved up towards the −67 to −70 dBm range and speed rose, without pushing a room that was fine into the weak range. If the gains in one room came with losses in another, the log shows the trade-off so you can choose knowingly.

If your router is an operator’s 4G or 5G unit (MTN describes its router plans as working on an MTN 4G or 5G Wi-Fi device), moving it can change two things at once. The router’s own mobile signal may change as well as its Wi-Fi coverage. After every move, rerun the close-range test next to the router. That way you know whether the incoming speed changed or only the coverage did.

When the signal is strong but the speed isn’t

If readings look healthy but speed doesn’t, check for interference. The ACMA suggests temporarily switching off and unplugging electronic devices, and watching for slowdowns that line up with a microwave or cordless phone being used. Cisco Meraki’s list of interference sources includes microwave ovens, cordless phones, Bluetooth devices, wireless cameras, fluorescent lights and other Wi-Fi networks. Unplug one suspect at a time and retest, just like any other change.

Placement has limits. In one Super User case, the house was built in 1927 with dense plaster walls and was on a 300 Mbps plan. The poster measured about 350–400 Mbps on 5 GHz on the router’s floor, around 70 Mbps across most of the second floor, and only 15–20 Mbps in an office at the end of the hall. When readings stay weak after sensible moves, the fix is hardware, which the last section covers.

Switch to the 5GHz Band (and Test Whether It Actually Helps)

2.4 GHz vs 5 GHz is a trade-off, not an automatic upgrade. Microsoft’s comparison credits 2.4 GHz with longer range and better passage through walls. Its downsides are slower throughput, fewer channels that don’t overlap, and more congestion because microwaves, cordless phones and Bluetooth share the band. 5 GHz offers faster throughput and less congestion, but shorter range and weaker passage through walls. The FCC puts it the same way: 5 GHz is faster, and its signal covers a shorter range. The FCC also suggests reserving the 5 GHz network for your most important uses, such as work or school.

That makes the right band a question of distance, which your log can answer. In the old-house case above, 5 GHz gave about 350–400 Mbps on the router’s floor against roughly 90 Mbps on 2.4 GHz, but 5 GHz “doesn’t appear to reach the second floor.” The same home needed different bands in different rooms.

Confirm which band you’re really on

On Windows 11, go to Settings > Network & internet > Wi-Fi > (your network) properties and read the value next to Network band (channel). Microsoft’s guidance adds that if the value shows more than one band, your connection is using Wi-Fi 7’s Multi-Link Operation. This is the check one commenter suggested in an r/HomeNetworking thread. There, a PC was stuck around 20 Mbps while other devices in the house got 130 Mbps, and the commenter’s first question was whether it had landed on 2.4 GHz.

One network name or two?

Here the vendors disagree. Microsoft recommends separate names for each band “so you’ll know which network you’re connected to.” Apple recommends one name for all bands and warns that separate names may stop devices connecting reliably to every band. Routers that use one name steer devices between bands automatically. ASUS calls its version Smart Connect, and notes that a phone’s own built-in Wi-Fi preferences can make the steering rules ineffective or cause frequent disconnections.

A practical way to reconcile the two: split the names temporarily so you can test each band in each room with certainty. Then decide what to keep based on your results. If automatic steering keeps putting a device on the slower band in a room where your log shows 5 GHz winning, keeping separate names is the fix that measurably helps. If it doesn’t, going back to one name follows Apple’s reliability advice.

A note on 6 GHz in Nigeria

Some newer routers add a 6 GHz band. Microsoft notes that it performs best close to the router, and only if both the router and the device support Wi-Fi 6E. In January 2026, the Nigerian Communications Commission published a framework for the lower 6 GHz band (5925–6425 MHz). A compliance summary from iCertifi explains that qualifying use is licence-exempt, but covered equipment must be NCC type-approved before it’s imported, sold or used. ASUS also cautions that supported channels differ by country, so a device that supports 6 GHz may not connect if the band isn’t available where you are.

Change the Wi-Fi Channel and Width to Reduce Interference

A band is divided into channels, and neighbouring networks compete for them. Cisco Meraki’s documentation explains that two access points on the same channel “will share the capacity of the channel.” Overlapping channels are worse. Oscium explains that on 2.4 GHz, only channels 1, 6 and 11 don’t overlap. Sharing one of those is “a much better choice than dealing with adjacent-channel interference” on the channels in between. Microsoft and Intel give the same advice.

Auto first, then a manual challenger

Vendors split on the default here too. Apple recommends setting channel selection to Auto. Microsoft says some routers’ Auto option “work great and pick the best channel, but others might not.” Your log settles it for your home. Record results on Auto first, then try one manual channel.

To choose it, use an analyser app to see where nearby networks sit. Microsoft’s rules for 2.4 GHz: pick 1, 6 or 11, and prefer the one with the fewest access points on it. For 5 GHz, where overlap matters less, choose the channel with the fewest access points.

On 5 GHz, some channels are DFS channels, which routers share with radar. Intel suggests that if you get drops or can’t see your network while on one, you try a non-DFS 5 GHz channel.

Channel width: wider isn’t always faster

Channel width is how wide a slice of the band your network uses. Apple describes wider channels as “faster but more susceptible to interference.” It recommends 20 MHz on 2.4 GHz and Auto on 5 GHz and 6 GHz. Microsoft suggests setting 2.4 GHz to 20 MHz if your signal is strong and the channel clear but the connection is still unreliable. Intel suggests trying 40 MHz on 5 GHz if reliability is the problem, and warns that 80 MHz and 160 MHz pick up interference from many more sources.

Where the setting lives depends on your router. On ASUS routers, for example, it’s under Wireless > General in the web interface, and ASUS adjusts width automatically by default. For other brands, Microsoft points you to your router’s documentation, since you usually sign in through a web browser.

Change the channel or the width, never both at once, and retest the same spots. If your neighbours’ networks are busiest in the evening, Intel’s point about crowded networks improving and degrading on their own means an afternoon test can flatter a channel. Retest at the time you usually struggle before deciding to keep it.

Check Your Device Settings Before Blaming the Router

If one device is slow and everything else is fine, the router is the least likely culprit. One Super User poster got 50+ Mbps on a Mac but couldn’t get above 15 Mbps on a Windows PC in the same room. Buying a new router didn’t help. What finally fixed it, in the poster’s words, was “a new Wi-Fi dongle (dual band) for my PC.” Before spending money, run through the checks below and log each one as a separate change.

Find out what your adapter supports

In Command Prompt, type netsh wlan show drivers and look next to Radio types supported. Microsoft explains that 802.11ax means Wi-Fi 6/6E and 802.11be means Wi-Fi 7. It also notes that Wi-Fi 7 support starts with Windows 11, version 24H2. If your adapter lists neither, a Wi-Fi 6 or Wi-Fi 7 router can’t give that PC the newer standard’s benefits.

Next, create Windows’ wireless network report. Run Command Prompt as administrator and type netsh wlan show wlanreport. The report is an HTML file covering Wi-Fi events from the last three days. It shows red circles for errors and lists each adapter’s current driver version, driver date and any problem number. Microsoft says the problem number matches a Device Manager error code that explains why a driver didn’t load.

Settings worth testing on Windows

Microsoft’s troubleshooting guidance lists several device-side settings. Each is one change for your log:

• Adapter power saving: in Device Manager, open your Wi-Fi adapter’s Properties > Power Management and untick “Allow the computer to turn off this device to save power.”
• Wireless adapter power plan: under Power Options, Microsoft’s steps set Wireless Adapter Settings > Power Saving Mode to Maximum Performance.
• Band filtering: on the adapter’s Advanced tab, check that the Wireless Mode or Band setting allows your network’s frequency.
• Driver: compare the driver version and date with what’s on your PC maker’s website. Before uninstalling a driver, Microsoft advises downloading a backup first. If Windows doesn’t reinstall a driver automatically, you’ll need the backup, and the PC may not be able to get online to fetch one.

Warning before you use network reset: Microsoft calls network reset the last step to try. It removes your network adapters and their settings. Afterwards you may need to reinstall VPN software and re-enter saved Wi-Fi passwords. In the r/HomeNetworking case above, network reset only fixed the speed until the next boot, and later stopped working at all. A reset can hide a device fault without fixing it.

Two “hidden fixes” to treat carefully

Receive segment coalescing. In an r/it thread, a commenter suggested turning off receive segment coalescing on a laptop that was slow on every network test. Microsoft’s documentation describes this feature as combining received segments to reduce processing overhead. None of the sources reviewed here show that turning it off speeds up Wi-Fi, and the poster in that thread hit a “permission denied” error before finishing.

If you want to test it, treat it as a reversible experiment:

1. Open PowerShell as administrator.
2. Run Get-NetAdapter to find your Wi-Fi adapter’s name.
3. Run Disable-NetAdapterRsc -Name "Wi-Fi", using your adapter’s actual name. The cmdlet reference notes that the adapter restarts, so the connection will drop briefly.
4. Retest. If nothing improves, turn the feature back on with Enable-NetAdapterRsc and the same name.

Android’s Wi-Fi scan throttling. You may have been told to turn this developer option off to speed up Wi-Fi. Android’s documentation describes it as a limit on how often apps can scan for networks, and says the toggle is there “for local testing.” Nothing in that documentation says it limits connection speed. Its practical effect is on analyser apps: it can slow down how often your room-by-room readings refresh. The WiFiAnalyzer project adds that the setting applies to every app on the phone, and that its wording and location vary by manufacturer.

When Software Changes Aren’t Enough: Extender, Mesh, or New Router?

Only your log can justify buying hardware, and it also tells you which hardware to buy:

• Wired result is the bottleneck. No Wi-Fi hardware can help. NETGEAR, which sells mesh systems, says on its own site that any mesh system is “only as fast as your Internet speed”. It suggests mesh might be excessive on a 20–30 Mbps connection.
• Wi-Fi is slow even next to the router while wired is fine, and your devices’ adapters are current. The router itself is the likely limit. The FCC’s advice is to check whether your model can deliver your plan’s speed, and to buy or rent an upgrade if it can’t.
• Fast near the router, but some rooms stay weak after placement, band and channel tests. This is a coverage problem, and an extender, mesh system or cabled access point addresses it.

Before buying a Wi-Fi 6, 6E or 7 router, check your main devices with netsh wlan show drivers. Microsoft’s requirements call for both a router and a network adapter that support the newer standard. The PC-versus-Mac case shows what happens otherwise: the new router changed nothing because the old dongle was the limit.

Extender, mesh or cable: what each trade-off costs

The options below apply to coverage problems.

• Extender. Microsoft suggests an extender when you can’t move closer to the router or move the router itself. NETGEAR’s comparison describes the costs. Many extenders broadcast a separate network name you have to switch to, and traditional dual-band models “may reduce the available bandwidth by half.” Speeds can also be poor if the extender sits too far from the router.
• Mesh. NETGEAR describes mesh as several nodes under one network name that hand your device between them automatically. Tri-band and quad-band designs use a dedicated channel for traffic between nodes. It also lists higher cost and more demanding setup as disadvantages. Because NETGEAR sells both products, treat its comparison as the maker’s own account rather than independent testing. Cisco Meraki’s documentation, written for business mesh networks, notes that each wireless hop “will reduce bandwidth by 50%”. Fewer hops are better.
• A cabled access point. Answers to the old-house question put Ethernet to an access point on each floor as the “gold standard.” The alternatives mentioned were MoCA over existing TV coaxial cable, or powerline adapters, whose performance one answer says depends on the home’s wiring. If only wireless mesh is possible, another answer advises choosing a system with a separate 5 GHz radio for node-to-node traffic, so your bandwidth isn’t divided by two.

Measure before you buy. One answer in that same thread suggests checking with another device at the exact spot you’d put the extender, to confirm it actually gets a usable signal from the router. Your analyser app does this: stand where the extender or node would go and take a dBm reading and a speed test. If that spot is already weak, a device placed there has only a weak signal to repeat.

If the numbers point towards buying something, the choice between types has its own trade-offs. Our separate Wi-Fi extender vs mesh comparison covers that decision.

If you’re buying 6 GHz-capable equipment in Nigeria, remember the type-approval requirement covering import and sale. Asking the seller whether the model is NCC type-approved is a sensible check.

What to Do First

Run a wired speed test, compare it with your plan, and record Wi-Fi results with signal readings in each room before changing anything. That one baseline tells you whether the limit is your service, your router, your home’s layout or a single device. From there, make one change at a time, retest the same way, and keep only what measurably helps, so you don’t spend money on hardware that fixes a problem you don’t have.

Frequently Asked Questions

Why do I have full signal bars but slow internet?

Bars are too coarse to judge a connection by, and Oscium notes that a strong signal doesn’t guarantee good performance because interference can still slow things down. A slow wired test also points to the plan or provider rather than your Wi-Fi.

Does restarting the router actually help?

Sometimes. The FCC says a simple reboot can resolve a problem, and Microsoft notes it briefly disconnects everyone. If speed only recovers after each restart and then falls again, log it and keep looking for the underlying cause.

Should my 2.4 GHz and 5 GHz networks have different names?

Separate names make it clear which band you’re testing, as Microsoft recommends. Apple warns they can make connections less reliable, though. Split them while you test, then keep whichever setup your results favour.

Can I use 6 GHz Wi-Fi in Nigeria?

The NCC’s January 2026 framework for the lower 6 GHz band allows qualifying licence-exempt use. Equipment must still be NCC type-approved. You also need both a router and a device that support Wi-Fi 6E, and the band performs best close to the router.