Gigabit broadband is only useful if your router, Wi‑Fi, Ethernet ports and devices can deliver high speeds where you use them.
Gigabit Wi‑Fi guide
A fast package does not guarantee gigabit speed on every device. The broadband line, router ports, Wi‑Fi link, mesh backhaul and client hardware must all support the result you expect.
Quick answer
No. You do not need Wi‑Fi 7 for a 1 Gbps broadband service. A wired Gigabit Ethernet path normally delivers roughly 940–950 Mbps of TCP payload, while a strong Wi‑Fi 6 or Wi‑Fi 6E setup can be enough for many homes. Wi‑Fi 7 becomes more useful when compatible clients, premium mesh backhaul, local wireless congestion or a multi-gigabit package are the measured limit.
UK full fibre reality
A gigabit service can be limited by the router, a 1GbE port, an older client, weak signal, poor mesh placement or household traffic. Replacing everything with Wi‑Fi 7 does not remove a bottleneck outside the wireless link.
The 940 Mbps ceiling
On standard Ethernet with a 1500-byte MTU, a full TCP/IPv4 packet carries 1460 bytes of application payload after the minimum 20-byte IPv4 and 20-byte TCP headers. Ethernet then adds its own frame and on-wire spacing overhead.
| Raw 1GbE line rate | 1,000,000,000 bits/s |
|---|---|
| IP packet / Ethernet payload | 1500 bytes |
| TCP application payload | 1460 bytes (1500 − 20 IPv4 − 20 TCP) |
| On-wire Ethernet size | 1538 bytes (8 preamble/SFD + 14 header + 1500 payload + 4 FCS + 12 inter-frame gap) |
| Simplified payload efficiency | 1460 ÷ 1538 = 94.93% |
| Theoretical TCP payload ceiling | ≈949.3 Mbps before ACKs, TCP options, PPPoE/VLAN overhead, encryption and test-stack effects |
That is why real speed tests on a clean 1GbE path commonly land around 930–950 Mbps, not exactly 1,000 Mbps. Under the same simplified framing assumptions, 2.5GbE raises the ceiling to roughly 2.37 Gbps. Ethernet frame sizes are documented by Cisco, while RFC 6691 defines the 20-byte minimum IPv4 and TCP headers used to derive a 1460-byte MSS.
A client can only use the Wi‑Fi generation, antenna count and channel width it supports. A common 2×2 Wi‑Fi 6 client on an 80 MHz channel tops out at a 1201 Mbps PHY rate, so usable throughput is lower after airtime, acknowledgements, encryption, contention and retries. A 160 MHz Wi‑Fi 6/6E client can link much faster, but only when both router and device support the wider channel.
CPU, firmware and WAN/LAN port speeds can cap a fast full-fibre service.
Wireless throughput drops as signal weakens, especially on higher-frequency bands.
A node placed in a weak-signal location repeats a weak connection.
Uploads, downloads and many active devices share capacity and can raise latency.
If a wired control test is poor, fix the line, package or provider issue before upgrading Wi‑Fi.
Test first
Compare the same device over Ethernet, beside the router and in the room where the connection feels slow. Then use the test that matches the symptom.
The broadband line is probably not the first bottleneck. Compare near-router Wi‑Fi with the problem room, then check client capability, router placement, channel choice and mesh backhaul before replacing the package.
Look upstream of Wi‑Fi: package speed, router WAN/LAN ports, the test device, provider congestion or the broadband line itself can all cap both wired and wireless results.
Treat this as a placement or attenuation problem first. Brick, foil-backed insulation, distance and weak mesh-node positioning usually matter more than changing from Wi‑Fi 6 to Wi‑Fi 7.
Interactive checker
Use your package, devices, goal and router ports to identify whether Wi‑Fi 7, Ethernet, Wi‑Fi 6 mesh or a coverage fix should come first.
Connection comparison
Use these figures as reference points rather than guaranteed speed-test results. Wired ceilings can be calculated from framing assumptions; Wi‑Fi results vary much more with the router, client, signal, interference, channel width and local airtime.
| Connection type | Useful reference ceiling | Channel / client profile | Best use | Important caveat |
|---|---|---|---|---|
| Gigabit Ethernet (1GbE) | ≈949 Mbps simplified TCP/IPv4 payload ceiling; often ≈930–950 Mbps in speed tests | Wired; 1 Gbps line rate | PCs, consoles, TVs, work docks and clean line testing | A 1GbE port cannot show a true 1,000+ Mbps application result. |
| 2.5GbE Ethernet | ≈2.37 Gbps under the same simplified framing assumptions | Wired; 2.5 Gbps line rate | Multi-gig packages, NAS, switches and creator workstations | Every bottleneck port in the path must negotiate above 1GbE. |
| Wi‑Fi 6 | 2×2 / 80 MHz PHY up to 1.201 Gbps; 2×2 / 160 MHz up to 2.402 Gbps | 2.4 / 5 GHz; 80 or 160 MHz | Modern homes where strong 5 GHz coverage already works well | Usable throughput is below PHY rate and can fall sharply through walls or contention. |
| Wi‑Fi 6E | Same Wi‑Fi 6 PHY family, with 6 GHz access for compatible clients | 2.4 / 5 / 6 GHz; up to 160 MHz | Clean short-range links in congested flats or near a mesh node | 6 GHz loses useful range sooner and needs compatible clients. |
| Wi‑Fi 7 | 2×2 / 320 MHz / 4K-QAM PHY up to 5.76 Gbps; suitable real systems can exceed 2 Gbps | 2.4 / 5 GHz, with 6 GHz optional; up to 320 MHz on 6 GHz | Multi-gig internet, premium mesh backhaul, large local transfers and compatible clients | 6 GHz, 320 MHz and MLO implementation vary by router and client. |
Wireless figures are capability references, not guarantees. Intel documents 2×2 Wi‑Fi 6 client rates up to 2.4 Gbps at 160 MHz and 2×2 Wi‑Fi 7 rates up to 5.76 Gbps with 320 MHz and 4K-QAM. Independent router testing also shows that model choice, client support and distance materially change real throughput.
Fast visual decision
What Wi‑Fi 7 actually changes
Wi‑Fi 7 can coordinate more than one link across bands. Some client/router combinations rapidly switch between eligible links, while true simultaneous multi-radio modes can use more than one link at once. Do not assume that every Wi‑Fi 7 device simply adds 5 GHz and 6 GHz speeds together.
See STR vs EMLSR MLO explainedIf interference occupies an eligible slice of an 80, 160 or 320 MHz Wi‑Fi 7 channel, compatible equipment can leave that sub-channel unused while continuing across the remaining clean spectrum. That can help in dense flats and terraces, but it does not make a noisy 320 MHz channel automatically better than a clean 160 MHz one.
A Wi‑Fi 5 or Wi‑Fi 6 phone does not gain 320 MHz channels, 4K-QAM or Wi‑Fi 7 MLO just because the router is newer. It may still benefit indirectly if compatible Wi‑Fi 7 devices move heavy traffic onto cleaner 6 GHz links and reduce contention elsewhere.
Check Wi‑Fi 6/6E/7 client compatibilityUK ISP hardware reality
Some UK providers now supply Wi‑Fi 7 on selected packages, so an aftermarket router is no longer automatically required. The important check is the exact hub supplied with the exact broadband tier at your address.
Gigabit relevance: Included with select full-fibre plans; 2.5GbE WAN plus one 2.5GbE LAN port gives useful headroom beyond a pure 1GbE path.
Gigabit relevance: EE's higher-end option, with 6 GHz and multiple 2.5GbE LAN ports; paired with the 1.6Gbps Ultimate route.
Gigabit relevance: Supplied with Sky's 2.5Gbps and 5Gbps Gigafast+ services. Sky's standard Max Hub remains Wi‑Fi 6.
Gigabit relevance: Hub 5 serves Virgin's fibre-coax network and Hub 5x its full-fibre route; both are Wi‑Fi 6, so Wi‑Fi 7 requires separate hardware today.
Provider hardware changes with package and rollout. Checked against current EE, Sky and Virgin Media specifications in August 2026.
Use Ethernet for consoles, TVs, desktops and work docks where practical.
Compare Ethernet and Wi‑FiWi‑Fi 7 or premium Wi‑Fi 6 mesh may help, but node placement and loaded latency still matter.
Test loaded latencyIf your primary issue is local network jitter rather than pure throughput, use our diagnostic guide to see whether Wi‑Fi 7 reduces gaming lag and jitter.
Prioritise 2.5GbE, local-network speed and compatible Wi‑Fi 7 clients.
Compare Wi‑Fi 6 and Wi‑Fi 7No. Ethernet or a capable Wi‑Fi 6 or Wi‑Fi 6E setup can be enough. Upgrade when testing proves that compatible wireless devices, busy-home capacity or mesh backhaul are the limit.
A Wi‑Fi link rate is not the same as usable application payload throughput. Encryption, management frames, acknowledgements, contention and retransmissions consume airtime. The final speed gap also depends on the client device, signal, walls, interference, channel width, router design, mesh backhaul and household traffic. In clean single-client conditions, application payload throughput can sometimes be around 60% to 70% of the reported raw wireless link rate, but treat this as a planning range rather than a guarantee.
With a 1500-byte MTU and minimum IPv4/TCP headers, the simplified TCP payload ceiling is about 949 Mbps before acknowledgements and other overhead. Real 1GbE speed tests commonly land around 930–950 Mbps. To test at 1,000 Mbps or above, the router and test device need suitable 2.5GbE or faster ports.
Wi‑Fi 6 can deliver strong speeds close to a capable router, but it will not guarantee full gigabit performance in every room or on every device.
It is most useful with gigabit or multi-gig full fibre, compatible Wi‑Fi 7 clients, strong signal, heavy wireless use, premium mesh or large local file transfers.