[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
http://www.vanheusden.com/httping/ is a simple tool that can check basic load times, i.e. you will notice Wordpress is a lot slower than a statically built site and if your Website is up. In the dead of the night from my Bitfolk server I get: hendry@uk ~$ httping http://www.dcglug.org.uk/ PING www.dcglug.org.uk:80 (http://www.dcglug.org.uk/): connected to 80.68.88.22:80 (522 bytes), seq=0 time=2856.95 ms connected to 80.68.88.22:80 (522 bytes), seq=1 time=868.36 ms connected to 80.68.88.22:80 (522 bytes), seq=2 time=602.40 ms connected to 80.68.88.22:80 (522 bytes), seq=3 time=436.12 ms connected to 80.68.88.22:80 (522 bytes), seq=4 time=428.20 ms connected to 80.68.88.22:80 (522 bytes), seq=5 time=392.82 ms connected to 80.68.88.22:80 (522 bytes), seq=6 time=462.64 ms connected to 80.68.88.22:80 (522 bytes), seq=7 time=1558.37 ms connected to 80.68.88.22:80 (522 bytes), seq=8 time=1160.73 ms connected to 80.68.88.22:80 (522 bytes), seq=9 time=1187.15 ms ^CGot signal 2 connected to 80.68.88.22:80 (522 bytes), seq=10 time=757.16 ms --- http://www.dcglug.org.uk/ ping statistics --- 11 connects, 11 ok, 0.00% failed round-trip min/avg/max = 392.8/973.7/2856.9 ms Compare that with Google... hendry@uk ~$ httping http://www.google.com PING www.google.com:80 (http://www.google.com): connected to 173.194.78.106:80 (767 bytes), seq=0 time=18.12 ms connected to 173.194.78.106:80 (767 bytes), seq=1 time=16.71 ms connected to 173.194.78.106:80 (767 bytes), seq=2 time=16.38 ms connected to 173.194.78.106:80 (767 bytes), seq=3 time=16.05 ms connected to 173.194.78.106:80 (767 bytes), seq=4 time=17.32 ms ^CGot signal 2 --- http://www.google.com ping statistics --- 5 connects, 5 ok, 0.00% failed round-trip min/avg/max = 16.1/16.9/18.1 ms -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq