Short guides to the ordinary reasons a connection changes from one run to the next.
Your provider’s advertised speed describes an access product. A browser test crosses several independently managed networks before it reaches a destination. The narrowest or busiest segment sets the observed rate.
Compare the same destination at different times before blaming the local link. Then compare a second destination to separate access problems from route-specific congestion.
Run a measured download →Radio airtime is shared. Distance, channel overlap, power saving and other clients can change a result even when the internet route is stable.
For a baseline, test over Ethernet or close to the access point. If wired and wireless results diverge, investigate the local radio path before the provider path.
Read the measurement method →There is no universal latency for a connection. Physical distance, routing policy and queueing make the round trip destination-specific.
A low idle value can coexist with poor responsiveness under load. Pathmeter’s value is a small browser-level sample, useful for comparing repeated runs to this node—not a replacement for a continuous packet-loss study.
Inspect this node →