Test beside the router
Run the LinkSpeed speed test on a modern phone, laptop or PC beside the router. Record upload, ping and jitter.
Upload speed troubleshooting guide
Find out why upload speed is slow
Start with one controlled test beside the router, then repeat over Ethernet if possible. The result should tell you whether the bottleneck is the package, Wi‑Fi, background uploads, router queueing or the provider path.
Start here
Find the Upload Bottleneck in Five Minutes
Keep the device and test method consistent. Change one variable at a time so each result removes a possible cause instead of creating a new guess.
Repeat over Ethernet
Use a known-good Ethernet cable where possible. If upload jumps sharply, the core broadband path is probably fine and Wi‑Fi is the weak point.
Pause background uploads
Stop OneDrive, iCloud, Google Photos, CCTV uploads, console captures and work file sync. Then rerun the same test.
Compare room, device and time
If one room or one device is much worse, focus on local wireless conditions. If every device is worse at the same time, move down to the provider evidence section.
Guide index
Jump to the Part That Matches the Result
Identify the upload fault boundary
Use the result matrix to decide whether the bottleneck is the package, Wi‑Fi, background traffic, router queueing or the provider.
Result-led diagnosisPackage limit or unrealistic expectation
Check whether the service simply has a low upstream cap compared with the advertised download speed.
Asymmetric packagesWi‑Fi, room and device limits
Use beside-router and Ethernet comparisons to prove whether local wireless conditions are suppressing upload.
Room and device checksBackground traffic and household load
Find out whether backups, cameras, sync and other household activity are silently filling the upstream path.
Busy-home checksRouter queueing and upstream saturation
Check loaded latency and decide whether SQM or router headroom is the real fix.
Loaded-latency checksBuild provider evidence
Use Ethernet results and repeated timings to decide when the provider needs to investigate provisioning or a line fault.
Escalation pathVisual explainer
Where slow upload speed can break down
Use this path map to separate a weak room, a busy router, a low upstream package cap and a slow destination service.
Upload fault matrix
Identify Your Upload Speed Fault Boundary
These symptoms tell you which section to jump to next. The aim is to validate the boundary before you start changing hardware or paying for a faster package.
Upload is always close to the package cap
If upload stays repeatably low on both Wi‑Fi and Ethernet but matches what the service is known to provide, the package is likely the limit rather than a fault.
Go nextUpload is poor in one room but better beside the router
This points to local wireless conditions, low client transmit power, interference, poor mesh placement or a weak device radio.
Go nextCalls, backups or livestreams collapse when the house gets busy
The likely boundary is background upload demand or router queue growth, not the headline package speed alone.
Go nextCheck household upload sources → or jump to router queueing →
Ping rises sharply while upload is active
This is the classic sign of upstream saturation or poor queue management. The line may not be broken at all: the queue is simply unmanaged.
Go nextEthernet upload is poor even when the line is quiet
If the same poor result repeats across devices and times, the problem may sit with package provisioning, signal levels, congestion or a line fault.
Go nextDownload looks normal but sending is slow
That does not rule out a problem. Many UK packages are highly asymmetric, and upload is more easily harmed by Wi‑Fi weakness and background sync.
Go nextCheck asymmetric package limits → then compare Wi‑Fi versus Ethernet →
Package speed reality
Package Limit or Unrealistic Expectation
Many people only notice slow upload after video calls, cloud backup or live streaming expose the upstream limit. A good download result does not prove the upload path is healthy.
What points here
- The same upload ceiling appears on Wi‑Fi and Ethernet.
- The result is close to the known product cap for FTTC, cable or a budget full-fibre package.
- Nothing changes much after pausing background traffic.
What to do next
- Check the package’s quoted or expected upload range rather than only the download headline.
- For regular cloud backup, CCTV and large file sharing, compare whether the service simply lacks enough upstream headroom.
- If the package should deliver more than you are seeing, continue to the Ethernet and provider sections before upgrading.
Common trap: a service can feel “fast” for browsing and downloads while still being too limited for multi-user upload tasks. That is especially common on asymmetric packages where upload is only a fraction of download.
Local wireless checks
Wi‑Fi, Room and Device Limits
Upload can fall harder than download when the device struggles to send back to the router. Poor signal, interference and weak client radios often show up first on uploads, calls and live streams.
What points here
- Upload improves beside the router or over Ethernet.
- One room or one device performs far worse than another.
- Phones and laptops in the same place give different upload results.
What to do next
- Retest beside the router, then in the problem room on the same device.
- Prefer 5 GHz when you are close enough, and check mesh placement if the upload collapse only happens on a satellite node.
- For work laptops, streamers or fixed devices, use Ethernet where practical before blaming the provider.
Need the room-specific fix? Use the wider companion guide on broadband slowdowns caused by Wi‑Fi and device limits if the same area of the home regularly underperforms.
Busy-home diagnosis
Background Uploads and Household Load
Slow upload often turns out to be normal capacity being silently used elsewhere. Cloud backup, photo sync, CCTV, console captures and work VPN traffic can keep the upstream path full for long periods.
What points here
- Performance improves as soon as you pause backup or sync services.
- Calls, livestreams or gaming feel worse while someone uploads files or cameras are active.
- The issue appears mainly when the home is busy rather than all day.
What to do next
- Stop or schedule OneDrive, iCloud, Google Photos, NAS replication and CCTV uploads outside important usage times.
- Check whether consoles are uploading captures or cloud saves in the background.
- If the line stays stable only when these jobs are paused, the long-term fix is queue management or a package with more upstream headroom.
Upload load raising ping? Run the bufferbloat test or continue to the upstream queue section below to see whether loaded latency is the real symptom.
Upstream queueing
Router Queueing, Upload Saturation and SQM
On many connections the upload path is the first to saturate. Once the queue fills, real-time traffic and TCP acknowledgements wait behind bulk uploads. That is why calls freeze, games feel delayed and browsing becomes sticky during uploads.
What points here
- Ping rises sharply during an upload even though the line is otherwise quiet.
- Large file sending or cloud sync makes everything else feel laggy.
- Upload results are not terrible, but the connection feels unstable under load.
What to do next
- Record idle ping, start a controlled upload, then compare the latency increase.
- If loaded latency rises hard, enable SQM or another sensible queue-management feature if your router supports it.
- Start shaping slightly below stable upstream throughput so the controllable queue stays in the router rather than upstream.
Advanced Router admin / power-user terminal audit
Use these checks only if you manage an OpenWrt or similar router and want deeper proof of upstream queue behaviour.
OpenWrt queue checks
tc -s qdisc show
tc -s qdisc show dev pppoe-wan
ip -s link show
uci show sqmReplace pppoe-wan with the actual shaped interface. Interpret drops, ECN marks, backlog and overlimits together rather than relying on one counter.
SQM causes throughput to collapse? The router CPU may be the bottleneck. Use the companion guide to balancing hardware acceleration and software SQM traffic shaping to check whether the current hardware can sustain shaping under load.
Provider evidence
Build Provider Evidence Before You Escalate
If upload remains poor on Ethernet with other traffic paused, collect evidence that shows the problem is outside local Wi‑Fi. This helps support distinguish a line or provisioning issue from a home-network complaint.
What points here
- Ethernet is consistently poor even beside the router.
- Multiple devices show the same weak upload ceiling.
- There is little improvement after stopping household uploads.
What to collect and ask for
- Record date, time, device, Wi‑Fi/Ethernet, upload speed, ping and jitter across several tests.
- Tell the provider the issue remains on Ethernet with background traffic paused.
- Ask them to check package provisioning, upstream congestion, signal levels or a line fault.
Slow only at the same evening times? Keep this page for the initial fault boundary, then move to the dedicated guide on why broadband slows down at night for the multi-day peak-time logging process.
Upload speed FAQs
Common Questions About Slow Upload Speed
Why is my upload speed slow but download speed is fine?
Many broadband packages are asymmetric, so upload capacity is much smaller than download capacity. Slow upload can also be caused by Wi‑Fi weakness, cloud backups, CCTV uploads, router queueing or provider-side faults even when download looks normal.
Can Wi‑Fi reduce upload speed?
Yes. Poor signal, interference, low client transmit power and weak mesh placement can reduce upload more than download, especially from rooms far from the router.
What should I test first for slow upload speed?
Start beside the router, then repeat over Ethernet if possible. Compare upload, ping and jitter again after pausing cloud backups and other background uploads.
When should I contact my provider?
If upload stays poor on Ethernet with background traffic paused and the same pattern repeats across multiple tests, collect the results and ask the provider to check provisioning, upstream congestion or a line fault.