The Fastest Blog in the World
jacquesmattheij.com
The Fastest Blog in the World
1–10 of 130 posts
Re: The Fastest Blog in the World
#2Re: The Fastest Blog in the World
#3Re: The Fastest Blog in the World
#4Very 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.
Re: The Fastest Blog in the World
#5Re: The Fastest Blog in the World
#6Browser caches solve a lot of things for us. Though you're still parsing a bunch of JS, google's front page is "only" fetching 56kb
Granted, this blog post is 13.5kb, but it doesn't have an entire search app embedded into it (with the whole search results automatically appearing thing, I imagine that inside that 56kb is pretty much all the code required for all of google's little widgets in the search results)
Anyways, always fun to see somebody go in and rip out as much cruft as possible
Re: The Fastest Blog in the World
#7Very 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.
Re: The Fastest Blog in the World
#8Is there a better way to have fast-loading comments than outsourcing them to Twitter/HN or Discus?
Re: The Fastest Blog in the World
#9That'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 have worked in the early days, when VC money took care of lack of income sources).
Re: The Fastest Blog in the World
#10I guess you're optimizing for people who only visit one page and bounce away?
Well, come to think of it, the majority of visitors who followed this HN link is never going to navigate past the single page that was linked. So it probably makes sense for optimize for them, at the expense of repeat visitors who will have to download the stylesheet over and over again.