Hi Guys - I'm the Yottaa guy. Agree with lots of things said here. However, each company operates within its own context and the popular way may not be the appropriate way for a particular company.
For Yottaa, from our background and industry experience (In my previous life, I started and grew an enterprise software company to profitability. I have also been involved with quite a few startups from initial formation to successful exits), we knew there is a $billion market for what we do because it is a proven market (It really doesn't take a genius to know there is a big market for web performance, monitoring and security). We also knew that we can execute on the ideas (normally it would take some real work to convince others about one's execution capability. Fortunately in our case, our decisions don't require us convincing other people to make). So we can skip the some of the initial "validated learning" process (not entirely, but a part of it). It is risky to skip some of it - however, that is the risk we decided to take anyway.
More importantly, as I learned from personal experiences, the biggest startup challenge is growth. The major hurdle to success is not financing, getting the first 10 customers, getting to the first million dollar revenue or even the first $5M revenue - we have done these before and lots of people have done these before. However, it is exponentially challenging to grow from $10M to $100M in revenue. Out of 1000 startups, there may be 100 get funded and 50 actually get to a million dollar in revenue, but there are probably only 5 get to $50M revenue.
Another important aspect to take into consideration is the kind of product that we are building at Yottaa. As highly distributed software service that optimizes and processes Internet traffic in real time, it takes more than five smart engineers to reach the basic level of performance, reliability and scalability.
There are quite a few other reasons that drove this decision that I won’t bore you folks further. In the end, we decided to take the approach we took. After a lot of real hard work and experiments, we have figured out the right process, people and methodology to be extremely effective and scalable. We have been able to roll out a major product every 3 months:
Late 2011: Site Optimizer
Jan 2012: Web Performance API
Feb 2012: Yottaa CDN
May 2012: Yottaa Mobile Acceleration Service
(lots more coming soon).
The pace of development and efficiency is fairly rapid. In 6 months, our Optimizer has grown to from 0 to over 100M unique visitors per month. So we are definitely seeing the benefits of our model now.
Like the result from the article. Showing the page load time vs percent of users is a very useful way to analyze site performance:how many percentage of site users are experiencing slow performance?
Further, combing this with web timing API would be even more interesting.
Great news. Google Chrome and FireFox both are adding support for Web Timing API. This is great for web development community (posted updated accordingly).
Good point. Tumblr is a lot faster than Posterous. However, it is only at about 50 percentile comparing to other sites over the Internet while Posterous is below average - in other words, Tumblr's performance is only about average. Both have lots to be improved.
Does a fast site help improve business success(comparing to a slower site similar in functionality)? Of course it does. Does performance play a role? It does. Is it the only reason? No.
The article does not pinpoint the success or failure of a business into a single reason. The article didn't claim "performance is The reason" that Tumblr is successful. It says "performance is most likely one of the key factors".
no, actually it does matter. Browser caching is not reliable and only covers around 20% to 25% of requests (according to GoogleMaps JS caching behavior stats). So it matters quite a bit.
Does web performance matter? For Tumblr and other light blogging service providers, clearly it does and it made a big difference. A recent New York Times article pointed out that "Tumblr Leaves Posterous In the Dust". Both are leading light blogging service providers. However, Tumblr has out-grown Posterous significantly over the last year. Why? it looks like that one big reason is that Tumblr has been twice as fast as Posterous.
The score shows as "0" initially until we've collected data from different geographic locations, which may take a little while Sometimes users mistake this "0" as the final score and didn't know they should wait until the score gets updated. We are aware of this issue and will fix this in future releases.
For Yottaa, from our background and industry experience (In my previous life, I started and grew an enterprise software company to profitability. I have also been involved with quite a few startups from initial formation to successful exits), we knew there is a $billion market for what we do because it is a proven market (It really doesn't take a genius to know there is a big market for web performance, monitoring and security). We also knew that we can execute on the ideas (normally it would take some real work to convince others about one's execution capability. Fortunately in our case, our decisions don't require us convincing other people to make). So we can skip the some of the initial "validated learning" process (not entirely, but a part of it). It is risky to skip some of it - however, that is the risk we decided to take anyway.
More importantly, as I learned from personal experiences, the biggest startup challenge is growth. The major hurdle to success is not financing, getting the first 10 customers, getting to the first million dollar revenue or even the first $5M revenue - we have done these before and lots of people have done these before. However, it is exponentially challenging to grow from $10M to $100M in revenue. Out of 1000 startups, there may be 100 get funded and 50 actually get to a million dollar in revenue, but there are probably only 5 get to $50M revenue.
Another important aspect to take into consideration is the kind of product that we are building at Yottaa. As highly distributed software service that optimizes and processes Internet traffic in real time, it takes more than five smart engineers to reach the basic level of performance, reliability and scalability.
There are quite a few other reasons that drove this decision that I won’t bore you folks further. In the end, we decided to take the approach we took. After a lot of real hard work and experiments, we have figured out the right process, people and methodology to be extremely effective and scalable. We have been able to roll out a major product every 3 months:
Late 2011: Site Optimizer Jan 2012: Web Performance API Feb 2012: Yottaa CDN May 2012: Yottaa Mobile Acceleration Service (lots more coming soon).
The pace of development and efficiency is fairly rapid. In 6 months, our Optimizer has grown to from 0 to over 100M unique visitors per month. So we are definitely seeing the benefits of our model now.
How successful can this model be? Time will tell.