3 ms·
The New York Times's Homepage isn't just text though. I see a lot of large, high-quality images, many of which transition to other images so you can see multipl
by Wowfunhappy 7y ago
The New York Times's Homepage isn't just text though. I see a lot of large, high-quality images, many of which transition to other images so you can see multiple visuals for a story. There's a "live updates" sidebar and a real-time stock ticker. There are video and audio embeds.
> Everyone else being bloated isn't an excuse.
It's not, but I'd rather focus on the worst offenders instead of the half-decent ones. I didn't compare it to Slack because I thought Slack was a good example—I did it for the exact opposite reason.
And, as long as there are sites that are so much heavier and yet seem to be doing fine (I don't like it, but it is what it is), I doubt NY Times is removing 3rd-party ads due to performance issues. It could be a nice side effect, though.
- vorpalhex 7y agoFor comparison, I disabled ublock origin and privacy badger and loaded https://fivethirtyeight.com https://fivethirtyeight.com which is in the same realm - heavy text content with several interactive widgets, video and audio embeds. Render time for my (aging) macbook pro is within the acceptable threshold (< 1500ms), memory snapshot in firefox is ~90Mb, and it feels like it loads quickly and responsively. It could be better - but it's infinitely more usable than NYT for me.
- deleted 7y ago[deleted]
- VHRanger 7y agoI don't think 1.5sec render time is acceptable for a webpage whose main payload of interest is 2-5kb of text (the article).
- JustFinishedBSG 7y agoThere's no articles on the page linked, and all the graphs on the right are dynamically rendered
- Intermernet 7y agoOptimisation opportunities: if you have a dynamically generated image, and you haven't yet received user input, statically generate it.
- fomine3 7y agoNYT is not app but website (IMO) but Slack is app. Not good comparison target.
- Intermernet 7y agoWebsites are apps, apps are websites. The area between each is a gradient, not black and white. The best way to measure this is to check a couple of metrics. Does this resource need to be generated dynamically? Related: can this resource be cached? More important: can this resource be resized? Often overlooked: do I need to process this javascript to provide the equivalent UX? The modern Web is terrible, and the modern state of app dev is terrible due to a substantial subset of the reasons that the modern Web is terrible.