The short answer
Read the test path before comparing the numbers. A router-to-internet test does not test the wifi link from your phone. A test from your phone to an internet server includes that link when the phone uses wifi.
Before you start
For people comparing home-network test results. Apps, router support and test names vary. Read the label and documentation for the tool you use.
- The name of the app or test service you already use.
- The test label and the device or router that runs it.
- A note of whether the device uses wifi, Ethernet or cellular data.
Which connection did you test?
- Device → routerA test of the local connection.
- Router → test serverA test from the router to the internet.
- Device → router → test serverA test from the device that includes the local connection.
Read the path
Device to internet
The test runs from your phone or computer to a test server. It includes the device connection, the local network and the internet path. A slow result alone does not locate the cause.
Router to internet
The router runs the test. A good result here can coexist with poor wifi in a room because your phone connection is outside this test path.
Device to router
A supported tool tests the local connection between the device and router. This can help inspect the local link, but it does not measure the complete internet path.
Using a Starlink test
Starlink documents router-to-internet and device test paths. Check which path your result names. The options you see depend on the supported equipment and app version. This article does not assume a particular menu layout.
A result from the router does not establish how well your phone works in the back bedroom. Use a device test and the actual task in that room when you want to check that experience.
Make a useful comparison
These are Wifi Bear recording steps. Keep the comparison conditions as consistent as you can.
- Record the tool, test label, connection type, time and result.
- Use the same device and test method. Keep the server the same if your tool lets you choose it.
- Run one test at a time and record other household activity.
- Keep security tools and managed-device policies in place. Note conditions that could affect the result.
- Repeat the actual task, such as the call or stream, and record what happens.
Keep the limits in view
Different tools can use different servers and methods. Do not subtract a device result from a router result to calculate a precise amount of wifi loss.
A download rate describes one part of a connection. It does not by itself explain a failed call or prove that a particular piece of equipment needs replacement.
What your result can mean
Router results look good, but a room still struggles
Inspect the device connection and compare the same device in two rooms. This is a next check, not proof of a router or mesh fault.
Two tools give different numbers
Compare their endpoints, methods and timing before treating one result as an error.
The test looks good, but the task still fails
Record the task, app and time. Keep that observation with the readings so the numbers do not replace the problem you are investigating.
Sources and further reading
- Starlink: How do I run a speed test?
Describes router and device test paths. Supported options and app layout must be checked against your equipment.
- Google: Test internet speed
Describes a router-to-server test and explains why tests with different endpoints can disagree.
- Cloudflare: The tricky science of internet measurement
Explains how test methods and competing traffic affect throughput measurements.