Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Even if you did lose 1% of customers because of 100ms delay; that could be a good thing.

The kind of customer who would change their mind about purchasing something because of 100ms delay may not be the kind of customer that you'd want to do business with anyway.

If 100ms is all it takes to put this customer off; maybe it means that they didn't really want to buy that thing to begin with... That kind of customer is probably more likely to get buyer's remorse, to file a complaint, require follow-up and demand a refund.

My point here is that it's silly to just look at statistics as black-and-white good or bad and pretend that they tell a complete story.



100ms additional delay, not 100ms delay. Someone could be patiently waiting for 2 seconds and hit back, just as it was about to load 100ms later.


I was assuming that. 100ms is barely enough time for the request to reach the server depending on the location.


In my experience 10% of the customers cause 90% of the trouble, and they're usually the cheapest ones.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: