The Website Obesity Crisis. Let me give you a concrete example.
I recently heard from a competitor, let’s call them ACME Bookmarking Co., who are looking to leave the bookmarking game and sell their website. While ACME has much more traffic than I do, I learned they only have half the daily active users. This was reassuring, because the hard part of scaling a bookmarking site is dealing with people saving stuff. We both had the same number of employees. They have an intern working on the project part time, while I dither around and travel the world giving talks.
We have similar revenue per active user. But where the projects differ radically is cost. I pay just over a thousand dollars a month for hosting, using my own equipment. So while I consider bookmarking a profitable business, to them it's a $4,000/month money pit. The point is that assumptions about complexity will anchor your expectations, and limit what you're willing to try. Our First Node.js App: Backbone on the Client and Server. Here at Airbnb, we’ve been looking curiously at Node.js for a long time now.
We’ve used it for odds and ends, such as the build process for some of our libraries, but we hadn’t built anything production-scale. Until now. The Problem There’s a disconnect in the way we build rich web apps these days. In order to provide a snappy, fluid UI, more and more of the application logic is moving to the client. But all too often, it’s not so clean; application logic is somewhat arbitrarily split between client and server, or in some cases needs to be duplicated on both sides.
If you’ve seen my tech talk or last blog post, then all this should sound familiar. This Holy Grail approach is something we had dreamt about for a long time, but not having any experience with Node.js, we didn’t quite know where to start. Our Solution I’m proud to announce that we’ve launched our first Holy Grail app into production! The performance gains are an awesome side effect of this design. Improving performance on twitter.com.
To connect you to information in real time, it’s important for Twitter to be fast.
This rule triggers when PageSpeed Insights detects that additional network round trips are required to render the above the fold content of the page.
Not just because we're performance wonks (guilty!) , but because we think speed is a competitive advantage. There's plenty of experimental data proving that the slower your website loads and displays, the less people will use it. [Google found that] the page with 10 results took 0.4 seconds to generate. WebPagetest - Website Performance and Optimization Test. Calibre.