This was more interesting than I expected. Though they didn’t clarify why it costs $700,000, given the context I assume it’s customers on slower devices/connectivity leaving rather than something like bandwidth?
The funny thing is that internet speeds, back in 2006, were significantly lower than today. And here we are, with 10x the speeds and pages somehow loading slower than back then!
That was what I got from the article too. That the 700k was lost opportunity due to a poor user experience, not that it actually was them spending more money.
Often, it boils down to one common problem: Too much client-side JavaScript. This is not a cost-free error. One retailer realized they were losing $700,000 a year per kilobyte of JavaScript, Russell said.
“You may be losing all of the users who don’t have those devices because the experience is so bad,” he said.
They just didn’t link to the one retailer’s context. But it’s “bring back old reddit” energy directed at everything SPA.
This was more interesting than I expected. Though they didn’t clarify why it costs $700,000, given the context I assume it’s customers on slower devices/connectivity leaving rather than something like bandwidth?
Amazon found back in 2006 that every 100ms page load time resulted in -1% sales, and considering that they’re talking about bloat yeah, it’d be just from the increase load time/customers lost.
The funny thing is that internet speeds, back in 2006, were significantly lower than today. And here we are, with 10x the speeds and pages somehow loading slower than back then!
That was what I got from the article too. That the 700k was lost opportunity due to a poor user experience, not that it actually was them spending more money.
They just didn’t link to the one retailer’s context. But it’s “bring back old reddit” energy directed at everything SPA.
It’s a retailer so definitely lost sales or conversions
At $700k per kb, it really can’t be anyone other than Amazon.