Live data from Hacker News

The Fastest Blog in the World

jacquesmattheij.com

71–80 of 130 posts

Re: The Fastest Blog in the World

#71

Mine is very fast http://max.io I use wintersmith to generate it, and it is hosted by nginx in an EC2 t1.micro

Indeed it is! 330 ms on my connection, 5 requests, 18K data and 13 K in flight.

The funny thing is I didn't even try! Just feels like common sense. Maybe since I've been doing web stuff since '95 its in my blood to keep things tiny and simple.

Re: The Fastest Blog in the World

#72
> I’m sure I can do better still, for instance the CSS block is still quite large (too many rules, not minified yet)

CSS doesn't minify particularly well since the class names, tag names, and attributes all have to stay in their full form. Basically it just ends up being removing extraneous whitespace.

However, ever since reading James Hague's post on "Extreme Formatting"[0], I've rather liked CSS without all the extra whitespace. For example, [1]. You can see all the rules at a glance, and while it's a bit weird at first, I think you can get used to it pretty quickly. But then again, I've always sort of thought APL/J/K are beautiful in their own way.

[0] http://prog21.dadgum.com/200.html [1] http://prog21.dadgum.com/p21.css

Re: The Fastest Blog in the World

#73
post #36

Earlier quoted context omitted.

On the other hand, I don’t personally want autosuggest, analytics, G+ integration, live updates, an apps tray, or any of the rest. For me, Google’s homepage circa 2005 was just as useful as the current one (or more useful even, since their results weren’t as crapped up by SEO spam sites, and the search syntax itself was more power-user friendly and predictable). I used to occasionally click google ads, but they’ve go…

If you don't want that, make your own Google page. Create a form with get-action to google.com, parameter q, host this on your own site or even locally, and you've got that fast simple page that doesn't register your typing.

Or better yet, search right from the location bar of any modern browser, without any intermediary pages.

Re: The Fastest Blog in the World

#74
post #58
post #36

Earlier quoted context omitted.

If you don't want that, make your own Google page. Create a form with get-action to google.com, parameter q, host this on your own site or even locally, and you've got that fast simple page that doesn't register your typing.

Brilliant! I have been planning to do the same with youtube (in combination with youtube-dl) but kept postponing it. Your comment might give me the final motivation I need.

Here's a crude starting point:

    
        
            
                html,body { margin: 0, width: 100%; }
                body, input { font-family: Verdana, sans-serif; font-size: 1.2em; line-height: 1.4em; }
                form { margin: 20% auto; width: 26em; }
            
        
        
            
                
                
            
        
    

Re: The Fastest Blog in the World

#75

Earlier quoted context omitted.

Indeed it is! 330 ms on my connection, 5 requests, 18K data and 13 K in flight.

The funny thing is I didn't even try! Just feels like common sense. Maybe since I've been doing web stuff since '95 its in my blood to keep things tiny and simple.

I think one of the major differences is in how the content is generated. The more software that is used to make the content the larger the pages will be. If you hand-craft your page it will automatically be small and fast.

Re: The Fastest Blog in the World

#78
It's great to see focus on performance, especially after all the recent stories on web bloat.

I've noted a few techniques I've used on my blog to get pages served in a single request to users, including using SSIs and avoid cloudflare's "rocket loader"

http://www.pixelbeat.org/docs/web/about/#performance

Re: The Fastest Blog in the World

#79
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.

Apache has support for HTTP/2 today. A switch to nginx would mean to wait until they launch support later this year.
Post reply on HN