Yes correct. Those are all possibilities that have to be considered one by one and eliminated. But based on the results above, it is unlikely the reason for the issues at this stage.
The answer is as I and others have indicated is to completely exclude wi fi out of the equation with a cable connection to the router, disabling wifi as well.
OKAY I think we are onto something here daniellgr. Look at the two traces below.
First is from my Macbook using WiFi.
Second is from a Windows PC wired to the router (because as I said Macbook Pro has no bloody lan port)
traceroute to lb.wordpress.com (192.0.78.13), 64 hops max, 52 byte packets
1 broadcom.home (10.0.0.2) 2.345 ms 2.352 ms 2.076 ms
2 * * *
3 cdsl1-rba-vl2253-ipc.ip.isnet.net (196.38.73.182) 256.367 ms 155.168 ms 253.673 ms
4 cdsl1-rba-vl2253.ip.isnet.net (196.38.73.181) 43.439 ms 39.255 ms 25.782 ms
5 cdsl1-rba-vl150.ip.isnet.net (196.38.73.17) 25.054 ms 24.855 ms 24.814 ms
6 core2b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.63) 26.317 ms 28.188 ms 27.016 ms
7 168.209.201.93 (168.209.201.93) 199.417 ms 200.692 ms 199.051 ms
8 core1b-dock-ten-0-3-0-0sub2.ip.isnet.net (168.209.246.1) 207.231 ms 204.550 ms 201.883 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Tracing route to lb.wordpress.com [192.0.78.13]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Broadcom.Home [10.0.0.2]
2 * * * Request timed out.
3 24 ms 24 ms 24 ms cdsl1-rba-vl2253-ipc.ip.isnet.net [196.38.73.182]
4 67 ms 61 ms 26 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
5 25 ms 24 ms 24 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 29 ms 33 ms 25 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
7 205 ms 204 ms 197 ms 168.209.201.93
8 200 ms 203 ms 202 ms core1b-dock-ten-0-3-0-0sub2.ip.isnet.net [168.209.246.1]
9 226 ms 226 ms 207 ms 195.66.226.127
10 195 ms 194 ms 195 ms 192.0.78.13
Trace complete.