How’s your connection doing?
Analyse your Internet connection in seconds and find out what might be slowing your network down — with, for every figure, what it lets you do.
One question before we start
How are you connected? No browser can detect this reliably, and half the advice depends on it.
About 15 seconds. The test downloads and uploads real data — expect around ten megabytes off your plan.
Worth knowing before reading the results
- La perte de paquets n’est pas mesurable depuis un navigateur.
- Le type de connexion est celui que vous indiquez, aucun navigateur ne le détecte.
- Le serveur de test est sur un autre continent : sa ville réelle est affichée avec le résultat, et la distance compte dans le temps de réponse.
Your tests will be kept here, on this device only. Nothing is sent: a connection history says where you are and at what time, and there’s no reason for us to know that. It follows this browser, not you — it won’t follow you to another phone.
How to test your connection in 3 steps
Launch the test
A few seconds of real measurements. The test data is random bytes, so compression cannot inflate your speed — the number you see is the line, not a trick.
Read the diagnosis
Every value carries its source, and the probable causes are ranked from most to least likely — always as probabilities, because no test can name a culprit with certainty.
Compare and act
Follow the suggested actions, retest right next to the router to see whether the Wi-Fi is at fault, and watch your history over time — it stays on your device.
Why use this speed test
- Packet loss cannot be measured from a browser, so this test says so instead of showing "0%". Anything that could not be measured is written, never replaced by a zero.
- Wi-Fi, router, provider or plain distance to the server: the likely causes are ranked and explained, each with a way to verify it.
- Good speed but choppy calls? The test measures response time during a download — the number classic speed tests skip, and the one that explains most call drops.
- The history is stored on your device only, your IP address is not logged or displayed, and the transferred data is random bytes generated for the test.
Frequently asked questions
Why is there no packet loss figure?
- Because a browser cannot measure it: the underlying protocol retransmits lost packets before the page ever sees them. Showing "0%" would be an invented number — this test shows interruptions of the flow instead, which are measurable.
Why does the test ask whether I am on Wi-Fi or mobile data?
- Because browsers almost never expose the real link type, and guessing gets it wrong. Declaring it lets the diagnosis keep only the advice that applies to you — no "move closer to the router" when you are on mobile data.
My latency is high but everything works — is my line bad?
- Not necessarily. The distance to the test server accounts for a large share of latency. A high but steady response time usually points to distance, not to a faulty line — the diagnosis takes that regularity into account.
What is latency under load?
- The response time measured while a download is running. It is what makes video calls stutter as soon as someone else on the connection downloads — and a classic speed test does not show it.
Are the results comparable with other speed tests?
- Only roughly: server location and load differ from one tool to another. The most useful comparison is with your own previous runs, kept in your local history.
What data is stored or sent?
- The history stays on your device. Your IP address is not displayed or logged, and the test traffic is random bytes with no personal content.
Is it free?
- Yes — no account, no signup, and no limit on how often you rerun it.