Copper lines have different limits
DSL performance can vary with line length, line quality, modem sync and the technology used by the provider.
Check how a DSL or VDSL-style connection performs in the areas that matter most on copper lines: downstream speed, upstream balance and latency under load.
A DSL/VDSL-focused reading for downstream, upstream and loaded response
Run the live measurement to evaluate DSL/VDSL line performance, with particular attention to downstream/upstream balance and latency on a copper-based access line.
The live measurement connects directly to Cloudflare. Results are estimates and can change with Wi‑Fi, VPNs, device load, server routing and network conditions.
DSL performance can vary with line length, line quality, modem sync and the technology used by the provider.
On asymmetric DSL services, a busy upload can increase latency sharply. That is why this result keeps upstream and loaded latency visible.
If possible, compare an Ethernet test before concluding that the DSL line is responsible for a poor wireless result.
Household capacity and busy-network performance.
Open test →Ping, jitter and connection stability.
Open test →Wireless stability, congestion symptoms and router help.
Open test →Downstream speed plus practical file download times.
Open test →Video quality, buffering risk and simultaneous streams.
Open test →Overall speed, stability and the full test family.
Open test →This page interprets the live measurements for DSL/VDSL line performance. The result gives extra weight to downstream/upstream balance and latency on a copper-based access line instead of treating every connection problem as a simple download-speed issue.
Test by ethernet, reboot the modem and compare the sync/service tier with the measured throughput. Run more than one test before drawing a conclusion because Wi-Fi conditions, local congestion, device capability and the remote network can all change a single measurement.
A speed test is a snapshot of the path between your device and the measurement service. The actual app or service may use different servers and routes, so compare this diagnosis with the real activity you are trying to improve.