Wi-Fi
Wi-Fi speed test for apartment living
Compare wired, near-router, room, peak-time, and second-device results to separate dense-building interference from provider, building, router, or client limits.
Five-test apartment auditOwner vs building boundariesChannel and mesh decisions
Speed TestResults
Test your internet speed
Measure download, upload, and latency instantly—no installs.
Download
—
Upload
—
Latency
—
Actionable insights
See how your results stack up for streaming, gaming, and remote work.
Run again after tweaks to confirm Wi-Fi and device improvements.
Runs in your browser. No account or download required.
Setup checklist
Get faster, steadier results
Follow these focused steps, run a fresh speed test, and compare the numbers against your goals.
There is no universal apartment Mbps target
- Plan from simultaneous activities and their current service-specific requirements, not the square footage or an invented 100–300 Mbps rule.
- A small apartment can have poor Wi-Fi because of neighboring networks, concrete, metal, mirrors, appliance interference, router placement, or a building-managed system.
- A fast plan cannot repair a weak room link. A strong Wi-Fi signal also cannot repair a slow provider or building uplink.
- Latency depends on the destination, access technology, route, and current load. Do not diagnose a shared-building network from an arbitrary apartment-wide latency threshold.
- Updated July 24, 2026. The guide now uses controlled room, time, device, and wired comparisons instead of universal plan and latency claims.
Five-test apartment workflow
- Identify whether you control the router and internet account or use a building-managed network. Record the plan, gateway, test device, connection type, and any VPN.
- Run a capable wired baseline at the gateway when an authorized Ethernet connection is available. Pause unrelated traffic and save the selected endpoint and all result metrics.
- Use the same device on Wi-Fi near the router, then in each important room. Keep the endpoint fixed when possible so distance and obstacles are the main changed variables.
- Repeat the weakest room during the actual busy period and once on a second capable device. This separates time-based congestion from a single client problem.
- After one placement, channel, access-point, or cabling change, repeat the exact failing test. Do not change several variables and then guess which one helped.
Decision table: ISP, building, Wi-Fi, or device?
- Wired baseline weak: inspect the provider or building-managed service, gateway, cabling, port speed, and current outage before replacing Wi-Fi hardware.
- Wired good; near-router Wi-Fi weak: inspect router radio settings, channel use, firmware, client compatibility, and nearby interference.
- Near-router good; one room weak:placement, walls, appliances, mirrors, access-point backhaul, or the client's band is the stronger hypothesis.
- Quiet good; evening poor everywhere: test Ethernet at the same time. If wired also falls, shared provider or building congestion is more likely; if only Wi-Fi falls, dense radio use is more likely.
- One device weak; another healthy: update and restart the client, forget and rejoin the network, inspect power-saving and radio settings, and compare supported bands.
- Mbps adequate; loaded latency degrades: pause one local upload or download at a time and retest before changing the plan.
Dense-building channel and band guidance
- Apple recommends automatic channel selection, 20 MHz channel width on 2.4 GHz, and Auto or all supported widths on 5 GHz and 6 GHz. See the Apple router settings guide.
- Do not blindly choose a channel from a one-time scan. Neighboring access points can change channels and load, and some routers coordinate automatically.
- Enable the bands supported by the router and clients instead of forcing every device onto one band. Different frequencies trade reach, wall penetration, compatibility, and available capacity.
- Do not turn off necessary legacy or smart-home devices as a general fix. Isolate, schedule, replace, or move the actual source only after a controlled test identifies it.
- Back up the router configuration and follow its vendor instructions before changing security, band, channel, width, DHCP, NAT, or firmware settings.
Router placement, mesh, and backhaul decisions
- Place an owner-controlled router in open air near the center of the served area when cabling and lease rules allow it. Avoid a closed media cabinet and large metal obstructions.
- Retest the same weak room after moving the router. Keep the new placement only if the measured room and real application improve without creating another dead zone.
- Do not assume an apartment needs mesh. A poorly placed wireless node can repeat a weak backhaul and add another radio without fixing the bottleneck.
- If one room remains weak, compare a temporary approved access-point location or wired backhaul before purchasing permanent equipment.
- In a building-managed network, do not add rogue access points, repeaters, travel routers, or unauthorized cabling. Provide the property or network operator with room, time, device, and paired evidence.
Compare the plan or building service with evidence
- FCC broadband consumer labels are designed to disclose plan price, speeds, data allowances, and network-management information. Save the provider's label and FCC fact sheet with your wired results when you control the account.
- Compare repeated capable wired tests with the plan's disclosed typical performance. A Wi-Fi room test alone is weak evidence of provider underperformance.
- For building-provided service, ask what performance is committed per unit, whether capacity is shared, which equipment is managed, and how to report a room-specific problem.
- Save date, time, room, device, band, gateway or access point, endpoint, household load, download, upload, idle and loaded latency, jitter, unsuccessful probes, and confidence.
- If a documented U.S. provider issue remains unresolved, the FCC lists speed, latency, equipment, coverage, and interference categories in its internet complaint guidance.
Limits and safe next actions
- SwiftSpeedTest measures one browser-to-selected-endpoint path. It cannot see channel utilization, signal level, every neighboring network, building backhaul, or every application destination.
- Prefer reversible, authorized changes: pause one transfer, move one device, test Ethernet, update one client, or change one documented router setting.
- Keep current Wi-Fi security and required firewall, VPN, and DNS policies. A higher benchmark is not evidence that weakening protection is safe.
- Do not enter neighbors' networks, alter building equipment, block other residents, or install unauthorized radios while diagnosing interference.
- See the SwiftSpeedTest methodology for adaptive transfers, loaded responsiveness, confidence, privacy, and known limitations.
Retest and log improvements
Run SwiftSpeedTest after each change. Note the download, upload, and latency shifts to lock in better performance.