How to Test Your Business Internet Connection Before Installing VoIP

Key Takeaways

• A standard speed test only tells part of the story — latency, jitter, and packet loss are equally important for VoIP readiness
• Test during peak business hours, not at midnight, to get results that reflect real working conditions
• Running the test on a wired connection (not Wi-Fi) gives you the most accurate baseline
• A full network assessment from Vistanet covers everything a DIY speed test doesn’t — and it’s included free with the needs analysis

Before switching to a VoIP phone system, it’s worth spending 15 minutes testing your current internet connection. Not because the results will always be alarming — many businesses already have perfectly adequate connections — but because discovering a problem before installation is much less disruptive than discovering it after.

This guide walks through how to run a meaningful internet test, what the results mean, and what to do if the numbers suggest a problem.

Why a Basic Speed Test Isn’t Enough

Most people have run a speed test before. You go to a website, click a button, and see a download speed, an upload speed, and a ping number. If the download speed looks close to what your provider advertises, you close the tab and assume everything is fine.

That approach misses the factors that matter most for VoIP call quality.

VoIP calls are real-time communication. Voice data packets must arrive consistently, in sequence, with minimal delay. A fast internet connection that delivers packets in unpredictable bursts — or that performs well at 10 p.m. but struggles at 10 a.m. — will produce poor call quality regardless of the peak speed number.

The four things to measure are:

• Download speed (matters, but less than you’d think for VoIP)
• Upload speed (often the real bottleneck, especially on cable)
• Latency / ping (target: under 100ms; ideal: under 50ms)
• Jitter (the variation in latency; target: under 30ms)
• Packet loss (target: 0%; tolerable: under 0.5%)

A standard speed test from speedtest.net gives you download speed, upload speed, and a single ping number. For a complete VoIP readiness assessment, you’ll want more — but the speed test is a legitimate starting point.

Step-by-Step: Running a Meaningful Test

Step 1: Use a wired connection

Plug your test device directly into your router or network switch using an Ethernet cable. Wi-Fi adds a layer of radio transmission between your device and your router that can mask problems with the internet connection itself — or create its own jitter and packet loss. Test on wire first. You can test on Wi-Fi separately if you want to understand the wireless experience, but the wired result is your baseline.

Step 2: Test during peak hours

This is the most important step most people skip. Run your test at the busiest time of your typical workday — often mid-morning or just after lunch. If you’re on a cable connection, you’re sharing bandwidth with neighboring businesses and residences. Peak-hour congestion can cut your available speed in half. Testing at midnight gives you a number that tells you nothing about how your connection performs when your team and your customers depend on it.

Step 3: Test multiple times

Run the test at least three to five times during that peak window and average the results. A single test can be skewed by temporary conditions. Multiple runs give you a more accurate picture of typical performance.

Step 4: Record what you find

Write down or screenshot your results each time: download speed, upload speed, ping, and jitter if your test tool shows it. You’ll want these numbers to compare against later, and they’re useful context if you call your provider about a problem.

Interpreting Your Results

Upload speed

This is the most important number for VoIP. Each active phone call uses approximately 85 to 100 Kbps of upload bandwidth. More importantly, everything your team does that sends data outbound — file uploads, cloud backups, video calls — draws from this pool.

If your upload speed is below 10 Mbps and your team makes multiple simultaneous calls, you may already be running close to capacity. Below 5 Mbps upload is a clear problem for most business phone systems.

Latency / ping

This measures how long it takes a data packet to make a round trip to a test server. For VoIP:

• Under 50ms: Good. Callers won’t notice any delay
• 50 to 100ms: Acceptable for most calls
• Above 100ms: Risk zone — some callers will notice delay
• Above 150ms: Consistently noticeable — calls feel like talking on a satellite phone

If your latency is above 100ms to a server that’s geographically nearby, that’s worth investigating before going live with VoIP.

Jitter

Not all speed test tools report jitter. Speedtest.net shows it; others don’t. Jitter measures how consistent your latency is from packet to packet. High jitter produces robotic, choppy audio even when average latency looks acceptable.

Target: under 30ms. Above 50ms jitter will produce noticeable audio problems.

Packet loss

Basic speed tests don’t measure packet loss directly. For a packet loss measurement, you need a tool like PingPlotter, WinMTR, or an online VoIP quality test (several are available free; search “VoIP quality test”).

Target: 0%. Any consistent packet loss above 0.5% will affect call audio. Above 1 to 2% makes calls difficult. If you’re seeing regular packet loss, something is wrong — with your connection, your internal network, or both.

What to Do If the Numbers Suggest a Problem

Upload speed is too low

If you’re on a cable plan and upload speeds are consistently below 20 Mbps, you have two options: upgrade your plan (often to a higher tier or a business fiber option) or work with your phone system provider to configure Quality of Service settings that prioritize voice traffic over other data. QoS won’t create bandwidth you don’t have, but it will ensure calls get priority when the connection is under load.

Latency is too high

High latency to a nearby test server usually indicates a problem with your ISP’s network or your internal routing. Check whether the high latency is consistent across multiple servers and time periods. If it is, contact your provider. If it varies, your router configuration may be the issue.

Jitter is high

High jitter is almost always a QoS configuration problem, a congested network, or a physical issue with cabling. If you’re on Wi-Fi, switch to a wired connection and retest. If jitter is high on a wired connection, your router may need configuration updates, or there may be a physical layer problem your ISP needs to address.

Packet loss is present

Any consistent packet loss is a problem. Start by testing at the router level (connect directly to the router, bypassing any internal switches or Wi-Fi). If packet loss persists, the problem is with the connection from your ISP. If it disappears at the router level, the problem is inside your building.

When to Call Vistanet Instead of DIYing It

The tests above give you a working picture of your connection. What they don’t give you is a professional network assessment that looks at your router configuration, internal network topology, number of devices, call volume patterns, and how everything fits together.

That’s what Vistanet’s needs analysis includes. Before installing any business phone system, the team evaluates your full network environment — not just the internet speed — and identifies anything that would interfere with clean call quality. If the internet needs to be upgraded or reconfigured, that happens before the phones go in, not after.

The assessment is free, and it takes less time than diagnosing call quality problems after the fact.

Request a free needs analysis to get started.

Frequently Asked Questions

What speed test tool should I use?

Speedtest.net (by Ookla) is the most widely used and gives reliable results for download speed, upload speed, latency, and jitter. Fast.com (by Netflix) is good for download speed but doesn’t report jitter. For packet loss testing, PingPlotter is a more sophisticated option that shows network behavior over time.

Should I test with all my devices connected or just one?

Both. Test with one device connected directly to the router via Ethernet to get your best-case baseline. Then test again with your normal office load — all computers, phones, and other devices on the network as they would be during a typical workday. The difference between the two results tells you how much your existing network load is affecting your available bandwidth.

My provider says my speeds are fine. Why are my calls still choppy?

Speed is only one factor. High jitter, elevated latency, or packet loss can cause call problems even when download and upload speeds look healthy. A full network assessment that measures all four factors will usually identify the actual cause.

Can I run these tests myself before calling Vistanet?

Absolutely, and the results are useful context to bring to the conversation. Knowing your current upload speed and latency helps the needs analysis move faster — you’re starting with data rather than symptoms. If the tests reveal a clear problem, you’ll already know what to ask your provider about.

Is there a difference between testing from a laptop vs. a VoIP phone?

Yes. VoIP desk phones and wireless handsets don’t have built-in speed test tools, so you test from a computer on the same network. The results reflect the connection quality available to all devices on that network, including your phones. If your computer tests show good results but calls are still poor, the problem may be in how your network is managing traffic — a QoS configuration issue rather than a raw speed problem.