Router vs. ISP vs. Your PC: Isolating the Real Bottleneck

30 Jul 2026

Your internet connection feels slow, but where is the problem actually occurring?

It could be:

The Windows PC
The Wi-Fi connection between the PC and router
The router itself
The broadband line supplied by your internet service provider
A VPN, security service or company network
The website or cloud platform you are accessing

These problems can produce almost identical symptoms. Websites hesitate, Teams calls break up, cloud files take longer to open and speed-test results vary unpredictably.

Restarting the router may appear to help, but that does not prove the router is faulty. The restart also reconnects the broadband session, changes the Wi-Fi environment and temporarily disconnects every device. Several variables have changed at once.

The most effective diagnosis is to test each part of the connection separately:

Your application

↓

Your Windows PC

↓

Wi-Fi or Ethernet

↓

Router

↓

ISP broadband connection

↓

Wider internet or cloud service

Hamilton Group’s experienced IT team uses this same isolation principle: change one variable at a time, compare the results and identify where performance first deteriorates.

What Does “Slow Internet” Actually Mean?

Before testing, define the problem more precisely.

Low download speed

Large files, applications, updates and streaming content take longer to arrive.

Low upload speed

Sending attachments, uploading cloud files, sharing video and backing up data takes longer.

A connection can have fast downloads but inadequate upload capacity.

High latency

The connection takes too long to respond, even when the total transfer speed appears good.

High latency affects:

Teams and Zoom
Remote desktops
VoIP
Online games
Cloud applications
Interactive websites

Jitter

Latency varies from one moment to another.

A video call may work normally for a few seconds and then briefly distort or freeze.

Packet loss

Some network traffic fails to reach its destination and must be retransmitted.

Symptoms may include:

Broken audio
Video freezing
Remote sessions disconnecting
Websites loading partially
VPN instability

One application is slow

The broadband connection may be healthy while a specific website, server or cloud service is experiencing a problem.

Do not judge every connectivity issue by download speed alone.

Start With a Controlled Test

A useful test should avoid changing several conditions at once.

Use:

The same computer
The same test service
The same router
Approximately the same time
No large downloads or uploads
No active VPN unless the VPN is what you are testing

Before starting:

Restart the PC.
Close unnecessary applications.
Pause large cloud synchronisation temporarily.
Confirm that Windows Update is not downloading.
Disconnect from the VPN.
Ask other users to avoid large transfers briefly.
Record the date and time.

Windows Delivery Optimisation can use network bandwidth for Windows updates, Microsoft Store applications and other Microsoft content, although it is designed to adjust its activity automatically. Check for update activity when an unexplained slowdown appears.

The Most Important Test: Use Ethernet

Connect a computer directly to the router using a suitable Ethernet cable.

Temporarily turn Wi-Fi off on that computer so you know the test is using the cable.

Ofcom recommends using a wired Ethernet connection for the most accurate broadband-speed measurement because Wi-Fi can reduce the speed between the router and the device.

Run several tests and record:

Download:

Upload:

Latency:

Time:

Connection type: Ethernet

Wired performance is good

If Ethernet delivers approximately the expected speed but Wi-Fi is slow, the broadband line and ISP are probably not the main bottleneck.

Focus on:

Wireless coverage
Router placement
Channel congestion
Wi-Fi bands
Mesh-node placement
The PC’s wireless adapter

Wired performance is also poor

If every wired test is substantially below the expected service speed, investigate:

The Ethernet link
Router performance
The router’s WAN connection
The broadband line
ISP congestion or faults

The wired test narrows the problem, but it does not automatically prove that the ISP is responsible. A faulty cable, overloaded router or 100 Mbps Ethernet link could still be limiting the result.

Compare More Than One Device

Test at least two devices.

Ideally, use:

One computer over Ethernet
One computer over Wi-Fi
A second modern device for comparison

Every device is slow

The problem is more likely to involve:

The router
The broadband connection
ISP performance
A network-wide upload or download
A wider service outage

Only one Windows PC is slow

The problem is more likely to involve:

Its network adapter
Its driver
Its VPN or security software
Background applications
Power-saving settings
Windows configuration
Malware or unwanted software
A damaged Ethernet cable used only by that PC

One website or application is slow on every device

The destination service may be the problem.

Test several unrelated services before blaming your own equipment.

Test Close to the Router

For Wi-Fi testing, place the laptop in the same room as the router or access point.

Run the test again.

Then repeat it in the usual working location.

A useful comparison might look like:

Ethernet: 480 Mbps

Wi-Fi beside router: 420 Mbps

Wi-Fi in office: 62 Mbps

This strongly suggests that the broadband line is delivering the available capacity, while the wireless path into the office is the bottleneck.

Ofcom notes that increasing the number or thickness of walls between a router and a device can reduce performance. It also recognises that the Wi-Fi connection between the router and user devices can become the bottleneck as broadband speeds increase.

Check the PC’s Wi-Fi Connection

Open Terminal or Command Prompt and run:

netsh wlan show interfaces

This can show information such as:

Connected network name
Radio type
Channel
Signal
Receive rate
Transmit rate

Microsoft documents netsh wlan show interfaces as part of Windows’ built-in wireless-management and troubleshooting commands.

The reported receive and transmit rates are the connection rates between the PC and access point. They are not a guarantee of actual internet throughput.

For example:

Wi-Fi receive rate: 866 Mbps

Internet test: 200 Mbps

may be normal on a 200 Mbps broadband service.

By contrast:

Wi-Fi receive rate: 72 Mbps

Internet service: 500 Mbps

suggests that the wireless link may prevent the PC from using the available broadband capacity.

Check the adapter’s capabilities

Run:

netsh wlan show drivers

Review Radio types supported.

Microsoft recommends this command for checking the wireless standards supported by the Windows adapter.

An older adapter may not support:

5 GHz
Wi-Fi 6
Wi-Fi 6E
Wi-Fi 7
Wider channel widths
Modern security standards

A fast router cannot force an old client adapter to use technology it does not support.

Generate a Windows Wireless Report

For intermittent Wi-Fi failures, open Terminal as administrator and run:

netsh wlan show wlanreport

Windows generates an HTML report containing wireless activity from the previous sessions.

The report can help identify:

Connection failures
Disconnections
Adapter information
Driver versions
Network profiles
Session durations
Reasons Windows recorded for losing connectivity

Microsoft provides the wireless network report specifically for analysing Wi-Fi events and connection history.

Do not publish the complete report publicly without checking it. It may contain computer names, wireless network names and adapter information.

Check the Ethernet Link Speed

A wired computer can still be limited by its local Ethernet connection.

A modern gigabit connection should normally negotiate at:

1.0 Gbps

A result of:

100 Mbps

can restrict real-world throughput to below 100 Mbps regardless of how fast the broadband service is.

Possible causes include:

An older network adapter
A damaged Ethernet cable
A cable with incomplete wiring
A 100 Mbps router or switch port
A docking station limited to 100 Mbps
Failed auto-negotiation
An unsuitable USB Ethernet adapter

Open:

Settings > Network & internet > Ethernet

Review the link speed where displayed.

You can also check:

Control Panel > Network and Internet > Network Connections

Double-click the Ethernet connection and review Speed.

Test another cable and port

When the link reports 100 Mbps unexpectedly:

Replace the Ethernet cable.
Connect directly to the router.
Avoid the docking station temporarily.
Try another router or switch port.
Restart the adapter and router.
Check the manufacturer’s network driver.

Do not manually force duplex and speed settings unless you understand the equipment at both ends. Auto-negotiation is normally the correct configuration.

Find the Router’s Address

Open Command Prompt and run:

ipconfig

Look under the active Wi-Fi or Ethernet adapter for:

Default Gateway

A typical address might look like:

192.168.1.1

or:

192.168.0.1

This is normally the router’s local address.

The gateway provides the first useful boundary test: can the PC communicate reliably with the router before internet traffic is involved?

Ping the Router

Run:

ping <default-gateway>

For example:

ping 192.168.1.1

A healthy local wired connection will usually produce low and consistent response times with no packet loss.

A Wi-Fi connection may vary more, but large spikes and losses are still useful evidence.

Example of a healthy local result:

Packets: Sent = 4, Received = 4, Lost = 0

Approximate round trip time:

Minimum = 1ms, Maximum = 3ms, Average = 1ms

Example requiring investigation:

Packets: Sent = 4, Received = 3, Lost = 1

Minimum = 4ms, Maximum = 194ms, Average = 69ms

If communication with the router itself is unstable, the ISP is not yet involved in that failed portion of the test.

Focus on:

Wi-Fi interference
Signal quality
Ethernet cabling
Network-adapter drivers
Router load
A faulty router port
Local network loops or congestion

Microsoft recommends pinging the default gateway when diagnosing Wi-Fi connection problems. If the router does not respond reliably, it advises checking the connection to the router before moving on to wider internet troubleshooting.

Test for Packet Loss Over Time

Four ping requests may miss an intermittent fault.

Run a longer test:

ping <default-gateway> -n 100

Record:

Packets sent
Packets received
Percentage lost
Minimum latency
Maximum latency
Average latency

Run this first over Ethernet and then over Wi-Fi.

Ethernet is clean but Wi-Fi loses packets

The wireless link is the likely bottleneck.

Both Ethernet and Wi-Fi lose packets to the router

Investigate:

Router failure
LAN congestion
Cabling
Switches
Network loops
Router CPU or firmware

The router test is clean but internet activity loses packets

The problem is likely beyond the local PC-to-router link.

Test DNS Separately

Sometimes the connection is not slow—the process of translating website names into network addresses is slow.

Symptoms can include:

A delay before websites begin loading
Applications eventually connecting and then working normally
Some services loading while others report name-resolution errors

Run:

nslookup www.microsoft.com

This shows which DNS server answered and whether it returned an address.

You can also flush the local Windows DNS cache:

ipconfig /flushdns

Microsoft includes flushing the DNS resolver cache among its supported network troubleshooting steps.

A DNS problem may involve:

The router’s DNS forwarding
ISP DNS servers
A VPN
Security filtering
Incorrect manual DNS settings
A damaged local cache
A business firewall

Do not change DNS services randomly without recording the existing configuration and understanding your organisation’s filtering or security requirements.

Use Tracert to See the Route

Run:

tracert /d www.microsoft.com

tracert shows the sequence of routers between the PC and destination. The /d option avoids name resolution, which can make the test complete more quickly.

Microsoft explains that tracert identifies the route by examining responses from intermediate routers. It also points to pathping when latency and packet-loss analysis across the route is required.

The first hop is normally your router.

Later hops may belong to:

Your ISP
A transit provider
A cloud network
The destination service

Important limitation

Asterisks in a traceroute do not automatically prove that a router is faulty.

Some network devices:

Deprioritise diagnostic traffic
Rate-limit responses
Do not reply to traceroute requests
Continue forwarding normal traffic successfully

Focus on repeated patterns and actual application performance rather than one missing response.

Use Pathping for Longer Analysis

Run:

pathping www.microsoft.com

pathping combines route discovery with a longer period of latency and packet-loss measurement.

It takes several minutes to complete.

Look for loss that begins at one point and continues through later hops. A single intermediate router that does not answer diagnostic traffic while later hops remain healthy may not be the actual source.

For difficult or business-critical cases, the results should be interpreted alongside:

Router logs
ISP line statistics
Application monitoring
Tests to several destinations
Wired and wireless comparisons

Check Task Manager for Local Bandwidth Use

Press:

Ctrl + Shift + Esc

Open Processes and check the Network column.

Look for applications using significant bandwidth, such as:

OneDrive
SharePoint synchronisation
Windows Update
Backup software
Steam or game launchers
Cloud-storage applications
Video conferencing
Browser downloads
Security tools
Remote-support software

Also open:

Performance > Wi-Fi

or:

Performance > Ethernet

This shows current send and receive activity.

One computer uploading a large cloud backup can consume the available upstream capacity and make calls or browsing feel slow across the network.

Check OneDrive, Backup and Cloud Activity

Upload saturation can be difficult to recognise.

Many broadband services provide significantly less upload capacity than download capacity. A large cloud backup may therefore fill the upload path even while download testing appears reasonably fast.

Check:

OneDrive synchronisation status
Backup application activity
SharePoint library synchronisation
Large email attachments
Video uploads
Security-camera uploads
Cloud-based file transfers

Pause the activity briefly and repeat the test.

If latency and call quality immediately improve, the connection may need:

Better traffic management
Faster upload capacity
Backup scheduling
A business-grade connection
Application bandwidth controls

Do not disable backups permanently to improve internet performance.

Test With and Without the VPN

A VPN changes the route your traffic follows.

It can also add:

Encryption overhead
Additional latency
Security inspection
Traffic filtering
A distant gateway
Capacity limits

Run the same test:

With the VPN disconnected
With the VPN connected

Performance is normal without the VPN

Investigate:

VPN gateway load
Gateway location
Split tunnelling
VPN client version
Security inspection
The organisation’s internet connection
The route to the business network

Performance is poor in both cases

The bottleneck is probably not limited to the VPN.

On a business PC, do not alter VPN or security policies without approval.

Check Whether Security Software Is Inspecting Traffic

Endpoint security, web filtering and encrypted-traffic inspection can affect performance.

Possible signs include:

One managed PC is slower than unmanaged devices.
Browsers are slower while other protocols work normally.
Performance changes after a security-agent update.
Downloads are fast initially and then pause during scanning.
The issue occurs only on company devices.

The correct response is not to disable protection.

Hamilton Group can review:

Security-agent health
Web-filtering policies
SSL inspection
Conflicting antivirus products
Proxy configuration
Endpoint performance

Any test that disables protection should be authorised, controlled and brief.

Check the Router’s Status Page

Do not use the default address or credentials from an unrelated internet guide. Check the router label, ISP documentation or network records.

Review information such as:

Internet connection status
WAN uptime
Synchronisation speed
Signal or optical status
Connection errors
Router CPU and memory
Connected devices
Firmware version
System logs

The available information varies by broadband technology.

DSL or fibre-to-the-cabinet connections

The router may show:

Downstream synchronisation rate
Upstream synchronisation rate
Noise margin
Attenuation
Error counts
Retraining or reconnection history

Full-fibre connection

You may have a separate optical network terminal, or ONT.

Check:

Power
Optical or PON status
Alarm or LOS indicators
Ethernet connection to the router

Do not disconnect or reset fibre equipment unnecessarily. Optical connectors are delicate, and the provider may need the equipment in its current state to diagnose a fault.

Separate Router Speed From ISP Speed

Some routers show the speed of the broadband connection arriving at the router.

Compare that figure with the speed reaching the computer.

For example:

Router reports from ISP: 500 Mbps

Wired PC test: 470 Mbps

Wi-Fi office test: 80 Mbps

The ISP connection appears healthy; Wi-Fi is the bottleneck.

Another result might be:

Service purchased: 500 Mbps

Router WAN speed: 92 Mbps

Wired PC test: 89 Mbps

Possible causes include:

Router WAN port negotiating at 100 Mbps
A damaged cable between the ONT and router
A router incapable of processing the service speed
Incorrect router configuration

Another example:

Service estimate: 80 Mbps

Router DSL sync: 31 Mbps

Wired PC test: 29 Mbps

The PC and local network are broadly delivering what the router receives. The broadband line or its synchronisation requires investigation.

Test the Router Without Wi-Fi

When possible:

Connect one computer by Ethernet.
Disconnect or pause other devices briefly.
Turn off the test computer’s Wi-Fi.
Restart the router once.
Wait for the broadband connection to stabilise.
Run several tests.

If performance improves substantially only when other devices are disconnected, the issue may be:

Network saturation
A device performing a large transfer
Too many simultaneous users
Router capacity
An upload bottleneck
Malware or unwanted traffic

If the connection remains slow with one wired computer, the evidence points more strongly towards the router, line or ISP.

Test at Different Times

Run controlled wired tests:

Early morning
During the working day
In the evening
When the problem is occurring

Record each result.

Performance is poor at all times

Possible causes include:

Line fault
Incorrect service profile
Router limitation
Cabling
Provisioning problem
Persistent local traffic

Performance declines only during busy periods

Possible causes include:

ISP congestion
Shared local bandwidth
Neighbouring Wi-Fi congestion
Peak cloud-service usage
Business network saturation

One speed test is only a snapshot. Repeated tests reveal the pattern.

Reboot the Router Once—Not Repeatedly

A router restart can clear:

A temporary software fault
A failed broadband session
Accumulated resource problems
A stuck wireless radio
A connection that needs renegotiating

Microsoft includes restarting the modem and router among its standard connectivity troubleshooting steps.

However, frequent restarts can:

Remove useful log evidence
Interrupt every connected user
Cause DSL connections to retrain
Hide an underlying fault temporarily
Make ISP diagnosis more difficult

If the router needs restarting regularly, investigate why.

Record:

How long performance remains normal
Whether the connection drops or merely slows
Router uptime
Temperature
Error messages
Firmware version

Update Router Firmware Carefully

Router firmware can affect:

Stability
Security
Wi-Fi performance
Broadband compatibility
Device handling
Traffic management

For an ISP-supplied router, firmware may be installed automatically.

For third-party equipment, use the manufacturer’s official management system and the exact package for the hardware revision.

Before updating:

Back up the configuration where supported.
Confirm the exact router model.
Use reliable power.
Do not interrupt the update.
Record ISP connection settings if manually configured.

Do not install unofficial firmware on a business-critical router merely to obtain additional features.

Check Whether the Router Is Powerful Enough

Older routers may struggle with:

Gigabit broadband
Many wireless devices
VPN termination
Intrusion prevention
Content filtering
Complex Quality of Service rules
Several simultaneous video calls
High-speed inter-VLAN traffic

Possible signs include:

Wired speed falls when security functions are enabled.
Router CPU remains close to maximum.
Performance deteriorates as more users connect.
The router becomes hot or unstable.
A restart provides only temporary relief.
The WAN and LAN ports support the speed, but real throughput remains much lower.

Replacing the router may be appropriate—but only after confirming that it is the limiting component.

Bypass Third-Party Equipment

Temporarily remove equipment between the PC and router, such as:

Powerline adapters
Mesh nodes
Wi-Fi extenders
USB docks
Ethernet switches
Firewall appliances
Secondary routers

Test directly from the primary router.

Speed improves

Reconnect the equipment one item at a time until the bottleneck returns.

Speed remains poor

The removed device was not the main cause.

Do not permanently bypass business firewalls or security appliances without authorisation.

Powerline Adapters Can Be Unpredictable

Powerline networking uses the building’s electrical wiring.

Performance can be affected by:

Different electrical circuits
Extension leads
Surge protectors
Electrical noise
Appliances
Wiring condition
Distance

The advertised powerline rate is not the same as usable network throughput.

Test by connecting the computer directly to the router. If performance improves substantially, the powerline link may be responsible.

For a permanent business workspace, structured Ethernet cabling or a properly positioned access point is normally more predictable.

Check for Double NAT and Multiple Routers

Some networks contain:

An ISP router
A separate mesh router
Another firewall or router
Extenders operating in router mode

This can create multiple layers of Network Address Translation.

Double NAT does not always reduce ordinary download speed significantly, but it can complicate:

VPNs
Port forwarding
Gaming
Voice services
Remote access
Troubleshooting

Confirm which device is actually:

Connecting to the ISP
Assigning IP addresses
Providing Wi-Fi
Acting as the default gateway
Performing security inspection

A clear network diagram can prevent hours of testing the wrong router.

When the ISP Is the Likely Bottleneck

Evidence increasingly points towards the provider when:

Several devices are affected.
Wired and wireless tests are both poor.
The PC-to-router ping is healthy.
The router’s incoming speed is below expectation.
The connection repeatedly drops or resynchronises.
The ONT or router reports a line alarm.
Performance remains poor with one wired device.
The problem occurs before traffic reaches the wider internet.
Neighbours using the same provider report a fault.
The ISP confirms an outage or line problem.

Ofcom advises testing over Ethernet and contacting the provider when broadband speeds remain well below the estimate supplied at sign-up. Providers can also perform line testing to establish what the connection is receiving.

Before contacting the ISP, prepare:

Account or circuit reference:

Service package:

Router model:

Wired test results:

Dates and times:

Router sync or WAN speed:

Connection-drop times:

Tests performed:

Devices affected:

This provides better evidence than simply saying, “The Wi-Fi is slow.”

Your Minimum Guaranteed Speed

UK broadband providers should supply an estimate of the speed expected at your property. Many providers participate in Ofcom’s voluntary Broadband Speeds Code of Practice, which includes requirements involving realistic speed information and minimum guaranteed speed.

When contacting the provider:

Ask what speed reaches the router.
Ask whether the line is showing errors.
Ask whether an outage or congestion is known.
Quote the minimum guaranteed speed provided for the service.
Request a formal fault investigation where appropriate.

The minimum guarantee normally relates to the provider’s broadband connection—not Wi-Fi performance in a distant room.

When Your PC Is the Likely Bottleneck

Focus on the PC when:

Other devices are fast.
The same Ethernet cable works normally with another computer.
Speed drops only when the VPN is active.
Task Manager shows heavy local network use.
The adapter negotiates at an unexpectedly low rate.
The problem began after a driver update.
CPU or memory usage is extremely high.
Security software is malfunctioning.
The PC has an older Wi-Fi adapter.
A clean Windows profile or another operating system works normally.

Update the network driver

Use this order:

Windows Update
Optional Windows driver updates where relevant
The exact computer manufacturer
The network-adapter manufacturer only when appropriate

Avoid generic driver-updater applications.

Check power management

Laptop power-saving features can reduce wireless performance.

Test:

On mains power
On battery
Through the dock
Directly connected to the manufacturer-approved charger

Forget and reconnect to Wi-Fi

Open:

Settings > Network & internet > Wi-Fi > Manage known networks

Select the affected network and choose Forget, then reconnect.

Do this only when you possess the required password, certificate or company configuration.

Reset the Windows Network Stack Carefully

Microsoft recommends network reset only after less disruptive troubleshooting has failed. It removes installed network adapters and their settings, then reinstalls them after the PC restarts. VPN clients and virtual switches may need to be configured again.

Before using it, try these commands in Terminal as administrator:

netsh winsock reset

netsh int ip reset

ipconfig /release

ipconfig /renew

ipconfig /flushdns

Restart Windows afterwards.

Microsoft includes these commands in its official Windows network troubleshooting process.

Use full Network reset only when needed:

Settings > Network & internet > Advanced network settings > Network reset

On a business PC, consult IT first because the reset may affect:

VPN software
Hyper-V
Static IP settings
Virtual adapters
Network security tools
Specialist application networking

When the Destination Service Is the Bottleneck

Your router, ISP and PC may all be healthy while one service remains slow.

Possible evidence includes:

Several unrelated websites are fast.
Speed tests show expected performance.
Only one cloud platform is affected.
Colleagues in other locations report the same issue.
The service’s official status page reports disruption.
Another network produces the same problem.
The issue affects one region or tenant.

Examples can include:

Microsoft 365
A hosted accounting platform
A supplier portal
A remote desktop server
A company’s own website
A cloud storage provider

Do not replace the router because one remote server is overloaded.

A Fast Isolation Sequence

Use this order:

Test 1: Another website or service

If only one destination is slow, investigate that service.

Test 2: Another device

If only one PC is affected, investigate that PC.

Test 3: Move beside the router

If performance improves, investigate Wi-Fi coverage.

Test 4: Connect by Ethernet

If wired performance is good, the Wi-Fi path is the bottleneck.

Test 5: Check Ethernet link speed

If it negotiates at 100 Mbps, test the cable, port, dock and adapter.

Test 6: Ping the router

If local latency or loss is poor, the fault is inside the local network.

Test 7: Check the router’s WAN or line speed

If the router receives less than expected, investigate the line or ISP.

Test 8: Test with one wired device

This removes most wireless and multi-device variables.

Test 9: Repeat at different times

This identifies congestion and scheduled traffic.

Test 10: Contact the ISP with evidence

Provide wired results, times, router statistics and the expected service speed.

Common Mistakes to Avoid

Upgrading the broadband package first

A faster package will not repair weak Wi-Fi, a 100 Mbps Ethernet cable or an overloaded PC.

Blaming the ISP from a Wi-Fi speed test

The result includes the wireless connection between the device and router.

Testing only one device

You cannot tell whether the problem follows the device or the network.

Running one speed test

A single result may be affected by temporary traffic or the selected test server.

Restarting everything at once

You may improve the connection without discovering which component caused the problem.

Ignoring upload usage

Cloud backups and video uploads can make the entire connection feel unresponsive.

Testing through a VPN

Test with and without the VPN so its effect is clear.

Buying a new router without a wired baseline

The existing router may be delivering the ISP connection correctly.

Resetting Windows too early

Network reset cannot improve a poor broadband line or weak signal through a wall.

Focusing only on download speed

Latency, jitter and packet loss often matter more for real-time applications.

A Practical Bottleneck Checklist

When the internet feels slow:

Define whether the problem is speed, latency, loss or one application.
Record the time and symptoms.
Close unnecessary applications.
Pause large cloud transfers briefly.
Disconnect the VPN for a comparison.
Test another website.
Test another device.
Test beside the router.
Connect one PC directly by Ethernet.
Turn Wi-Fi off on the wired PC.
Check the Ethernet link speed.
Replace the test cable if necessary.
Run several speed tests.
Check upload as well as download.
Run ipconfig.
Ping the default gateway.
Run a longer 100-packet gateway test.
Check netsh wlan show interfaces.
Review the wireless network report.
Check Task Manager for network activity.
Review OneDrive, backup and update traffic.
Check the router’s WAN or line statistics.
Bypass mesh nodes, extenders and powerline adapters.
Test at different times of day.
Restart the router once.
Record whether the improvement lasts.
Update official router and network-adapter software.
Contact the ISP with the wired evidence.
Escalate difficult business problems to an experienced IT provider.

How Hamilton Group Can Help

A slow connection can waste hours when the ISP, router and Windows PC each appear to blame the others.

Hamilton Group’s experienced IT team can isolate the failure properly and identify which part of the connection needs attention.

Windows and Device Diagnosis

We can investigate:

Wi-Fi and Ethernet adapters
Drivers
Link negotiation
VPNs
DNS
Background traffic
Security software
Windows networking
Hardware faults

Router and Wireless Assessment

Hamilton Group can review:

Router capacity
Firmware
Wi-Fi bands
Channel congestion
Access-point placement
Mesh performance
Powerline adapters
Ethernet cabling
Traffic management

ISP Fault Evidence

We can collect:

Wired baseline tests
Packet-loss results
Latency patterns
Router line statistics
WAN connection information
Connection-drop times
Traceroute and path analysis

This allows us to present the ISP with useful technical evidence rather than relying on one wireless speed-test screenshot.

Business Network Troubleshooting

Where several employees are affected, we can determine whether the bottleneck involves:

Internet capacity
Upload saturation
Firewall performance
VPN gateways
Cloud backups
Microsoft 365
Wireless coverage
Internal switching
Cabling
ISP resilience

Connectivity Planning

Hamilton Group can also help businesses select and deploy:

Suitable broadband services
Backup internet connections
Managed routers and firewalls
Business Wi-Fi
Wired access points
Structured cabling
Connection monitoring
Automatic failover

Hamilton Group aims to make first contact on IT support requests within 15 minutes, helping businesses identify connectivity problems before they disrupt calls, cloud systems and daily work.

Find the First Point Where Performance Drops

The best troubleshooting question is not:

“Is my internet slow?”

It is:

“At which point between the PC and the destination does performance become slow?”

Start with another device, move close to the router and then test through Ethernet. Check the local link before blaming the ISP, and check the incoming broadband connection before replacing the PC.

When the wired connection is healthy but Wi-Fi is poor, fix the wireless network. When every wired device is slow and the router receives less than expected, involve the ISP. When only one PC is affected, investigate that PC.

Call 0330 043 0069, book a meeting with one of our experts or visit hgmssp.com for experienced help diagnosing routers, broadband connections, Wi-Fi and Windows networking.

Previous Next