Work and video calls
Internet Speed Test for Work From Home: A Call-Ready Audit
Test a work-from-home connection for video meetings, VPN access, cloud work, and shared-household load with a repeatable, source-backed workflow.
Source-backed planningLoaded-latency checkVPN-safe workflow
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.
Start with concurrent work, not a universal Mbps number
- Count the work that can overlap. Add each active video meeting, remote desktop, cloud sync, software update, and household stream. A single-user minimum does not describe a busy home.
- Separate service requirements from planning headroom. Zoom currently lists 3.8 Mbps upload and 3.0 Mbps download for one 1080p Web App video endpoint, but it also adapts to network conditions. See Zoom's official requirements.
- Do not convert one platform figure into a guarantee. Microsoft says Teams consumption changes with layout, resolution, and frame rate, and that the client adapts when bandwidth is constrained. Review the current Teams network guidance for the mode your organization uses.
- Use the versioned requirements calculator to combine simultaneous activities. Its totals are planning estimates, not an application or ISP service-level promise.
A repeatable work-from-home test protocol
- 1. Record the context. Note the device, Wi-Fi or Ethernet, room, VPN state, time, active household traffic, and chosen test endpoint. Without that record, two results are hard to compare.
- 2. Establish a quiet wired baseline. When your equipment and employer policy allow it, connect the same work device by Ethernet and pause nonessential personal transfers. Do not bypass a managed gateway or workplace security control.
- 3. Repeat at the actual desk. Use the same device and endpoint over the Wi-Fi connection you normally use. Run at least two trials and compare download, upload, idle latency, loaded latency, jitter, unsuccessful probes, and confidence.
- 4. Reproduce the busy period. Retest while the normal household workload is active. Google explicitly recommends observing both bandwidth and latency over time for stable video calls in its Meet quality guidance.
- 5. Validate the application.The browser test measures one path to a test endpoint. Confirm the result with the meeting client's own network statistics, a short test call, and your employer's approved diagnostics.
Decision table: interpret the comparison before buying speed
- Wired is stable; desk Wi-Fi is not: investigate signal, interference, access-point placement, client drivers, and roaming. More ISP capacity does not repair a weak local radio path.
- Quiet tests pass; busy tests become unresponsive: identify the overlapping upload or download. Schedule backups and large syncs, then retest. If loaded latency remains high, evaluate vendor-supported queue management or more capacity.
- Only VPN-connected work is slow: repeat the same endpoint and workload, then give timestamps and results to your IT team. VPN server load, inspection, routing, protocol, and device policy can all change the path.
- Only one meeting service fails: check its status page and in-app diagnostics. A healthy generic speed test does not prove every service route is healthy.
- Every wired result is consistently weak:compare the same time-stamped evidence with the provider's plan and broadband label, check approved cabling and gateway steps, then contact the provider.
Upload, latency, jitter, and loss each answer a different question
- Download capacity supports received video, screen shares, cloud content, and concurrent household use.
- Upload capacity supports your camera, microphone, screen share, backups, and files leaving the home.
- Idle latency describes responsiveness before the connection is busy; loaded latency shows whether responsiveness collapses during transfers.
- Jitter describes variation between latency samples. Unsuccessful application probes are a diagnostic signal, not a claim about physical-line packet loss.
- Use the test confidence and run notes. A short, low-confidence browser sample should trigger a controlled retest, not a confident diagnosis.
Keep workplace security controls in the test
- Do not disable a work VPN, endpoint agent, firewall, proxy, or managed DNS merely to improve a score unless your IT team explicitly approves that comparison.
- If IT requests an A/B test, keep the device, test endpoint, time window, and background traffic as consistent as possible; change only the approved variable.
- Use an organization-provided device and approved access method for work. The NSA's current telework-focused home-network security guidance emphasizes secure devices, network segmentation, and safe telework practices.
- Save only the evidence your employer permits. A share link or exported result can expose connection details, timestamps, and notes to whoever receives it.
Fast recovery before an important meeting
- Check the meeting provider and ISP status pages before changing network settings.
- Stop nonessential personal uploads, cloud backups, game downloads, and high-bitrate streams; keep required work security software running.
- Use Ethernet when available, or move closer to the approved access point and compare the same device on the preferred band.
- If video is unstable, use the application's supported lower-quality or audio-only mode while you investigate.
- Keep a policy-approved fallback such as dial-in audio or a managed hotspot, and test it before the meeting—not during the incident.
Sources, scope, and update record
- Sources checked July 24, 2026. Platform requirements change with software, codec, layout, and policy. Follow the linked first-party documentation for current figures.
- This guide distinguishes vendor requirements, editorial planning headroom, and measured diagnostics. It does not promise that one Mbps threshold makes every meeting reliable.
- A browser test cannot certify the employer VPN, remote desktop host, meeting region, local Wi-Fi, or ISP independently. The controlled comparisons above are designed to isolate those layers.
- Run the internet quality test to compare the video-call profile with gaming, 4K streaming, and large-upload readiness from the same measured run.
- Read the measurement methodology and limitations before using results for escalation or procurement.
Retest and log improvements
Run SwiftSpeedTest after each change. Note the download, upload, and latency shifts to lock in better performance.