3 ms·
no-one tests on the actual problem devices which are low- to mid-range android phones on slow connections. I do. But I work in healthcare for the rural and po
by reaperducer 7y ago
no-one tests on the actual problem devices which are low- to mid-range android phones on slow connections.
I do. But I work in healthcare for the rural and poor. Some of my target devices the kind of craptastic phones people on HN would buy as a joke burner, but for millions of people is their entire family's only connection to the internet.
- microcolonel 7y agoAt the other end of the spectrum, I've worked on an ecommerce site where I was instructed to ignore that our JS payload was taking more than six seconds to parse on flagship phones (setting aside the network entirely). Worse still, after loading that code up, only then would it request the manifest that described 90% of the above-the-fold content. The decadence of web development today, particularly with agencies and large corporate customers, is truly boundless.
- nkrisc 7y agoFascinatingly, at a previous ecommerce gig, we had a similar issue. On of the developers ran a test where on one of our main pages, he added performance improvements to get the fastest speed to a reasonable place, and then segmented traffic into buckets that deliberately slowed the server response by various, increasing amounts of time. And wouldn't you know, it made almost no difference on our primary conversion metrics. As far as we could tell his methodology was sound, but unfortunately it got buried when it was discovered the findings could be abused to show that performance doesn't matter.