CNMC speed test: what it measures and what it does not prove

The National Commission on Markets and Competition (CNMC) provides an Internet speed test on its telecommunications quality portal. Its clearest value is practical: it lets you measure the connection you are using and consult information about results generated by people who run tests. It is not, by itself, a certificate that an operator has or has not met the terms of a contract. Its role is to provide a measurement and information that can help put that measurement in context, rather than to settle a contractual dispute automatically.

That distinction matters because a speed test answers a limited question: what performance was recorded during one particular session? It does not automatically answer other questions, such as whether the connection maintains that performance at different times, whether every device in a home receives the same service, or whether the operator has complied with every aspect of its offer. The result is best read as an observation of a particular test, not as a verdict on the service as a whole. Keeping that scope in mind makes the figures more useful and avoids drawing conclusions that the measurement was not designed to support.

The description of the dataset associated with the test mentions download and upload speeds, latency and signal strength. It also says that network information, such as the technology used, is collected. These measurements are not interchangeable: download speed represents receiving data; upload speed represents sending it; and latency is the connection’s response time. Signal strength provides additional context for measurements where that information is available. Each figure therefore describes a different aspect of the connection, rather than a different way of expressing one overall score.

For downloading files or streaming content, download speed is often a visible and relevant measure. For video calls, cloud backups or sending files, upload speed also matters. Latency can help explain responsiveness in interactive activities, although it is not enough on its own to assess an application. A result becomes more meaningful when the measurements are related to the use being assessed, rather than reducing the connection to a single figure. Looking at the figures in relation to what you were doing helps explain what the test can say, while keeping clear that no one metric describes every part of the experience.

The data portal explains that the published measurements are generated from the user population through a crowdsourcing approach. This kind of dataset provides observations from tests carried out by different people and devices; it is not equivalent to a controlled measurement of every line, and it does not justify assuming that all test conditions are the same. The result of one session describes that session, not necessarily the connection’s usual behaviour. Aggregated observations can offer a broader view, but they do not turn an individual test into a controlled assessment of a particular household’s service.

A one-off test can also be affected by local factors: wireless coverage, distance from the router, the equipment used, other applications running, or simultaneous use of the network. This is a general limitation when interpreting speed tests, not a claim that the CNMC controls or removes each variable. A measurement records the outcome under the circumstances in which it was taken; those circumstances can differ between sessions and users. An observed speed on one device should not be confused with a comprehensive audit of the contracted service.

If the result seems very different from what you expected, the most useful approach is to repeat the check systematically. Running several tests at different times can help show whether the difference appears consistently or only on one occasion. Note the time, the device and the type of connection—for example, Wi-Fi or cable, if the equipment supports both options—so that you retain context that a single figure would otherwise lose. Comparing results without recording these details makes it harder to tell whether the sessions were genuinely comparable.

Before testing, it is sensible to close downloads and tasks that use the network, avoid having other devices transfer large amounts of data, and keep the same device and location when comparing sessions. To distinguish a Wi-Fi issue from one that also occurs over a wired connection, you can compare both situations where possible. These are practical comparison principles; they should not be presented as official CNMC instructions unless they are documented as such. Applying them consistently does not eliminate every variable, but it makes repeated observations easier to interpret and compare.

The test’s number is not necessarily directly comparable with the speed advertised for a tariff. Check the speed and conditions stated in the contract, the technology in use, and the equipment to which the device running the test is connected. A Wi-Fi measurement includes the wireless link between the router and the device; it therefore does not allow every difference to be attributed exclusively to the operator’s network. The test result and the advertised figure may describe different circumstances, so the comparison needs to take those circumstances into account.

If you intend to make a complaint, it is prudent to save the results and the conditions for each measurement, check the contract and report the issue to the operator with that information. An organised record can help with diagnosis, but it does not automatically turn a test into conclusive evidence of non-compliance. Interpretation depends on repetition, method and the agreed conditions, not only on a result that seems low. Keeping the measurement details together with the contract terms makes it easier to explain what you observed without claiming more than the evidence establishes.

The CNMC test can serve as a starting point for checking basic measurements and observing how they vary. The dataset adds an aggregated perspective: it lets users consult measurements supplied by users and associated fields for speed, latency, signal and technology. That scale does not replace an individual diagnosis, because aggregated data bring together different testing conditions and do not necessarily describe a particular line. It is useful to distinguish the wider collection of observations from the experience of a single connection.

The information consulted is not enough to claim that one test determines the overall quality of a connection, certifies contractual compliance, or identifies the cause of a problem by itself. For a more useful diagnosis, combine repeated measurements, comparable conditions and the information in the contract; an independent tool may provide another observation, but its results also need to be interpreted in light of its method. The prudent approach is to use the test as an indication and look for consistency before drawing conclusions. In this way, the measurement can inform a further check without being treated as proof of something it cannot establish alone.