Is full Wi-Fi signal still slow? 6 common misconceptions about enterprise Wi-Fi.
The company has applied for 1000M commercial broadband, and the Wi-Fi on mobile phones and notebooks shows full strength, with no major problems under normal circumstances. However, every Monday morning, or when multiple people are having a Teams Meeting in the conference room, the screen starts to freeze, screen sharing becomes unsmooth, and file synchronization slows down significantly.
When faced with this situation, many companies' first reaction is:
"Is the broadcast not fast enough?"
"Should we add another AP?"
"Would simply switching to Wi-Fi 7 solve the problem once and for all?"
The problem may not actually be with the strength of the Wi-Fi signal.
Full marks only indicate the first part of the journey.
A full Wi-Fi signal on a phone or computer mainly indicates that the device is receiving a strong wireless signal. However, this icon alone cannot determine whether the entire internet connection is smooth.
A seemingly simple internet connection may actually involve:
Notebook／Mobile → AP → Switch → Router／Firewall → ISP → Cloud Service/Website
The Wi-Fi icon only reflects part of the situation between the device and the access point (AP). It doesn't show whether the channel is busy, whether there is wireless interference nearby, whether the switch or firewall behind the AP can handle it, or even the performance of the ISP and cloud service at that time.
In other words:
Having coverage does not equate to having sufficient capacity; having a signal does not equate to having a good actual experience.
The following six common misconceptions are precisely why businesses are most likely to misdiagnose Wi-Fi problems.
Misconception 1: If 1000M is applied for, each device should have 1000M.
1000M is the maximum access speed indicated by the ISP plan, which is shared by the company's devices. It does not mean that each notebook and mobile phone has its own dedicated 1000M line.
After data leaves the device, it still needs to pass through AP, Switch, Router/Firewall and other network devices. Even after the firewall has security features such as IPS, Application Control, Malware Protection or SSL Inspection enabled, its actual processing capacity may still be lower than the highest Firewall Throughput listed in the specifications.
In addition, the performance of the website, Microsoft 365, or other cloud services themselves will also affect the speed experienced by the user.
Dividing 1000M directly by the number of devices yields a meaningless result. To determine if the network is sufficient, one should pay attention to how many devices are using the network simultaneously during peak hours, what they are doing, and whether there are any other bottlenecks along the network path.
If the problem lies with Wi-Fi, Switch, or Firewall, upgrading the Broadband alone may have very limited effect.
Misconception 2: With only 30 employees, the Wi-Fi load must be low.
When planning enterprise Wi-Fi, simply counting the number of employees can easily underestimate the actual demand.
Assuming each employee uses a notebook and a mobile phone, 30 people already represent 60 devices. Add to that tablets, meeting room equipment, wireless printers/scanners, visitor devices, and other connected devices, and a company of 30 people can easily have 60 to 100 endpoints, or even more.
However, only part of the number of devices was disclosed.
What truly affects Wi-Fi performance is how many devices are transmitting data, what data rate they are using, and how many retransmissions are needed when the connection quality is poor.
You can think of Wi-Fi Airtime as a single-lane road shared by everyone, with each device using this road to transmit data. Devices with good connection quality can pass through faster; devices using lower data rates or requiring frequent retransmissions will occupy the road for longer, and other devices will naturally have to wait longer.
Wi-Fi 6 and Wi-Fi 7 can more intelligently arrange different devices to use this route, but Airtime is still a shared resource, and not each device has its own dedicated line.
The actual use of the device is also important. A Wi-Fi IP camera that continuously uploads images may take up more airtime than several mobile phones that are just on standby or occasionally checking emails.
Therefore, when planning, you should ask more detailed questions: Which devices are using Wi-Fi? Where are they located? Which frequency band are they using? What type of data are they transmitting? Are the problems concentrated during a particular busy period?
Misconception 3: If Wi-Fi is slow, just add an access point (AP); it doesn't matter where the AP is placed.
Increasing AP can sometimes improve coverage or capacity, but the key is to first identify which problem the company is facing.
If some rooms or seats do not receive a stable signal, it may be a coverage issue; if all seats show full signal and only slow down when multiple people are using the device at the same time, you should further check the Capacity, Channel, and Airtime.
Adding access points (APs) without a comprehensive plan can have the opposite effect. Multiple nearby APs using the same or interfering channels will compete for airtime. Ultimately, while the number of Wi-Fi bars may increase, actual speed and stability may not improve.
The placement location should not be overlooked.
Hong Kong offices commonly feature low ceilings, false ceilings, air conditioning ducts, wiring ducts, glass meeting rooms, concrete walls, and numerous metal filing cabinets. These materials and structures can absorb or reflect signals and may also alter the propagation path of wireless signals.
If the AP is stored above the false ceiling and there are metal ducts or other obstructions nearby, even if it looks neat, it may not be an ideal installation location.
There is another variable in high-density commercial buildings: the addition of access points or increased wireless usage in nearby offices may suddenly cause the originally stable channel to become congested.
The number, location, orientation, channel, and power of the access points (APs) should all be planned according to the actual environment. Installing them in a convenient location after the renovation is complete is often the beginning of problems.
Myth 4: Switching to Wi-Fi 6E or Wi-Fi 7 will naturally eliminate the old problems.
While Wi-Fi 6, 6E, and 7 do offer higher efficiency, greater capacity, and lower latency, the new standards do not automatically correct existing network problems.
To fully utilize the capabilities of next-generation Wi-Fi, several conditions need to be considered:
Do Notebooks and Mobile devices support the corresponding standards?
Are the AP location, channel, coverage, and RF design reasonable?
Can the wired infrastructure, including Switch, Uplink, PoE, and Cabling, provide sufficient support?
Does the firewall have sufficient practical handling capabilities?
Is the ISP connection stable?
Do existing devices and applications really need to be upgraded?
If the existing access point (AP) is misplaced, or the real bottleneck is in the switch, firewall, or cabin, simply reinstalling the new AP in its original position will not solve the old problems.
When purchasing Wi-Fi 6E/7 equipment, Hong Kong businesses should also pay attention to local specifications. According to the current HKCA 1081, the designated 6GHz frequency bands for license-free use in Hong Kong are 5.945–6.425GHz. When purchasing overseas versions of equipment, in addition to the model and maximum speed, it is also necessary to confirm whether they meet the usage requirements of the Hong Kong OFCA.
Whether an upgrade is needed should be determined by the actual requirements and assessment results. Simply pursuing the latest specifications often fails to solve the original problem.
Myth 5: If Office works smoothly most of the time, it will definitely be enough for busy periods.
Everything is normal when colleagues haven't all returned in the morning, but it starts to slow down during large meetings or busy periods, which is a common situation for enterprise Wi-Fi.
The meeting room is a typical example.
Normally there might only be two or three devices in the room, but during large meetings, multiple colleagues will gather in the same spot, using both notebooks and mobile phones simultaneously. Some will turn on cameras, conduct two-way voice communication, share screens, while others will access cloud files.
These real-time applications, in addition to requiring bandwidth, are also more sensitive to latency, jitter, and connection stability. Even if the total bandwidth is not very high, a short delay can cause "chokes," "audio cutouts," or video pauses.
To determine these types of issues, it's necessary to understand where and when the high-density usage is concentrated, how many devices are active simultaneously, and whether it's general browsing or real-time applications like video/voice. The capabilities of the access point (AP), band, and channel to handle localized peaks also need to be considered.
"No one complains normally" proves that the design is good enough. Everyday use and busy scenarios are two different challenges.
Misconception 6: If there are multiple access points (APs), the device will automatically connect to the most suitable one.
My colleague was using Teams Call as he walked from his seat into the meeting room. The Wi-Fi signal on his phone didn't change noticeably, but the sound suddenly cut out for two seconds.
This type of situation may be related to roaming.
Many people believe that as long as multiple access points (APs) are installed in Office, the system will automatically switch the phone or notebook to the one with the closest signal and the strongest signal. In reality, when the AP is switched is largely determined by the client device itself.
Even if there is a nearby access point with a better signal, some devices may continue to connect to the one that was originally farther away until the connection quality deteriorates further before switching. This situation is usually called a Sticky Client.
Simply put, the device is still "holding onto" the connection to the remote access point. The screen may continue to show Wi-Fi, but the data rate has dropped, and retries and instability may occur.
Roaming behavior can vary across different brands, models, drivers, and operating systems. A good user experience requires appropriate coverage between access points (APs) and compatibility with channel, power, SSID, client device capabilities, and the user's actual movement path.
Having multiple access points (APs) is just the first step. The actual timing of the device switching and which AP it connects to still depends on the overall design.
How should an enterprise Wi-Fi assessment begin?
Slow Wi-Fi is just a symptom. Adding an access point or switching to Wi-Fi 7 without identifying the cause is like deciding on a solution without doing any troubleshooting, which can easily lead to misdiagnosis.
A systematic enterprise Wi-Fi assessment can begin with the following four steps.
Step 1: Record the problem pattern
First, record when the problem occurred, where it was concentrated, which devices were affected, and what application was being used at the time.
This data helps to determine whether the problem affects the entire network or is concentrated in a specific area, on a specific device, or during peak hours.
Step 2: Establish a wired Baseline
Conduct wired testing at the Gateway or a suitable location to verify ISP connectivity, latency, and stability.
If the wired connection itself is not working properly, you should start by checking the ISP or upstream network. If the wired connection is working properly but the wireless experience is still not ideal, then the investigation should focus on the AP and RF environment.
A single Speedtest run conducted by a mobile phone via Wi-Fi can only be used as one reference and cannot represent the overall health of the network.
Step 3: Check layer by layer along the Network Path
Start with Router/Firewall, Switch, Uplink, PoE, and Cabling, then check AP location, Channel, Signal-to-Noise Ratio, and Interference.
The timing of testing is also important. An empty office might function normally, but a Monday morning or during a large meeting could be a different story. It's best to collect data when and where the problem actually occurs.
Step 4: Prioritize improvements based on evidence.
After completing the inspection, determine the appropriate course of action: adjust the channel or power, move the AP, improve network cabling, upgrade the switch/firewall, resolve ISP issues, or add APs where necessary.
Similarly, whether the Wi-Fi standard needs to be upgraded should also be considered in the overall outcome.
Find Bottleneck first, then decide what to buy.
Stable enterprise Wi-Fi isn't just about a faster broadband, more access points, or the latest Wi-Fi 7. The wireless environment, wired network, security equipment, client devices, and actual usage requirements all need to work together.
If the company Wi-Fi only experiences problems during peak hours, in meeting rooms, or at specific seats, you can first record the time, location, affected devices, and applications, and then schedule a targeted network check.
i-Success can help companies conduct a comprehensive inspection of their environment, from Broadband, Firewall, Switch, AP to RF, using actual data to identify the real bottlenecks, and then propose improvement plans in order of priority, avoiding blindly investing in new equipment before the cause is determined.
