Skip to main content

What is a Good WiFi Speed for Business vs. Home?

This technical guide provides a definitive comparison between enterprise and home WiFi speed requirements, equipping IT managers and venue operators with the architectural frameworks, capacity planning metrics, and best practices needed to deploy high-density, reliable networks. It covers the full spectrum from RF design and wired infrastructure to security compliance and business ROI, with concrete implementation scenarios from hospitality, retail, and public-sector environments.

📖 9 min read📝 2,145 words🔧 2 worked examples3 practice questions📚 8 key definitions

Listen to this guide

View podcast transcript
[Intro Music fades in and out] Host: Hello and welcome to this technical briefing. Today, we are tackling a fundamental question that network architects, CTOs, and IT managers face constantly: What is a good WiFi speed for business versus home? And more importantly, how do you architect a network that actually delivers it consistently under load? Over the next ten minutes, we are going to bypass the marketing fluff and dive straight into the technical realities of enterprise deployments. Host: Let us start with the context. When a consumer asks about a good WiFi speed, they are usually talking about raw throughput to a single device. Can they stream 4K video or download a game quickly? They might buy a gigabit connection and a high-end consumer router, and for a household of four, that is more than enough. But when an IT director at a 200-room hotel or a stadium operations manager asks the same question, the paradigm shifts entirely. Host: In the enterprise space, speed is a composite metric. It is not just about the ISP pipe. It is about aggregate throughput, client density, airtime fairness, and latency. A consumer router might boast 3 Gigabits per second on the box, but if you put 50 active clients on it, it will collapse due to CPU exhaustion and airtime contention. Enterprise access points, on the other hand, are engineered for high-density environments. They use advanced chipsets, sophisticated antenna arrays, and protocols like MU-MIMO and OFDMA to manage hundreds of concurrent connections efficiently. Host: So, what is a good speed? For a home user, 25 to 50 Megabits per second per device is excellent. For a business, the answer depends heavily on the use case. If you are deploying Guest WiFi in a retail environment or a hospitality venue, you typically want to provision between 10 to 30 Megabits per second per user. This allows for smooth browsing, social media, and video calls without allowing a single user to hog the bandwidth. For back-office operations, POS systems, and IoT devices, the bandwidth requirement per device might actually be lower, often just 1 to 5 Megabits per second, but the requirement for reliability and low latency is absolute. Host: Now, let us talk about the technical deep dive. How do you ensure those speeds are actually delivered? The first major hurdle is co-channel interference. In a high-density deployment, if you simply blast signal everywhere on maximum power, your access points will interfere with each other. This is known as co-channel interference, or CCI. To resolve CCI, you need careful channel planning, often leveraging dynamic radio management to adjust power levels and channel assignments on the fly. You should also be pushing clients towards the 5 GHz and 6 GHz bands wherever possible, leaving the congested 2.4 GHz band for legacy devices and IoT sensors. Host: Another critical factor is the underlying infrastructure. You can have the best WiFi 6E access points in the world, but if they are connected to a 1 Gigabit switch port, or if your Power over Ethernet budget is insufficient, you are going to create a bottleneck. Enterprise deployments require multi-gigabit switches, often supporting 2.5 or 5 Gigabits per second per port, and robust PoE-plus or PoE-plus-plus capabilities to power modern access points fully. Host: Let us move to implementation recommendations and common pitfalls. The most common mistake we see is the coverage-only design. An architect looks at a floor plan, draws circles around access points, and ensures there are no dead zones. But in a modern enterprise, you do not design for coverage. You design for capacity. You need to calculate the expected number of devices per zone and deploy enough access points to handle that density, even if it means turning the transmit power down to minimise interference. Host: Another pitfall is ignoring the authentication and onboarding process. If it takes a user two minutes to navigate a clunky captive portal, they will perceive the WiFi as slow, regardless of the actual throughput. This is where platforms like Purple's Guest WiFi come in. By streamlining the onboarding process and integrating seamlessly with your hardware, you not only improve the perceived speed and user experience but also capture valuable first-party data. And for seamless, secure onboarding, leveraging technologies like OpenRoaming, where Purple acts as a free identity provider, can completely eliminate the friction of captive portals for returning users. Host: Alright, let us move into our rapid-fire Q&A segment. Host: Question one: Is WiFi 6 really necessary for a standard office? Answer: Yes. While the raw top speed might not be critical for every user, the efficiency gains from OFDMA in WiFi 6 are crucial for high-density environments, significantly reducing latency when many devices are active simultaneously. Host: Question two: How much bandwidth should I allocate for guest WiFi? Answer: A good rule of thumb is to cap guest speeds at 10 to 20 Megabits per second per device using rate limiting. This ensures a good experience for the guest while protecting your core business operations from bandwidth hogs. Host: Question three: Can I use mesh WiFi in an enterprise setting? Answer: Generally, no. Mesh introduces latency and halves throughput with every hop. In an enterprise environment, every access point should have a dedicated wired backhaul. Host: To summarise and look at next steps: A good WiFi speed in an enterprise context is about consistent, reliable capacity, not just peak throughput. It requires careful RF planning, robust wired infrastructure, and intelligent management platforms. If you are evaluating your network requirements, start by auditing your current client density and mapping out your capacity needs, not just your coverage area. Host: Thank you for joining this technical briefing. For more deep dives into enterprise networking, be sure to check out our comprehensive guides on resolving co-channel interference and optimising your modern office network. Until next time. [Outro Music fades in and out]

Executive Summary

header_image.png

When evaluating what constitutes a good WiFi speed, the answer diverges sharply between residential and enterprise contexts. A home user measures speed by peak throughput to a single device; an enterprise measures it by aggregate capacity, airtime efficiency, and consistent latency across hundreds of concurrent clients. For CTOs, IT managers, and venue operations directors, deploying a high-performance network is not merely an infrastructure upgrade — it is a strategic enablement tool that directly impacts guest satisfaction, operational efficiency, and revenue generation.

Whether you are supporting POS systems in Retail , seamless guest experiences in Hospitality , critical life-safety devices in Healthcare , or high-turnover passenger connectivity in Transport , the network must be engineered for density and reliability, not just coverage. This guide provides the technical frameworks required to architect, deploy, and manage enterprise-grade WiFi networks that meet stringent SLA requirements while delivering measurable business value.


Technical Deep-Dive: Architecture and Standards

The Capacity vs. Coverage Paradigm

The most fundamental mistake in enterprise WiFi design is conflating coverage with capacity. In a home environment, the primary goal is coverage — eliminating dead zones so that every device in the building has a signal. In an enterprise environment, particularly in high-density venues such as conference centres, hotel lobbies, or retail floors, the primary goal is capacity. A venue may have excellent signal strength (RSSI of -55 dBm or better) at every point in the building, yet users experience slow speeds and high latency because the channel is saturated.

This is the core distinction: coverage is about signal; capacity is about throughput under concurrent load. A modern enterprise access point can theoretically deliver 9.6 Gbps aggregate throughput under WiFi 6 (802.11ax), but that figure is meaningless if the RF environment is poorly designed. In practice, a single AP in a high-density environment may serve 50-80 active clients simultaneously, and the actual per-client throughput will depend on channel utilisation, interference levels, and the efficiency of the MAC layer scheduling.

WiFi Standards and Their Enterprise Implications

The choice of WiFi standard has direct implications for enterprise performance. WiFi 5 (802.11ac Wave 2) introduced MU-MIMO for downlink, allowing APs to serve multiple clients simultaneously on separate spatial streams. WiFi 6 (802.11ax) built on this with OFDMA, BSS Coloring, and Target Wake Time (TWT), addressing the core challenges of high-density deployments. WiFi 6E extended the 802.11ax protocol into the 6 GHz band, providing access to up to 1,200 MHz of additional spectrum — a significant advantage for congested urban deployments.

For a comprehensive breakdown of frequency bands and their enterprise applications, refer to our guide on Wi Fi Frequencies: A Guide to Wi-Fi Frequencies in 2026 .

Standard Max Theoretical Speed Key Enterprise Feature Recommended Deployment
WiFi 5 (802.11ac) 3.5 Gbps Downlink MU-MIMO Legacy refresh, low-density
WiFi 6 (802.11ax) 9.6 Gbps OFDMA, BSS Coloring Standard enterprise deployments
WiFi 6E 9.6 Gbps + 6 GHz 6 GHz spectrum access High-density, urban venues
WiFi 7 (802.11be) 46 Gbps Multi-Link Operation Future-proofing, emerging

Bandwidth Requirements: Home vs. Business

The raw throughput required per device often surprises IT professionals transitioning from consumer to enterprise networking. The table below provides a practical reference for capacity planning.

comparison_chart.png

For enterprise deployments, the critical metric is not the per-device figure in isolation, but the aggregate demand calculation: multiply the per-device allocation by the Maximum Concurrent Users (MCU) for each zone, then add a 30-40% headroom buffer for burst traffic and future growth. A conference room with 50 attendees all on video calls simultaneously requires a minimum of 750 Mbps of available capacity from the APs serving that zone, before factoring in overhead.

Co-Channel Interference: The Primary Performance Killer

Co-channel interference (CCI) is the single most common cause of poor enterprise WiFi performance. It occurs when multiple access points transmit on the same frequency channel and can hear each other. Because WiFi uses CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance), all APs on the same channel must wait for the channel to be clear before transmitting. In a dense deployment with many APs on the same channel, this creates a situation where the effective throughput per AP drops dramatically, even though the signal strength is excellent.

The 2.4 GHz band has only three non-overlapping 20 MHz channels (1, 6, and 11), making it extremely susceptible to CCI in dense deployments. The 5 GHz band offers up to 25 non-overlapping channels (depending on regulatory domain), and the 6 GHz band provides up to 59 non-overlapping 20 MHz channels, making these bands far more suitable for high-density enterprise use. For detailed guidance on resolving CCI in your deployment, see our guide on Resolving Co-Channel Interference in Enterprise Deployments .


Implementation Guide

venue_deployment_diagram.png

Step 1: Capacity Planning and RF Design

Begin with a detailed capacity plan before touching any hardware. Identify all zones within the venue, estimate the MCU per zone during peak load, and calculate the required aggregate throughput per zone. For hospitality environments, peak load typically occurs during breakfast service, check-in periods, and conference sessions. For retail, it is typically weekday lunchtimes and weekend afternoons.

Conduct an active RF site survey using professional tools (such as Ekahau or iBwave) to measure actual RF propagation, identify sources of interference (neighbouring networks, Bluetooth devices, microwave ovens), and model the impact of building materials on signal attenuation. Do not rely solely on predictive surveys based on floor plans; actual building materials frequently differ from architectural drawings.

For high-density areas such as auditoriums, exhibition halls, or stadium concourses, consider deploying directional antennas (patch or sector antennas) to create focused micro-cells. This approach reduces the contention domain per AP and allows you to serve more users with consistent throughput. For further guidance on office environments specifically, see Office Wi Fi: Optimize Your Modern Office Wi-Fi Network .

Step 2: Wired Infrastructure Readiness

The wireless network is only as fast as the wired backhaul. This is a frequently overlooked constraint: deploying WiFi 6E access points capable of multi-gigabit aggregate throughput on 1 Gbps switch ports creates an immediate bottleneck. Modern enterprise deployments require Multi-Gigabit Ethernet switching infrastructure, with 2.5 Gbps or 5 Gbps uplinks per AP in high-density zones.

Power over Ethernet (PoE) budgeting is equally critical. Modern 4x4:4 WiFi 6E access points with all radios active can draw 25-30W, requiring PoE+ (IEEE 802.3at, 30W) or PoE++ (IEEE 802.3bt, 60W) switch ports. Deploying a high-end AP on a standard PoE (802.3af, 15.4W) port will cause the AP to disable one or more radios to stay within the power budget, directly reducing capacity.

Step 3: Network Segmentation and Security

Enterprise networks must implement strict traffic segmentation. At minimum, the following VLANs should be defined and enforced:

  • Corporate VLAN: Internal staff devices, with full access to business systems. Protected by 802.1X authentication (WPA3-Enterprise).
  • Guest WiFi VLAN: Visitor devices, with internet-only access. Isolated from all corporate subnets via firewall rules. Rate-limited per device.
  • IoT VLAN: Sensors, cameras, building management systems. Isolated from both corporate and guest networks.
  • POS/Payment VLAN: Point-of-sale terminals. Strictly isolated and subject to PCI DSS compliance requirements.

For Guest WiFi deployments, client isolation must be enabled on the AP to prevent guest devices from communicating directly with each other, mitigating peer-to-peer attack vectors. DHCP lease times on the guest VLAN should be reduced to 30-60 minutes to prevent pool exhaustion in high-turnover environments.

Step 4: Authentication and Onboarding

The onboarding experience is a direct contributor to perceived network performance. A user who waits 90 seconds for a captive portal to load will report the WiFi as "slow" regardless of the actual throughput. Implementing Purple's Guest WiFi platform streamlines this process, providing a branded, fast-loading captive portal that captures first-party data for marketing purposes while maintaining compliance with GDPR and local data privacy regulations.

For venues seeking to eliminate captive portals entirely for returning users, OpenRoaming provides a standards-based solution. Under Purple's Connect licence, Purple acts as a free identity provider for the OpenRoaming federation, allowing users who have previously authenticated to reconnect automatically and securely across all participating venues. This is particularly valuable in transport hubs, retail chains, and hospitality groups with multiple properties.


Best Practices

The following vendor-neutral best practices represent the current industry consensus for enterprise WiFi deployments.

Disable Legacy Data Rates. The 802.11 standard requires all clients to be able to communicate at the lowest enabled data rate. If 1 Mbps is enabled, a client at the edge of the cell will transmit at 1 Mbps, consuming 54 times more airtime than a client at 54 Mbps. Disabling rates below 12 Mbps (or 24 Mbps in high-density environments) forces clients to roam to a closer AP, improving both their own performance and the overall efficiency of the network.

Implement Minimum RSSI Thresholds. Configure APs to refuse associations from clients with an RSSI below -75 dBm (or -70 dBm in very dense deployments). This solves the "sticky client" problem, where devices hold onto a weak connection to a distant AP rather than roaming to a closer one.

Enable Airtime Fairness. Without airtime fairness, a legacy 802.11b device connecting at 11 Mbps receives the same number of transmission frames as a modern 802.11ax device at 1 Gbps, but takes 90 times longer to transmit each frame. Airtime fairness allocates equal transmission time rather than equal frames, protecting fast clients from being dragged down by slow ones.

Leverage Purple's WiFi Analytics. Deploying WiFi Analytics alongside your network infrastructure provides real-time visibility into client density, roaming patterns, and bandwidth utilisation per zone. This data is invaluable for identifying capacity bottlenecks before they impact user experience and for optimising AP placement during post-deployment surveys.

Integrate BLE for Supplementary Location Services. For venues requiring granular indoor positioning beyond WiFi's typical 5-10 metre accuracy, integrating Bluetooth Low Energy beacons provides sub-metre accuracy for wayfinding and asset tracking. For a technical overview of BLE in enterprise environments, see BLE Low Energy Explained for Enterprise .


Troubleshooting & Risk Mitigation

Common Failure Modes

The Sticky Client Problem. Devices maintain a weak connection to a distant AP, consuming airtime at low data rates and degrading performance for all other clients on that AP. This is typically caused by missing minimum RSSI thresholds or disabled 802.11k/v/r roaming assistance. Mitigation: enable 802.11r (Fast BSS Transition) for seamless roaming, 802.11k (Neighbour Reports) to inform clients of nearby APs, and 802.11v (BSS Transition Management) to actively request clients to roam.

DHCP Pool Exhaustion. In high-turnover environments such as transport hubs or retail stores, the DHCP pool can deplete within hours if lease times are set to the default 24 hours. Mitigation: reduce DHCP lease times to 30-60 minutes on guest VLANs, and size the DHCP pool to accommodate at least 3x the expected MCU to account for devices that disconnect without releasing their lease.

Captive Portal Redirect Failures. Users report being unable to access the captive portal, perceiving the network as broken. This is typically caused by DNS misconfiguration, HTTPS-only browsing behaviour (HSTS), or overly aggressive firewall rules blocking the redirect. Mitigation: ensure the DHCP server provides a DNS address that resolves to the captive portal controller, and configure the firewall to permit HTTP traffic to the portal IP before authentication.

Rogue Access Points. Unauthorised APs connected to the wired network or operating in the RF environment represent both a security risk and a source of interference. Mitigation: deploy a WIPS (Wireless Intrusion Prevention System) and conduct regular RF audits. Implement 802.1X on all switch ports to prevent unauthorised devices from obtaining network access.


ROI & Business Impact

A robust enterprise WiFi network is a foundational asset that drives measurable ROI across multiple dimensions. The direct cost of poor WiFi — guest complaints, staff productivity loss, and failed transactions — is quantifiable. A 2023 study by Hospitality Technology found that 67% of hotel guests rated WiFi quality as the most important in-room amenity, ahead of breakfast and parking. In retail, network downtime directly impacts POS transaction throughput and, in environments with digital signage, advertising revenue.

Beyond connectivity, the network is a data collection platform. By integrating with Purple's WiFi Analytics , venues can capture first-party data at the point of onboarding, understand footfall patterns through presence analytics, and deliver targeted marketing campaigns based on visit frequency and dwell time. For a 500-location retail chain, even a modest 2% uplift in repeat visit frequency driven by personalised WiFi-triggered campaigns represents a significant revenue impact.

The compliance dimension also carries financial weight. GDPR violations related to improper data collection through captive portals can result in fines of up to 4% of global annual turnover. Deploying a compliant, auditable onboarding platform from the outset is materially cheaper than remediating a non-compliant deployment after a regulatory investigation.

Key Definitions

Airtime Fairness

A scheduling mechanism that allocates equal transmission time to all clients, rather than equal data frames. This prevents older, slower devices from monopolising the access point and degrading performance for faster, modern clients.

Critical in mixed-device environments like public venues and hotels, ensuring that a legacy 802.11g smartphone does not cripple the network experience for modern 802.11ax laptops.

Co-Channel Interference (CCI)

Occurs when multiple access points transmit on the same frequency channel and can hear each other above the CCA (Clear Channel Assessment) threshold. Under CSMA/CA, they must each wait for the channel to be clear before transmitting, effectively reducing the aggregate capacity of all APs on that channel.

The primary cause of slow WiFi in high-density deployments where APs are placed too close together or transmit power is set too high.

OFDMA (Orthogonal Frequency-Division Multiple Access)

A technology introduced in WiFi 6 (802.11ax) that subdivides a channel into smaller resource units (RUs), allowing an access point to transmit data to multiple clients simultaneously within a single transmission opportunity.

Essential for reducing latency and improving efficiency in environments with many small-packet workloads, such as VoIP calls, IoT sensor data, and web browsing.

Rate Limiting

The practice of capping the maximum upload and download bandwidth available to an individual user or device, typically enforced at the AP or RADIUS server level.

Used in Guest WiFi deployments to ensure equitable distribution of the internet connection and prevent a single user from saturating the shared backhaul with large downloads.

BSS Coloring

A spatial reuse technique in WiFi 6 that adds a numerical colour identifier to all 802.11ax transmissions. If an AP detects traffic on its channel from a different BSS colour and the signal is below a defined threshold, it can classify the channel as clear and transmit anyway, increasing spatial reuse.

Particularly valuable in ultra-dense deployments such as stadiums, conference halls, or multi-tenant office buildings where many independent networks share the same RF space.

Minimum RSSI

A configuration parameter that instructs an access point to refuse or terminate a client association if the received signal strength falls below a defined threshold (e.g., -75 dBm).

The primary tool for solving the sticky client problem, ensuring that devices roam to a closer AP rather than maintaining a weak, low-throughput connection to a distant one.

OpenRoaming

A Wireless Broadband Alliance (WBA) federation standard that enables automatic, secure WiFi connectivity across participating networks using existing credentials (e.g., mobile operator SIM, social login, or enterprise identity), without requiring manual captive portal authentication.

Provides a seamless, secure onboarding experience for returning users across multi-site deployments. Purple acts as a free identity provider for OpenRoaming under the Connect licence.

PoE++ (IEEE 802.3bt)

The latest Power over Ethernet standard, delivering up to 60W (Type 3) or 90W (Type 4) of DC power over standard Ethernet cabling. Required to power modern high-density WiFi 6E access points with all radios operating at full capacity.

Deploying a PoE++ AP on a standard PoE (802.3af, 15.4W) port will cause the AP to throttle its radio output, directly reducing capacity. Always verify PoE budget before deployment.

Worked Examples

A 300-room luxury hotel is upgrading its network. The current setup has one AP in the hallway for every four rooms, resulting in persistent complaints about slow speeds and dropped video calls, despite a 2 Gbps internet circuit.

The issue is not the ISP circuit but the RF design and capacity model. Hallway deployments cause APs to hear each other loudly (CCI) while struggling to penetrate heavy fire-rated room doors. The solution is an in-room deployment model. Install a wall-plate AP in every room (or every other room, depending on wall attenuation measurements from the site survey). Reduce transmit power to limit the cell size to the immediate room. Enable client steering to push devices to 5 GHz. Implement per-device rate limiting at 20 Mbps down / 5 Mbps up to ensure equitable distribution of the 2 Gbps backhaul across all 300 rooms. Deploy Purple's Guest WiFi captive portal for GDPR-compliant onboarding and first-party data capture. Configure 802.11k/v/r to ensure seamless roaming for guests moving between their room, the lobby, and the restaurant.

Examiner's Commentary: This approach shifts the design from coverage-centric to capacity-centric. Moving APs into rooms eliminates the attenuation of fire-rated doors for the client device, while those same walls now isolate APs from each other, drastically reducing CCI. The rate limiting protects aggregate bandwidth from individual heavy users. The 802.11k/v/r configuration ensures that the guest experience is seamless as they move around the property — a critical factor in hospitality where a dropped video call in the lobby is a direct service failure.

A large retail chain wants to deploy Guest WiFi across 500 stores to capture customer data and provide in-store navigation, but the IT security team is concerned about the PCI DSS compliance implications of having public devices on the same physical network infrastructure as POS terminals.

Implement a strictly segmented network architecture using VLANs enforced at the switch level. Create a dedicated Guest WiFi VLAN that is completely isolated from the POS VLAN via firewall rules denying all inter-VLAN traffic. The POS VLAN should be treated as a PCI DSS Cardholder Data Environment (CDE) and subject to all relevant controls including network access control, encryption in transit, and quarterly vulnerability scans. The Guest WiFi VLAN should use Purple's captive portal for GDPR-compliant data capture, with client isolation enabled to prevent peer-to-peer attacks between guest devices. Implement rate limiting at 15 Mbps per device. Deploy Purple's WiFi Analytics to capture footfall data and dwell time metrics for each store, feeding into the retail marketing platform.

Examiner's Commentary: The key insight here is that physical network sharing does not imply logical network sharing. VLANs with enforced firewall rules provide the necessary isolation for PCI DSS compliance, provided the firewall rules are correctly configured and regularly audited. Client isolation is a critical, often overlooked step that prevents lateral movement between compromised guest devices. The Purple analytics layer transforms the WiFi infrastructure from a cost centre into a revenue-generating data asset.

Practice Questions

Q1. You are deploying a network in a high-density university lecture theatre that seats 400 students. You have a 1 Gbps internet connection. How should you approach the AP deployment and configuration to ensure stable performance during a lecture where all students are simultaneously accessing online course portals and streaming lecture content?

Hint: Consider the limitations of a single AP's capacity, the risk of CCI in an open space, and the impact of legacy data rates on airtime efficiency.

View model answer

Deploy multiple high-density WiFi 6 or 6E APs with directional patch antennas to create focused micro-cells within the theatre, minimising CCI. Disable 2.4 GHz radios on all APs to eliminate the three-channel constraint, relying entirely on 5 GHz and 6 GHz. Disable legacy data rates below 12 Mbps. Implement per-device rate limiting at 5-10 Mbps to prevent a minority of heavy users from saturating the 1 Gbps backhaul. Enable OFDMA and MU-MIMO. Configure minimum RSSI thresholds at -70 dBm to prevent sticky clients. Calculate: 400 students at 5 Mbps each requires 2 Gbps aggregate, so the 1 Gbps circuit will be the bottleneck — recommend upgrading the ISP circuit to 2-3 Gbps or implementing QoS policies to prioritise course portal traffic.

Q2. A client complains that their new enterprise WiFi network is slower than their home router. They are testing speeds using a single laptop connected to an AP that is currently serving 80 other active clients in a busy open-plan office.

Hint: Explain the difference between peak single-client throughput and aggregate AP capacity, and how consumer vs enterprise APs are optimised differently.

View model answer

Explain that consumer routers are optimised to provide maximum peak throughput to a single device in a low-density, low-interference environment. Enterprise APs are optimised for aggregate capacity, airtime fairness, and consistent performance across many concurrent devices. While a single speed test on an enterprise AP may show lower peak numbers than a home router in an empty room, the enterprise AP is simultaneously maintaining stable, low-latency connections for 80 concurrent users — a load that would cause a consumer router to crash or degrade severely. The network is performing correctly; the comparison methodology is flawed. Recommend conducting the speed test during off-peak hours to establish the true single-client peak throughput.

Q3. During a post-deployment survey in a warehouse with 30 APs deployed, you observe high channel utilisation (over 65%) on the 2.4 GHz band across all APs, even during periods when very few client devices are actively transmitting data. What is the most likely cause and how do you resolve it?

Hint: Consider management traffic, beacon frames, and the relationship between data rate and airtime consumption.

View model answer

The high utilisation is almost certainly caused by management overhead, specifically beacon frames being transmitted at the lowest mandatory data rate (1 Mbps) by all 30 APs, which can all hear each other. Each beacon consumes 54 times more airtime at 1 Mbps than it would at 54 Mbps. With 30 APs each beaconing every 100ms on the same three 2.4 GHz channels, the cumulative management overhead can easily consume 50-70% of available airtime. Resolution: disable legacy data rates (1, 2, 5.5, 11 Mbps) on all 2.4 GHz radios, which forces beacons to be transmitted at higher rates. Additionally, review the channel plan and reduce transmit power on 2.4 GHz radios to reduce the number of APs that can hear each other. Consider disabling 2.4 GHz entirely on APs that are within 10 metres of another AP.