Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Fastest Blog in the World

jacquesmattheij.com

Post reply on HN
Print view View original

61–70 of 130 posts

Re: The Fastest Blog in the World

#61

Post by jacquesm »

kmfrk wrote: post #47
aorth wrote: post #39

Earlier quoted context omitted.

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!

No idea either but for when you do here is the Hugo breakdown:

  302 pages created
  267 categories created
  gin 1149 ms

  real    0m1.613s
  user    0m1.180s
  sys     0m0.408s

Re: The Fastest Blog in the World

#62

Post by mundanevoice »

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…

Mine is even faster than you.

   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 ms

Re: The Fastest Blog in the World

#63

Post by design-of-homes »

How does my blog compare? I submitted this link to Hacker News yesterday. It's quite an image heavy page but I think (I hope!) it loads quite fast for most users. It obviously won't be as fast as a text-only page. There are no fancy optimisation tricks. Just plain HTML and CSS and a tiny bit of Javascript (for older browsers). Not responsive either, but readable on mobile.

http://www.designofhomes.co.uk/042-tour-bois-le-pretre.html

Re: The Fastest Blog in the World

#64

Post by bhaak »

Animats wrote: post #28

Here's a page of mine that's almost 20 years old.[1] Look at the page source. That's HTML in its pure form. No styling at all. Looking at the page source for the "fastest blog", there's still far more formatting info than content. Much of that bloat isn't doing anything. [1] http://www.animats.com/papers/leggedrun/leggedrun.html

HTML in its pure form doesn't render well on current mobile devices.

It's idiotic that you are punished when you use HTML like it was supposed to be used but that's unfortunately how the mobile browsers work currently.

Re: The Fastest Blog in the World

#65

Post by jacquesm »

design-of-homes wrote: post #63

How does my blog compare? I submitted this link to Hacker News yesterday. It's quite an image heavy page but I think (I hope!) it loads quite fast for most users. It obviously won't be as fast as a text-only page. There are no fancy optimisation tricks. Just plain HTML and CSS and a tiny bit of Javascript (for older browsers). Not responsive either, but readable on mobile. http://www.designofhomes.co.uk/042-tour-bois…

That's pretty good actually. You're very heavy on visuals but that's to be expected given the nature of the page and the only things you could do to make it faster are to lose the font and inline the CSS, but likely the gains in your case would be minimal so I'd just leave it as it is. Good job!

Re: The Fastest Blog in the World

#67

Post by chrismorgan »

jacquesm wrote: post #43
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 :)

Things like resource inlining are an antipattern in an HTTP/2 world. The stylesheet for example should not be inlined; the server should instead push the stylesheet out to the user agent proactively (typically three frames—a PUSH_PROMISE telling the client of the request that is being simulated, then a HEADERS and a DATA frame with the response).

The first time, the browser will receive it approximately as fast as the inlined version; subsequent times, there is no overhead, moreover browsers can load the stylesheet only once rather than needing to load it for every page.

Re: The Fastest Blog in the World

#70

Post by fauigerzigerk »

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…

>If the only change is that it loads faster, and he doesn't grow his audience, then he hasn't really achieved anything.

Sure he has achieved something. He has made his readers a little bit happier. Presumably, he has also made himself a little bit happier. It's called progress.

Post reply on HN