The Fastest Blog in the World • Hacker News Board

Re: The Fastest Blog in the World

#41

Post by robbiep » Mon, Aug 03, 2015, 9:05 AM UTC

onion2k wrote: post #18

This is absolutely brilliant if the only metric your audience cares about is page load time . For most sites that's only part of the story. Take the first paragraph, about how Google's homepage of just a textbox should really be a few hundred bytes instead of a megabyte. Google's homepage does a lot more than just enabling you to enter a search - there's the autosuggest feature, there's analytics, the apps tray, G+ i…

I don't know, bloat is pretty important for mobile users. I've managed to chisel an entire business out of providing content for a specific population of users that access that information frequently, as well as (due to Mobile data limits) demand small or minimal download sizes.

If there wasn't so much crud being transmitted I would be out an entire business, on the other hand, the entire internet would be a much nicer place

Re: The Fastest Blog in the World

#42

Post by robertsky_ » Mon, Aug 03, 2015, 9:05 AM UTC

hendry wrote: post #15

Mine is faster :) https://github.com/kaihendry/natalian X1C3:~$ httping http://natalian.org PING natalian.org:80 (/): connected to 54.192.159.125:80 (147 bytes), seq=0 time= 91.36 ms connected to 54.192.159.123:80 (147 bytes), seq=1 time= 28.63 ms ^CGot signal 2 --- http://natalian.org/ ping statistics --- 2 connects, 2 ok, 0.00% failed, time 1394ms round-trip min/avg/max = 28.6/60.0/91.4 ms X1C3:~$ httping http://ja…

  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.

Re: The Fastest Blog in the World

#43

Post by jacquesm » Mon, Aug 03, 2015, 9:07 AM UTC

aorth wrote: post #3

Very zippy indeed! Have you thought about switching to nginx so you can get SPDY (and soon HTTP/2)? Also, Hugo is cool. I've evaluated it myself, but I have 8 years of WordPress archives -- ~500 posts -- and I worry about things like images, comments, etc.

The benefits from SPDY are probably not going to help much if you only do one request :)

Re: The Fastest Blog in the World

#44

Post by keithpeter » Mon, Aug 03, 2015, 9:07 AM UTC

pjc50 wrote: post #32

coldtea wrote: post #9

> I positively hate bloat in all its forms. Take the Google homepage. It’s a one liner text field and two buttons. It weighs in at a whopping 1170 kilobytes! That’s more than a megabyte for what technically should not take more than a few hundred bytes. That's because you didn't consider the business reasons behind it being 1170Kb. If it was your "few hundrend bytes" design it would have sank the company (or only hav…

The Google home page from 1998 really is a one line text field and two buttons. https://web.archive.org/web/19981111183552/http://google.sta... It only really starts getting js-heavy after about 2010. Evidently the relative cost of bandwidth and value of analytics have crossed over.

I remember first seeing google and it seemed so amazingly clean and fast compared to AltaVista. We were using a 64k leased line into the small college I worked in at that time, and I had a 28k8 modem at home.

As we move to price per Gb of download from 'all you can eat' I think that page payload may become more important.

Re: The Fastest Blog in the World

#45

Post by hliyan » Mon, Aug 03, 2015, 9:08 AM UTC

hendry wrote: post #15

Mine is faster :) https://github.com/kaihendry/natalian X1C3:~$ httping http://natalian.org PING natalian.org:80 (/): connected to 54.192.159.125:80 (147 bytes), seq=0 time= 91.36 ms connected to 54.192.159.123:80 (147 bytes), seq=1 time= 28.63 ms ^CGot signal 2 --- http://natalian.org/ ping statistics --- 2 connects, 2 ok, 0.00% failed, time 1394ms round-trip min/avg/max = 28.6/60.0/91.4 ms X1C3:~$ httping http://ja…

I don't get it. Mine's pretty stripped down but I still get this: :(

   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 :)

Re: The Fastest Blog in the World

#46

Post by eterm » Mon, Aug 03, 2015, 9:10 AM UTC

onion2k wrote: post #18

This is absolutely brilliant if the only metric your audience cares about is page load time . For most sites that's only part of the story. Take the first paragraph, about how Google's homepage of just a textbox should really be a few hundred bytes instead of a megabyte. Google's homepage does a lot more than just enabling you to enter a search - there's the autosuggest feature, there's analytics, the apps tray, G+ i…

There's also the "Billion Dollar line of javascript"[1] which focuses your input on the search box.

[1] https://www.branded3.com/blog/billion-dollar-javascript/

Re: The Fastest Blog in the World

#47

Post by kmfrk » Mon, Aug 03, 2015, 9:10 AM UTC

aorth wrote: post #39

kmfrk wrote: post #7

Earlier quoted context omitted.

Doing an import is hardly going to ruin your existing installation. Back up your blog and do the Jekyll import, and see if it’s worth switching to you. :)

Indeed! It is rather a limit on time. :P

I actually don’t know how fast Jekyll builds blog posts nowadays, but it has been a little on the slow side at one point.

No idea how it’d handle 500 blog posts - but there’s only one way of finding out!

Re: The Fastest Blog in the World

#48

Post by jacquesm » Mon, Aug 03, 2015, 9:12 AM UTC

hliyan wrote: post #45

hendry wrote: post #15

Mine is faster :) https://github.com/kaihendry/natalian X1C3:~$ httping http://natalian.org PING natalian.org:80 (/): connected to 54.192.159.125:80 (147 bytes), seq=0 time= 91.36 ms connected to 54.192.159.123:80 (147 bytes), seq=1 time= 28.63 ms ^CGot signal 2 --- http://natalian.org/ ping statistics --- 2 connects, 2 ok, 0.00% failed, time 1394ms round-trip min/avg/max = 28.6/60.0/91.4 ms X1C3:~$ httping http://ja…

I don't get it. Mine's pretty stripped down but I still get this: :( 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 :)

7 requests, 300K, the other is 2 requests, 90K, mine is 1 request, 49K.

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.

Re: The Fastest Blog in the World

#49

Post by hendry » Mon, Aug 03, 2015, 9:13 AM UTC

jacquesm wrote: post #40

hendry wrote: post #15

Mine is faster :) https://github.com/kaihendry/natalian X1C3:~$ httping http://natalian.org PING natalian.org:80 (/): connected to 54.192.159.125:80 (147 bytes), seq=0 time= 91.36 ms connected to 54.192.159.123:80 (147 bytes), seq=1 time= 28.63 ms ^CGot signal 2 --- http://natalian.org/ ping statistics --- 2 connects, 2 ok, 0.00% failed, time 1394ms round-trip min/avg/max = 28.6/60.0/91.4 ms X1C3:~$ httping http://ja…

I'm pretty far away from you, you have to discount for the network. Pretty good though, I think if you inline the CSS you'll win hands down :)

I don't like the idea of having reproduced CSS in each page. style.css should be optimal. :)

Re: The Fastest Blog in the World

#50

Post by jacquesm » Mon, Aug 03, 2015, 9:16 AM UTC

hendry wrote: post #49

jacquesm wrote: post #40

Earlier quoted context omitted.

I'm pretty far away from you, you have to discount for the network. Pretty good though, I think if you inline the CSS you'll win hands down :)

I don't like the idea of having reproduced CSS in each page. style.css should be optimal. :)

It should be, but measurements bear out that it isn't...