After another review, to me it appears to be a connection issue. Ping and Tracert tests show that there are problems when reaching your server:
traceroute to naogu.es (217.76.132.165), 30 hops max, 60 byte packets
1 router36f254.local (192.168.15.1) 0.518 ms 0.490 ms 0.860 ms
2 192.168.14.1 (192.168.14.1) 1.775 ms 1.773 ms 1.750 ms
3 wsip-174-77-92-169.hr.hr.cox.net (174.77.92.169) 3.223 ms 3.207 ms 3.189 ms
4 172.21.224.153 (172.21.224.153) 5.053 ms 5.314 ms 5.019 ms
5 172.21.249.93 (172.21.249.93) 14.874 ms 14.871 ms 14.846 ms
6 ip-216-54-33-98.coxfiber.net (216.54.33.98) 14.819 ms 10.122 ms 5.476 ms
7 68.1.4.133 (68.1.4.133) 9.968 ms 9.941 ms 9.902 ms
8 xe-0-0-0.mad44.ip4.tinet.net (89.149.185.33) 119.941 ms 119.896 ms 119.895 ms
9 arsys-internet-gw.ip4.tinet.net (77.67.65.94) 119.883 ms 119.872 ms 119.854 ms
10 82.223.200.41 (82.223.200.41) 120.927 ms 120.279 ms 119.800 ms
11 82.223.200.2 (82.223.200.2) 125.075 ms 125.072 ms 125.015 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
PING naogu.es (217.76.132.165) 56(84) bytes of data.
^C
--- naogu.es ping statistics ---
26 packets transmitted, 0 received, 100% packet loss, time 25198ms
As I’m writing this however, I am seeing your site load much faster for me. It may be that not all routers along the way are setup to respond correctly to tracert’s.
Are you seeing any improvement in your site’s loading time?