Question Ethernet and WiFi

Jun 8, 2025
13
0
10
So i have problem with ethernet. When im connected via ethernet pages on chrome and league of legends for example load very slowly. Loading youtube for example takes time, pages load very very slowly while on WiFi its working very good pages load very fast and everything is going smoothly (only sometimes i get disconnected in games for 2-3 seconds thats why i dont want to use wifi). Ethernet in games and download speed works very good, only loading pages is the problem. So i have been switching between lan and wifi. This happened when my internet provider changed my modem. On my old modem it worked very good but i cant change back now :). Any solutions?

[td]Vendor[/td][td]Ubee Interactive Corp.[/td] [td]Model[/td][td]EVW32C-0N-010[/td]

On idle on ethernet
Pinging www.google.com [142.251.39.68] with 32 bytes of data:
Reply from 142.251.39.68: bytes=32 time=28ms TTL=117
Reply from 142.251.39.68: bytes=32 time=26ms TTL=117
Reply from 142.251.39.68: bytes=32 time=26ms TTL=117
Reply from 142.251.39.68: bytes=32 time=28ms TTL=117
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 26ms, Maximum = 28ms, Average = 27ms

When opening youtube and pinging on ethernet
Pinging www.google.com [142.251.39.68] with 32 bytes of data
:Reply from 142.251.39.68: bytes=32 time=705ms TTL=117
Reply from 142.251.39.68: bytes=32 time=217ms TTL=117
Reply from 142.251.39.68: bytes=32 time=30ms TTL=117
Reply from 142.251.39.68: bytes=32 time=27ms TTL=117
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 705ms, Average = 244ms

On WiFi
Pinging www.google.com [142.251.39.68] with 32 bytes of data:
Reply from 142.251.39.68: bytes=32 time=14ms TTL=117
Reply from 142.251.39.68: bytes=32 time=13ms TTL=117
Reply from 142.251.39.68: bytes=32 time=14ms TTL=117
Reply from 142.251.39.68: bytes=32 time=14ms TTL=117
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 14ms, Average = 13ms

WiFi and Youtube
Pinging www.google.com [142.251.39.68] with 32 bytes of data:
Reply from 142.251.39.68: bytes=32 time=15ms TTL=117
Reply from 142.251.39.68: bytes=32 time=15ms TTL=117
Reply from 142.251.39.68: bytes=32 time=14ms TTL=117
Reply from 142.251.39.68: bytes=32 time=14ms TTL=117
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 15ms, Average = 14ms
 
1st - disable ipv6 on both adapters.
2nd - you're not showing entire command output.

19919167645585
 
  • Like
Reactions: kanewolf
Clear browser cache / change browsers?

Reset network card?

Did you set different DNS on ethernet and wifi?

Also change DNS to 8.8.8.8 / 8.8.4.4 and see if any improvement
 
Last edited:
I could see that happening on wifi since wifi buffers data that is damaged. Ethernet discards damaged data so you get packet loss not delays.

This is very strange.

Instead of some IP on the internet try to ping your router IP.

If it actually is some issue with the ethernet should happen here also. If it does not then it is going to be messy because it is going to be some software on the pc delaying the data. Again look for anything that talks about favor one kind of traffic over another. It is in the bloatware loaded on some motherboards and video cards...asus in particular is a very bad offender.
 
I could see that happening on wifi since wifi buffers data that is damaged. Ethernet discards damaged data so you get packet loss not delays.

This is very strange.

Instead of some IP on the internet try to ping your router IP.

If it actually is some issue with the ethernet should happen here also. If it does not then it is going to be messy because it is going to be some software on the pc delaying the data. Again look for anything that talks about favor one kind of traffic over another. It is in the bloatware loaded on some motherboards and video cards...asus in particular is a very bad offender.
When i refresh youtube page and ping
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=458ms TTL=64
Reply from 192.168.0.1: bytes=32 time=347ms TTL=64
Reply from 192.168.0.1: bytes=32 time=481ms TTL=64
Reply from 192.168.0.1: bytes=32 time=767ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 347ms, Maximum = 767ms, Average = 513ms

Idle is ok
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=20ms TTL=64
Reply from 192.168.0.1: bytes=32 time=19ms TTL=64
Reply from 192.168.0.1: bytes=32 time=20ms TTL=64
Reply from 192.168.0.1: bytes=32 time=19ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 20ms, Average = 19ms
 
This is absolutely bizarre.

Open Chrome browser and also open developer tools (or press ctrl+shift+i) and visit youtube.com or any site. on developer's tools window click Network tab and sort by "time" column and see what's the slowest/largest object to download on the webpage.

Even if there is a difference, ethernet usually is faster than wifi, not the other way around.

To WIndows apps, they don't know any difference between wifi or ethernet.
 
This is absolutely bizarre.

Open Chrome browser and also open developer tools (or press ctrl+shift+i) and visit youtube.com or any site. on developer's tools window click Network tab and sort by "time" column and see what's the slowest/largest object to download on the webpage.

Even if there is a difference, ethernet usually is faster than wifi, not the other way around.

To WIndows apps, they don't know any difference between wifi or ethernet.
View: https://imgur.com/a/Tn7vCRv
 
Do you have any (ad-blocking) extensions?

To launch Chrome without extensions, you can use the command-line argument --disable-extensions when starting Chrome. This argument can be added to the Chrome shortcut's target path.
 
Maybe nothing but are you running this in virtual machines. The ethernet function is being shared/emulated when you run some VM implementations.

Ethernet is basically a hardware function. Ping is a extremely simple command with almost no overhead. I can't see how you can get latency that high. The cable itself always transmit data at some fractional speed of light.
 
Do you have any (ad-blocking) extensions?

To launch Chrome without extensions, you can use the command-line argument --disable-extensions when starting Chrome. This argument can be added to the Chrome shortcut's target path.
Tried still the same
Maybe nothing but are you running this in virtual machines. The ethernet function is being shared/emulated when you run some VM implementations.

Ethernet is basically a hardware function. Ping is a extremely simple command with almost no overhead. I can't see how you can get latency that high. The cable itself always transmit data at some fractional speed of light.
Im not running in vm
do a tracert to youtube.com
Tracing route to youtube.com [142.251.208.174]
over a maximum of 30 hops:

1 19 ms 19 ms 19 ms 192.168.0.1
2 25 ms 40 ms 26 ms 10.70.0.1
3 114 ms 38 ms 192 ms sa-he-m-10-be3.sbb.rs [89.216.4.246]
4 28 ms 27 ms 27 ms bg-ne-m-0-be40.sbb.rs [89.216.6.158]
5 27 ms 27 ms 27 ms bg-tp-m-0-hg7-2.sbb.rs [89.216.5.248]
6 32 ms 45 ms 42 ms 72.14.219.230
7 546 ms 609 ms 475 ms 209.85.245.45
8 666 ms 33 ms 31 ms 216.239.49.77
9 32 ms 31 ms 32 ms bud02s43-in-f14.1e100.net [142.251.208.174]

Trace complete.

C:\Windows\System32>tracert youtube.com

Tracing route to youtube.com [142.251.208.174]
over a maximum of 30 hops:

1 19 ms 18 ms 19 ms 192.168.0.1
2 25 ms 25 ms 25 ms 10.70.0.1
3 262 ms 243 ms 237 ms sa-he-m-10-be3.sbb.rs [89.216.4.246]
4 27 ms 26 ms 27 ms bg-ne-m-0-be40.sbb.rs [89.216.6.158]
5 28 ms 27 ms 40 ms bg-tp-m-0-hg7-2.sbb.rs [89.216.5.248]
6 266 ms 128 ms 95 ms 72.14.219.230
7 32 ms 33 ms 33 ms 209.85.245.45
8 33 ms 32 ms 40 ms 216.239.49.77
9 33 ms 33 ms 31 ms bud02s43-in-f14.1e100.net [142.251.208.174]

Trace complete.