All troubleshooting guides

Speed seems low?

Paying for a fast plan and seeing a small number? Check the units first. Then look at active transfers and the connection from your PC to the router before deciding what to ask your provider.

Plan and transfer comparisons, with Windows and Mac wired-link checks.

By Jerrod Vick

Technical content updated

All sections in this guide

Check the number you are comparing

Bits to bytes: divide by eight
80 Mbps÷ 8 =10 MB/s

Unit conversion only, before overhead and other limits.

  1. Find the expected wired download and upload rates in your provider's plan documentation. Do not compare upload with the download headline.
  2. Check the units in the file-transfer app. Mbps means megabits per second. MB/s means megabytes per second. Eight bits make one byte.
  3. Convert the units before judging the gap. For example, 80 Mbps equals 10 MB/s before overhead and other limits.
  4. Check the scan profile. Lower data uses smaller transfers and skips upload. It cannot establish sending capacity.

Our browser check estimates transfer speed to Cloudflare. The result depends on your device, Wi-Fi, destination, and how long the test runs. This check cannot tell you your line's maximum speed.

Repeat with one condition changed

  1. Save the usual scan with its date, profile, device, and connection method noted separately.
  2. Look for a known active transfer using Resource Monitor or Activity Monitor. Pause it through its app, then repeat the same profile.
  3. If you use Wi-Fi, make the wired comparison before interpreting the plan-speed gap.
  4. If a wired estimate remains low, compare another device at a similar time. Then compare the original device at another time.
  5. Use your provider's documented test method when evaluating its expected service rate.

If only one device is consistently slower, investigate its adapter or software conditions. If several wired devices show the same repeated pattern, give that evidence to support. The scan cannot establish a contractual shortfall by itself.

Estimate a file-transfer time

In decimal units, a 1 GB file is about 8,000 megabits. Divide by the estimated Mbps to get a rough time before additional overhead.

Arithmetic examples, not performance promises
Rate1 GB transfer
20 Mbps8,000 ÷ 20 = 400 seconds, about 6 minutes 40 seconds
80 Mbps8,000 ÷ 80 = 100 seconds, about 1 minute 40 seconds

Use upload for sending a backup and download for receiving a file. Treat this as a rough planning number. Transfers speed up and slow down, services set limits, and other traffic uses some of the same capacity.

Prepare evidence for your provider

  • Expected wired rates and the provider's own test results, if available.
  • Dates, times, device, connection method, and scan profile.
  • Whether other transfers were paused and whether the pattern repeats on another wired device.
  • Capacity estimates plus idle response and added delay. Report relay loss only when observed.
"Two wired devices show lower estimates in the evening with transfers paused. Morning readings are higher. Here are the dates and comparisons. Can you investigate this pattern?"

If downloads are quick but calls or games lag, follow the responsiveness guide instead of assuming a faster plan will help.

Sources and app instructions

Can't find the menu? Your app or operating-system version may use different labels. Try the official instructions below. The example readings in this guide are made up to show you what to look for.

What to save for support

Keep the expected wired rate, repeated estimates, and conditions for each comparison. Use your provider's test method when discussing the service rate.

Save a speed comparison

Report an unclear step or an error · Data use and privacy