• @HewlettHackard@lemmy.ca
    link
    fedilink
    English
    201 year ago

    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?

    • neil
      link
      fedilink
      English
      9
      edit-2
      1 year ago

      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-ish.

      edit to give it a little personal context: I was stuck on geosat internet for a little while and could not use amazon’s site across the connection. I’m not sure if they’re the retailer mentioned. But the only way I could make it usable was to apply the ublock rule *.images-amazon.com/*.js^ described here.

      What really stunk about it was that if you’re somewhere where geosat is/was the only option, then you’re highly dependent on online retail. And knowing how to manage ublock rules is not exactly widespread knowledge.

    • @malloc@programming.dev
      link
      fedilink
      English
      01 year ago

      One retailer realized they were losing $700,000 a year per kilobyte of JavaScript, Russell said.

      It’s a retailer so definitely lost sales or conversions

      • I Cast Fist
        link
        fedilink
        English
        81 year ago

        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!