Checklist
Home network speed audit checklist
Run a controlled wired, near-router, room-level, busy-network, and second-device audit to find the failing layer before buying a new plan or router.
Six-test comparisonISP vs Wi-Fi diagnosisEvidence-led retesting
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.
Prepare a reproducible audit
- Use one modern, fully charged device for the main comparisons. Record its model, operating system, browser, Wi-Fi band, and whether a VPN is active.
- Choose one SwiftSpeedTest endpoint and keep it fixed when possible. Changing endpoint location can change latency and routing.
- Pause unrelated transfers for the quiet baseline, but do not optimize away normal household traffic for the separate busy-network test.
- Record date, time, room, connection type, gateway or access point, download, upload, idle and loaded latency, jitter, unsuccessful probes, and result confidence.
- Updated July 24, 2026. This checklist now uses paired comparisons and decision rows instead of treating one whole-home Mbps score as a diagnosis.
Audit table: run these six comparisons in order
- A. ISP baseline: test by Ethernet at the primary gateway with other traffic paused. This is the cleanest browser-level comparison with the provider plan.
- B. Near-router Wi-Fi: use the same device in the same area. The A-to-B difference isolates much of the local wireless cost.
- C. Important-room Wi-Fi: test each office, bedroom, media area, or camera location. Compare C with B to expose coverage and interference.
- D. Busy-network test: repeat in the important room during ordinary household use. Compare D with C to expose contention and loaded responsiveness.
- E. Second-device control: repeat one weak result on another capable device. This separates a client problem from a room or network problem.
- F. Retest after one change: move, reconfigure, cable, or pause only one variable, then repeat the matching test. Multiple simultaneous changes destroy the evidence trail.
Decision table: identify the failing layer
- Ethernet weak; all Wi-Fi weak: inspect the gateway, modem or optical terminal, cabling, service plan, provider status, and WAN path before replacing access points.
- Ethernet good; near-router Wi-Fi weak:inspect radio settings, channel use, client capability, interference, and the gateway's Wi-Fi hardware.
- Near-router good; one room weak: treat it as coverage, building-material, placement, mesh-backhaul, or interference work—not proof that the ISP plan is too slow.
- Quiet good; busy test poor: identify uploads, streaming, cameras, game downloads, or backups one at a time. Loaded latency can reveal responsiveness loss even when Mbps remains high.
- One device weak; second device healthy:update, restart, forget and rejoin the network, inspect power-saving settings, and check that device's radio or adapter.
- Only one service fails: check its status, DNS, routing, application, and account. A healthy generic speed test does not certify every destination.
Compare the wired baseline with the plan correctly
- Find the provider's broadband consumer label. FCC labels are intended to disclose typical download, upload, and latency as well as price, fees, data allowances, and other plan information. See the FCC broadband-label fact sheet.
- Compare a capable wired device with the label's typical performance—not only a marketing phrase such as “up to.” Confirm the Ethernet port, cable, adapter, and gateway can support the plan rate.
- Collect multiple results at different times, including the period when the problem occurs. One result can be limited by a browser, device, endpoint, or temporary route.
- If the wired path repeatedly falls short, reboot only when safe, check the provider status and equipment, then save the results and plan label before contacting support.
- Do not use a browser test as a legal or regulatory certification. Follow the provider or regulator's required measurement and complaint process.
Router and Wi-Fi configuration checklist
- Place the primary access point in open air near the center of the area it serves, not inside a cabinet or behind large metal objects. Retest the exact weak room after moving it.
- Enable supported bands and use vendor-recommended channel settings. Apple recommends automatic channel selection, 20 MHz width on 2.4 GHz, and Auto or all supported widths on 5 GHz and 6 GHz in its official router settings guide.
- Use current WPA security supported by all required devices, one active DHCP server, and vendor-supported firmware. Back up the configuration before a reset or major change.
- For mesh systems, compare beside the main router and beside each node. A strong client signal with weak throughput can indicate poor wireless backhaul.
- Prefer Ethernet backhaul and wired fixed devices where practical. Add hardware only after the room-by-room comparison shows a coverage or backhaul problem.
Evidence log and pass criteria
- WAN pass:repeated wired performance is consistent with the provider's disclosed typical speeds and latency for the plan, within the limits of this browser test.
- Coverage pass: important rooms support their real activities without large unexplained degradation from the near-router result.
- Responsiveness pass:idle and loaded latency, jitter, and unsuccessful probes remain usable during the household's real busy period—not only during a quiet test.
- Device pass: a second capable device can reproduce a network problem; otherwise the first client remains the primary suspect.
- Change pass: the same test improves after one documented change and stays improved on a later retest.
Escalation and limitations
- The FCC complaint form includes speed, latency, equipment, coverage, and interference issue categories. Review the FCC internet-issue descriptions if provider support does not resolve a documented U.S. service issue.
- A browser test measures one device-to-endpoint path. It cannot see radio signal strength, channel utilization, every mesh hop, modem signal levels, or every internet destination.
- Wi-Fi performance changes with device capability, band, channel, interference, distance, building materials, access-point load, and backhaul. Avoid promising a fixed percentage of wired speed in every room.
- Read the SwiftSpeedTest methodology for the adaptive transfer protocol, confidence signals, 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.