Record the problem times, locations and clients first. Establish a wired baseline on the same network, then examine wireless, service-layer and application issues separately. Compare results under the same conditions after each change.
01 · Describe the problem precisely
- What time, and which room or aisle?
- One client, clients of the same type, or all devices?
- Slow performance, packet loss, AP switching, repeated login or no internet access at all?
- Does it occur only at full occupancy, with full stock, while equipment is running or after renovations?
02 · Separate wired, wireless and internet issues
First check whether wired connectivity is affected, then compare the local network with the internet. If both are slow, check cabling, switches and services; if the issue occurs only in a particular wireless area, investigate that area's APs, clients and RF data.
03 · Examine Signal, Capacity and Interference Together
Collect RSSI, SNR, channel utilisation, retries and AP logs. Non-Wi-Fi interference needs suitable spectrum measurements; an ordinary scanner may not identify it fully. Align the data with fault times rather than relying on a heatmap from a single moment.
Browse 48 common factors →04 · Walk a route with the actual client
Use actual scanners in warehouses and actual computers and applications for meetings, recording AP changes, authentication, packet loss and reconnection. Good performance at a fixed position does not ensure application continuity while moving.
05 · Validate changes under the same conditions
Record the original configuration, every change and the test results. Agree the scope, load, clients and acceptable performance. Reports should distinguish observations, suspected causes and items still requiring confirmation.
Before a survey, you may provide a floor plan with sensitive information removed, AP models and fault records. Do not include passwords, complete account details or personal information in public enquiry content.
Common questions
If a phone's speed test is normal, does that mean a scanner is also working properly?
You cannot assume that. Clients differ in bands, antennas, drivers, roaming and application needs. Test with the actual affected equipment.
Will buying more APs first solve the problem?
Identify the bottleneck first. Excessively dense AP deployment with poor channel planning may also increase same-channel sharing; assess additional equipment together with placement, channels and uplinks.
Sources and updates
Regulatory requirements and technical references are checked separately. The following engineering checks are compiled by WiFi-HK and do not imply endorsement by regulators or equipment brands.
- Cisco Meraki | Wireless troubleshooting ↗
- Cisco | WLAN Site Survey Guidelines ↗
- Cisco Meraki | SNR and Signal Strength ↗
Information verified: 10 October 2026 (Hong Kong time). Regulations and equipment requirements may change; check the formal specifications again before procurement and installation.
Turn knowledge into site improvements
Bring the problem locations, times, device models and floor plan to discuss the survey, AP planning and acceptance scope.