At two in the afternoon, the director of nursing says the internet is crawling. The business office manager opens a speed test on her phone in the hallway, gets a bad number, and calls the provider. The provider runs a check on their side, says everything looks fine, and closes the ticket. Everyone is annoyed, and the problem remains.
A speed test is a useful piece of evidence, but only when it is done in a way that isolates the provider's service from everything else in your building. This is how to do that.
A speed test measures how fast data moves between your computer and a testing server, usually in both directions. It also commonly reports latency, the delay in the connection, and sometimes variation in that delay, called jitter.
It does not measure how well your charting system performs, how busy your Wi-Fi is, or whether the problem is inside your building. Those are different questions. The goal here is to test the internet service itself.
Wi-Fi adds its own problems, such as weak signal, interference and many devices sharing airtime. A test run over Wi-Fi tells you about the Wi-Fi, not the provider.
For a clean test:
Use a computer connected by a network cable, not wireless. A desktop in the business office is fine.
If possible, connect it directly to the provider's equipment or the firewall, as close to the internet connection as you can. This removes the rest of the building network from the picture.
Turn off Wi-Fi on the computer so it does not switch connections.
Close other programs, downloads, cloud backups and video calls on that computer.
Ask your IT provider whether you can briefly pause large transfers in the building, such as backups or updates, during the test.
If the wired test is good and the problem still appears over Wi-Fi, the issue is likely inside your building and not with the provider.
A problem that comes and goes needs several tests. Run one during a quiet period, such as early morning, and one during the busiest part of the day, such as mid-afternoon, and one when the problem is happening. The difference between a quiet and a busy reading can point to congestion, either on the provider's side or in your own use.
Do each test more than once, and record each. One number can be a fluke.
Build a simple log, in a spreadsheet or a shared document, with these columns:
Date and time.
Which computer and where it was connected.
Whether it was wired.
Download speed, upload speed, latency and jitter, if shown.
The test site or app used.
Whether other activity was happening in the building.
Screenshots of the results.
Include the speed you pay for, so the gap is clear. Note that actual speeds are often somewhat below the advertised figure, and many contracts describe the quoted speed as a maximum, so check what your contract promises.
Run at least two different testing tools and note which each uses. Some tests connect to a nearby server and others to a distant one. If all of them show poor speeds, that is stronger evidence than one. Your provider may also offer its own test, and it is worth running it for comparison.
Before calling, check a few things.
Restart the provider's modem or equipment, if your IT provider agrees, since it sometimes clears a fault.
Look at the lights on the equipment and note anything unusual.
Check the cable between the computer and the wall and the connection to the provider's equipment.
Check that the firewall is not overloaded or running a heavy scan.
Ask whether anything changed recently, such as new cameras, a large update or a new device.
A fault in your firewall or a bad cable can look like a provider problem.
When you contact the provider, be specific. Say that you tested from a wired computer connected directly to their equipment, give the times and results, and note the speed the account should provide. Ask for a ticket number, ask what they will test and when, and write down the name of the person you spoke to. If the contract has repair commitments, mention them.
If the problem is intermittent, ask the provider to monitor the line over several days, and ask for a technician visit.
UnityCare IT can run these tests with you, separate a provider problem from a network problem inside your building, and prepare the evidence for the provider. We can also monitor your connection over time so you have a record when you call.
Wi-Fi, switching, firewalls and internet that hold up across a whole facility.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas
Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support