11 ms·

Depending on what you're building, I don't find 100k to be that much .

• thdrdt 6y ago
  It's not only filesize it's also what the browser must parse. Parsing huge files is not a great experience on mobile.
  • warent 6y ago
    I'm trying to imagine what browser is so outdated that it struggles to parse 100kb of javascript
    • Touche 6y ago
      It's not the browser, it's the processor that's in most non-iPhones.
      • true_religion 6y ago
        Samsung phones and Pixels aren’t that bad either. I am not saying it to be proud, but I tested our 3mb internal app with a 5 year old android phone, and worked. The only time it was slow is if the browser itself was old (e.g. Chrome 44).
      • kangoo1707 6y ago
        All browser processes 100KB of scripts just fine. And they process the scripts in the background. The HTML is already parsed and displayed.
• ehutch79 6y ago
  For low end android devices on a network in rural areas, that's a lot.
  • fastball 6y ago
    I would guess that for the majority of JS-heavy websites, android users in rural areas probably do not make up that much of the target market.
    • Touche 6y ago
      It's unrelated to network conditions (those just make it worse). It's related to the processor in many mobile phones.