But then your css had to load... that was another 104ms. ;)
Pretty awesome.
PING hliyan.github.io:80 (http://hliyan.github.io):
connected to 103.245.222.133:80 (360 bytes), seq=0 time=525.96 ms
connected to 103.245.222.133:80 (360 bytes), seq=1 time=555.35 ms
Edit: Connecting from Sri Lanka though (not via Loon, just our regular old ISPs :)Your site is definitely better than most though.
Also, with respect to the numbers you quoted, those are much more related to how many hops the traffic has to traverse than how efficient your site is.
Pretty good though, I think if you inline the CSS you'll win hands down :)
The first Java version of an internal app we had converted from Progress 4GL used Java Webstart to dynamically load & launch, and because of programmer laziness (and the 93 3rd party Java components they'd included) it literally took 3 minutes to launch. That was the point where the manager -- who was a better programmer than anyone in the team, but who had previously been hands-off -- stepped in and created some rules and instituted code reviews. Still, though, totally insane behavior by so many young web programmers.
PING gotchacode.com:80 (/):
connected to 104.28.19.6:80 (651 bytes), seq=0 time=540.86 ms
^CGot signal 2
--- http://gotchacode.com/ ping statistics ---
1 connects, 1 ok, 0.00% failed, time 1259ms
round-trip min/avg/max = 540.9/540.9/540.9 msBut not as bad as most, so there's hope :)
robertsky$ ping localhost
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.051 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.042 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.049 ms
yep... looks right.