Why does my SmartPhone get better speeds and latency then my TP-Link Archer T4U?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Why does my SmartPhone get better speeds and latency then my TP-Link Archer T4U?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Why does my SmartPhone get better speeds and latency then my TP-Link Archer T4U?
Why does my SmartPhone get better speeds and latency then my TP-Link Archer T4U?
2015-09-11 07:46:34
Model : TP-Link Archer T4U

Hardware Version : FCC ID: TE7T4U

Driver Version: 1027.4.1120.2014

ISP : Altibox.no (Norway)

These tests are taken at the exact same place from the routers location, and the difference is crazy. Just the latency difference makes me want to cry.
Whats the deal here? Ive tried several USB Hubs as well as reinstalling the driver several times.

http://i.imgur.com/vu4P40c.jpg (The ping on the PC was 23 by the way)

Both tests are done on the 5GHz band and at the exact same time (well not simultaneously obviously)
  0      
  0      
#1
Options
2 Reply
Re:Why does my SmartPhone get better speeds and latency then my TP-Link Archer T4U?
2015-09-11 17:05:12
What's the operating system of your PC installed T4U?
Check the link speed showing on wireless network connection on your PC.
  0  
  0  
#2
Options
Re:Why does my SmartPhone get better speeds and latency then my TP-Link Archer T4U?
2015-09-11 19:08:24
Im on WIndows 10 64bit
http://i.imgur.com/ygrznfi.png

It's steadily on 325Mpbs, but I did see it drop to 45 for just a split second while looking at it. I only saw this happens once tho in the time span of several minutes

These are the times I get when pinging the router

Pinging 198.162.0.1 with 32 bytes of data:
Reply from 198.162.0.1: bytes=32 time=110ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=112ms TTL=238
Reply from 198.162.0.1: bytes=32 time=109ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=109ms TTL=238
Reply from 198.162.0.1: bytes=32 time=109ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=111ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=108ms TTL=238
Reply from 198.162.0.1: bytes=32 time=119ms TTL=238
Reply from 198.162.0.1: bytes=32 time=109ms TTL=238


These are the times I get when pinging a server close to me. The spikes in latency worries me.

Pinging hit.no [128.39.198.70] with 32 bytes of data:Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=21ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=19ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=16ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
Reply from 128.39.198.70: bytes=32 time=8ms TTL=52
  0  
  0  
#3
Options