Slow Wi-Fi in One Room? Fix the Signal Path, Not Your Broadband Package
Your broadband connection is fast almost everywhere.
In the office next door, you get:
400 Mbps
In the corridor:
300 Mbps
Then you walk into one particular room and suddenly get:
30 Mbps
Teams calls freeze.
Cloud files take longer to open.
Websites hesitate.
Walk back into the corridor and everything improves again.
That pattern tells you something important:
your broadband package is probably not the main problem.
The internet connection entering the building may be perfectly healthy.
The weak point is more likely to be the wireless path between:
access point → walls/obstacles → device
Upgrading from 500 Mbps broadband to 1 Gbps does not make a Wi-Fi signal travel through a brick wall more effectively.
Fix the radio problem first.
First: Prove the Problem Really Is One Room
Before changing router settings, test methodically.
Use the same laptop or phone.
Run the same test:
beside the router/access point
immediately outside the problem room
inside the problem room
in another room at a similar distance
Microsoft specifically recommends taking a baseline in several locations and repeating those measurements after changing the network.
For example:
Beside access point: 470 Mbps
Corridor: 310 Mbps
Problem room: 38 Mbps
Nearby room: 260 Mbps
That is a strong indication that something about the affected room or the path into it is degrading Wi-Fi.
Now compare another device in the same room.
Every device is slow
Suspect:
coverage
walls/materials
interference
access-point placement
mesh design
Only one device is slow
Investigate:
Wi-Fi adapter
driver
supported bands
VPN
power saving
saved network profile
Microsoft recommends exactly this second-device test because it separates a network-wide problem from a device-specific one.
The Straight-Line Distance Is Not the Important Distance
Two rooms can both be ten metres from the router and have completely different Wi-Fi performance.
Why?
Because radio waves do not travel through every material equally.
A signal travelling through:
one plasterboard partition
may perform far better than a shorter path through:
brick
stone
reinforced concrete
metal framing
filing cabinets
metal doors
mirrors
machinery
Cisco also lists concrete, metal, mirrors and other physical obstacles as common sources of wireless degradation.
So the useful question is not:
“How far is the room from the router?”
It is:
“What is physically between the access point and the user?”
Understand 2.4 GHz, 5 GHz and 6 GHz
Modern Wi-Fi commonly operates across three bands.
2.4 GHz
Generally provides:
longer range
better penetration through walls
broad device compatibility
But typically has:
lower throughput
fewer clean channels
more interference
Microsoft describes 2.4 GHz as the band with the best range and obstacle penetration, although it is also the most congested.
For a distant room behind several walls, 2.4 GHz can sometimes give a better real connection than a weak 5 or 6 GHz signal.
5 GHz
Usually provides:
more throughput
more usable channels
lower congestion
but has:
shorter useful range
weaker penetration through obstacles
For most modern office environments, 5 GHz is extremely useful when access points are positioned properly.
6 GHz
Available with compatible Wi-Fi 6E and Wi-Fi 7 equipment.
It can provide:
high throughput
low congestion
low latency
when the device is close to the access point.
But Microsoft explicitly notes that 6 GHz has a shorter range and does not travel through obstacles as effectively as the lower-frequency bands.
So:
6 GHz is excellent for capacity.
It is not a magic dead-zone solution.
Do Not Assume the Highest Band Is the Best Band
Suppose the laptop sees:
5 GHz: weak
and:
2.4 GHz: strong
The 5 GHz network may have a much higher theoretical maximum.
That means very little if retransmissions, packet loss and unstable signal are destroying the actual connection.
A stable:
100 Mbps
link is generally more useful for business calls than an unstable connection fluctuating between:
350 Mbps and disconnected.
For one difficult room, test the bands separately before changing anything else.
Move the Access Point Before Buying Anything
This is one of the highest-value fixes.
Microsoft recommends placing the wireless router or access point:
centrally
higher up
away from walls
away from metal objects
with fewer obstacles between it and users.
Try temporary changes first.
Move it:
out of the cupboard
away from the floor
away from the metal filing cabinet
a few metres towards the centre of the building
Then rerun exactly the same test.
A surprisingly small change in position can alter the signal path substantially.
The Router Does Not Have to Live Beside the Internet Connection
This is one of the biggest design mistakes in small offices.
The fibre or broadband connection enters the building in:
a utility cupboard in one corner
so the router stays there forever.
That may be convenient for the cable installer.
It may be a terrible place for Wi-Fi.
A better design can be:
internet connection → router/firewall → Ethernet → centrally positioned access point
Now the broadband equipment can remain where it belongs while the wireless radio sits where the employees actually are.
For business Wi-Fi, this is often a much better long-term solution than repeatedly buying “more powerful” consumer routers.
Mesh Wi-Fi Can Help — If You Position It Correctly
Mesh can be useful where running Ethernet is difficult.
But there is a common mistake:
placing the mesh node inside the dead zone.
That node still needs a decent upstream connection.
If it receives a weak, unstable signal, it has very little good connectivity to repeat.
Instead place it:
between the main access point and the problem room
where the upstream connection remains healthy.
Then test again inside the affected room.
For permanent business installations, wired backhaul is usually more predictable:
main network → Ethernet → access point
rather than:
Wi-Fi → mesh node → Wi-Fi client
because wired backhaul removes one wireless link from the equation.
Channel Congestion Is a Different Problem
Weak signal and congested signal are not the same thing.
You can have:
strong Wi-Fi bars
but still experience:
high latency
erratic speeds
Teams problems
poor responsiveness
because several nearby networks are competing for the same airtime.
This is particularly common in:
flats
shared offices
business parks
dense residential areas
On 2.4 GHz, Microsoft recommends using channels:
1, 6 or 11
because these provide the standard non-overlapping options in common channel plans.
Do not pick an intermediate channel simply because fewer network names appear there.
It may overlap with both neighbouring channels and make things worse.
Channel Width: Wider Is Not Always Better
A wide channel can increase theoretical throughput.
It also consumes more spectrum.
On 2.4 GHz, Microsoft recommends testing 20 MHz where reliability is poor despite reasonable signal, because 40 MHz can create more interference in crowded environments.
For offices, stability and predictable airtime are usually more valuable than chasing the biggest possible speed-test figure.
Test Latency, Not Just Mbps
A one-room Wi-Fi problem may be much more obvious during:
Teams
VoIP
remote desktop
cloud applications
than during a simple download.
That is because business applications care about:
latency
jitter
packet loss
as well as throughput.
A Wi-Fi link delivering:
150 Mbps with low packet loss
may provide a much better call experience than:
400 Mbps with heavy jitter and retransmissions.
So when testing the problem room, note:
download speed
upload speed
latency
stability
not just the biggest number on the speed test.
When Faster Broadband Actually Would Help
There are situations where the package is the problem.
For example:
Wired Ethernet test: 35 Mbps
Beside router Wi-Fi: 32 Mbps
Problem room: 25 Mbps
Now the internet connection itself may be the main bottleneck.
Similarly, if the whole office becomes slow whenever:
cloud backups run
large files upload
several video calls start
then available WAN capacity may genuinely need reviewing.
But if:
wired = 500 Mbps
beside router = 450 Mbps
one room = 25 Mbps
buying 1 Gbps broadband will not fix the 25 Mbps room.
Extender or Access Point?
Plug-in extenders can help in simple environments.
But they are not automatically the best business fix.
An extender may:
consume additional airtime
provide inconsistent roaming
depend on a weak wireless backhaul
For a permanent workspace, a properly positioned wired access point is usually the cleaner architecture.
The objective is not:
“make the router louder.”
It is:
put usable radio coverage where employees actually work.
Do Not Put Every Access Point on Maximum Power
More transmit power does not automatically create a better wireless network.
If several access points overlap excessively:
roaming can become worse
devices may cling to distant APs
co-channel interference can increase
Professional Wi-Fi design is about:
coverage + capacity + channel reuse
not maximum output from every radio.
This is one reason simply adding access points randomly can make a network worse.
Check the Device Only After You Establish Scope
If every other device performs well in the room but one Windows laptop does not, then investigate the laptop.
Microsoft recommends checking the adapter's supported bands and driver settings where a device fails on a particular Wi-Fi frequency.
You can inspect the current Windows connection with:
netsh wlan show interfaces
Look at:
radio type
channel
receive/transmit rate
signal
You can also check:
Device Manager > Network adapters > Wi-Fi adapter > Properties
for adapter-specific configuration.
But if ten devices are slow in the same room, do not reset Windows on all ten.
That is almost certainly treating the wrong layer.
Forgetting the Network Is a Device Fix, Not a Coverage Fix
For one problematic Windows device:
Settings > Network & internet > Wi-Fi > Manage known networks
Select the network and choose:
Forget
then reconnect.
This can repair a corrupted saved profile.
It will not make a Wi-Fi signal penetrate reinforced concrete more effectively.
Likewise, Windows Network Reset is a last-resort device troubleshooting tool—not a radio-design solution. Microsoft itself recommends it late in the troubleshooting process.
The One-Room Wi-Fi Troubleshooting Order
If Wi-Fi is slow in one room:
1. Test the broadband connection over Ethernet.
2. Test Wi-Fi beside the access point.
3. Test the same device inside the problem room.
4. Test a second device there.
5. Identify which Wi-Fi band is being used.
6. Compare 2.4 GHz and 5 GHz.
7. Use 6 GHz only where signal remains strong.
8. Look at the physical path through walls and obstacles.
9. Temporarily move the access point higher or more centrally.
10. Check channel congestion.
11. Use sensible channel widths.
12. Position mesh nodes before the dead zone, not inside it.
13. Prefer wired access points for important permanent work areas.
14. Investigate the individual PC only if the problem follows that device.
15. Consider faster broadband only when wired testing proves the WAN itself is the bottleneck.
The key principle is:
If one room is slow and the rest of the building is fast, fix the wireless path before buying more internet speed.
How Hamilton Group Can Help
Hamilton Group can help businesses diagnose Wi-Fi problems based on evidence rather than replacing equipment at random.
We can help with:
Wi-Fi coverage surveys
access-point placement
channel planning
2.4, 5 and 6 GHz configuration
Wi-Fi 6E and Wi-Fi 7
mesh Wi-Fi
wired access points
PoE networking
Windows wireless problems
business broadband diagnosis
For offices, warehouses and commercial properties, the aim is to create stable coverage where people actually work, rather than concentrating all the wireless equipment beside the broadband socket.
Visit hgmssp.com or call 0330 043 0069.