Wi-Fi speed test

Published by Pulse (SearchSwitchSave.com). Reviewed April 2026 by the UKSpeedTest editorial team led by Dr Alex J Martin-Smith.

A Wi-Fi speed test tells you what your device can really achieve over wireless in your current room, at this time, on this network. That is the number that matters when meetings freeze in the loft, films buffer in the lounge, or cloud backups crawl after school. Pulse measures your live download speed, latency, and jitter from the device in your hand, so you can separate in-home Wi-Fi limits from a possible broadband-line issue before you spend money or escalate.

Who this page is for

• You get different speeds in different rooms and want to know if the issue is your router position, channel congestion, or the broadband line itself.
• You are deciding whether to move your hub, add mesh nodes, use Ethernet for fixed devices, or switch to a faster package.
• You need evidence before contacting your provider, landlord, or installer and want a fair testing method rather than one-off screenshots.

Definitions you should know before testing

• Download speed (Mbps): how fast data arrives to this device. Higher usually helps streaming and large downloads.
• Latency (ms): the delay before data starts moving back. Lower helps responsiveness in calls, browsing, and gaming.
• Jitter (ms): variation in latency over time. Lower usually means fewer glitches in real-time activities.

Real UK scenarios and what they show

A Cardiff family thought their full-fibre package was underperforming because the upstairs office was getting less than half the lounge speed each evening. A fair test sequence showed that Ethernet near the router was stable, but Wi-Fi in the office dipped sharply after 7pm when neighbouring flats were all active. They moved one mesh node out of a corner and switched two fixed devices to wired connections. Evening call quality improved within a day without changing package.

A Sheffield student house had complaints from one bedroom only. The group ran tests at the same times in four rooms using one laptop, then repeated one wired baseline. The room with issues had the highest jitter and weakest throughput, while other rooms were acceptable. The solution was not a pricier tariff: they repositioned the router away from a TV cabinet, updated firmware, and pinned high-demand devices to 5 GHz close to the hub.

Step-by-step: run a fair test and get useful evidence

1. Run one baseline near the router, ideally on Ethernet if your device supports it.
2. Run Wi-Fi tests in each room you actually use: desk, lounge, bedroom, and kitchen.
3. Repeat at two realistic times, such as lunchtime and peak evening usage.
4. Record setup details: device used, room, band if known (2.4 GHz/5 GHz), and nearby heavy activity.
5. Compare results before making changes, then retest after each change so you can isolate what worked.

How to interpret your result without guesswork

Start by comparing your result to your own baseline and your own usage needs, not generic speed brag numbers. If your home office calls are stable and file syncs complete on time, a lower figure may still be fit for purpose. If everyday usage breaks down, then the absolute number matters less than repeatable evidence of instability. Track at least a few runs over different times, especially when issues are most visible.

When results differ between rooms, this usually points to local wireless factors. When results are consistently weak even on controlled runs, you have a stronger case to escalate. Keep your notes practical: date, time, device, connection method, and what else was active on the network. This simple discipline turns anecdotal frustration into a credible troubleshooting record.

What to do next: troubleshoot, escalate, or switch

First, apply low-risk fixes: reposition the hub, reduce local interference, pause background traffic during critical tasks, and retest after each change. Second, if performance remains poor on fair repeat runs, contact your provider with a concise summary and your log. Third, if outcomes stay weak after support steps, use comparison and rights pages to evaluate whether a package change or provider switch is justified for your usage profile.

Mistakes that make speed evidence weak

The most common mistake is mixing too many variables in one comparison. If you change device, room, and time all at once, you cannot tell what caused the difference. Another common issue is testing while background updates are active, then treating that run as representative. You also weaken your case if you keep no notes and rely on memory. A provider support agent can only act on what is documented, so clear notes are not bureaucracy; they are leverage.

A second mistake is making binary decisions from one number, such as immediately upgrading package or immediately blaming line faults. In practice, users usually need a sequence: first isolate local factors, then compare repeated baselines, then escalate with evidence. This process sounds slower, but it usually saves time, money, and frustration because you avoid dead-end support calls and unnecessary contract changes.

Evidence checklist before opening a complaint

• At least three to six runs across different days, including problem periods.
• One controlled baseline run with minimal local variables.
• Notes on device, location, wired/Wi-Fi setup, and concurrent high-demand usage.
• Screenshots or copied results saved with clear timestamps.
• A concise summary of impact on real activities (calls, streaming, work tools, gaming).

Final quality check before changing package

Before committing to a new tariff, run one final comparison cycle so your decision is grounded in current evidence rather than historical frustration. Include at least one run in your most problematic time window and one run in a quieter period. If poor performance persists across both and remains visible in real tasks, the upgrade or switch case is much stronger. If the pattern is mostly room-specific or device-specific, local optimisation may still deliver better value than a contract change.

This final check also gives you a useful baseline for after-change validation. If you do switch provider or package, rerun the same method in the same rooms and times. That way you can confirm whether the change delivered meaningful improvement in stability and responsiveness, not just a temporary first-day speed spike.

Related guides

• Why is my Wi-Fi slow?
• Broadband speed vs Wi-Fi speed
• How to improve Wi-Fi speed at home
• UK speed test comparison

FAQ

References

1. Ofcom: broadband speeds code of practice (consumer guide)
2. Ofcom: advice for consumers
3. uSwitch: how to test broadband speed