over wifi - 30ms to google - that seems normal. Maybe switching to a 5GHz connection might reduce it a bit (to 25-28ms perhaps).

I personally don't think you can improve much. That's just the nature of Wi-Fi. You're better off just using a LAN cable instead of spending money on equipments to improve latency.

What is the latency you get when ping to router IP address (Maxis is 192.168.1.254)?

I too get about 30ms ping to Google. But my ping over wifi to Maxis router (192.168.1.254) is 1-2ms.
However the ping to next hop in ISP network is about 28ms. Seems like the poor latency is coming from the network side.

Didn't notice any improvement when testing with RT-AC66U. I'm on TM VDSL access, how about you?

C:\>tracert www.google.com

Tracing route to www.google.com [74.125.135.106]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms dsldevice.lan [192.168.1.254]
2 33 ms 30 ms 27 ms 58.71.243.253
3 39 ms 64 ms 30 ms 58.71.243.254
4 37 ms 47 ms 41 ms 58.71.243.53
5 31 ms 31 ms 31 ms 58.71.243.49
6 32 ms 31 ms 30 ms 58.71.244.254
7 32 ms 70 ms 32 ms 58.71.241.57
8 31 ms 30 ms 31 ms 58.71.241.30
9 32 ms 33 ms 31 ms 202.151.241.145
10 31 ms 30 ms 29 ms 202.151.241.162
11 32 ms 31 ms 33 ms 121.123.132.14
12 32 ms 32 ms 34 ms 209.85.242.236
13 33 ms 36 ms 34 ms 209.85.241.173
14 * * * Request timed out.
15 33 ms 31 ms 31 ms ni-in-f106.1e100.net [74.125.135.106]

Trace complete.

C:\>ping 192.168.1.254 -t

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.1.254:
Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 5ms, Average = 2ms
Control-C
^C
C:\>ping 58.71.243.253 -t

Pinging 58.71.243.253 with 32 bytes of data:
Reply from 58.71.243.253: bytes=32 time=29ms TTL=253
Reply from 58.71.243.253: bytes=32 time=29ms TTL=253
Reply from 58.71.243.253: bytes=32 time=26ms TTL=253
Reply from 58.71.243.253: bytes=32 time=26ms TTL=253
Reply from 58.71.243.253: bytes=32 time=27ms TTL=253
Reply from 58.71.243.253: bytes=32 time=27ms TTL=253
Reply from 58.71.243.253: bytes=32 time=27ms TTL=253
Reply from 58.71.243.253: bytes=32 time=29ms TTL=253
Reply from 58.71.243.253: bytes=32 time=28ms TTL=253
Reply from 58.71.243.253: bytes=32 time=28ms TTL=253

Ping statistics for 58.71.243.253:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 29ms, Average = 27ms
Control-C
^C
C:\>

This post has been edited by gogetter83: Dec 28 2013, 01:38 AM

as far as I know, TP-link still doesn't work properly with maxis IPTV despite their claims.