4 ms·

Most users cannot distinguish when websites are hogging resources. Metrics like the first paint, first meaningful paint and time to interactive are usually more

Most users cannot distinguish when websites are hogging resources. Metrics like the first paint, first meaningful paint and time to interactive are usually more important than memory usage. Memory usage sure will help but it is mudding water more than more specific user-centric metrics. Sometimes for business applications(Slack) feature richness and in-app performance is more important than memory usage. It all depends on website/application and throwing tantrum about memory usage do not help.

TeMPOraL 8y ago
> Most users cannot distinguish when websites are hogging resources. Of course they can. The user happily works on their computer. They open your site. Their browser (or entire computer) starts to lag shortly after. Doesn't take a genius to connect the dots, especially after this happening several times. > Metrics like the first paint, first meaningful paint and time to interactive Those are metrics for maximizing amount of people not closing your site immediately; not for minimizing the misery they have to suffer through.
- Chyzwar 8y ago
  > Of course they can. The user happily works on their computer. They open your site. Their browser (or entire computer) starts to lag shortly after. Doesn't take a genius to connect the dots, especially after this happening several times. Most users have 20 and more websites/tabs open at the same time. Most users do not even know what is a memory. Funny enough for most users, after initial load JavaScript rich SPA will be perceived as more snappy than a server-side rendered page but it will use more resources on the client side. > Those are metrics for maximizing amount of people not closing your site immediately; not for minimizing the misery they have to suffer through. These metrics are what is important for users. Users do not care how much resources your application consumes. What matter is performance perceived by the users. https://developers.google.com/web/fundamentals/performance/user-centric-performance-metrics https://developers.google.com/web/fundamentals/performance/u...

TeMPOraL 8y ago

> Most users cannot distinguish when websites are hogging resources. Of course they can. The user happily works on their computer. They open your site. Their browser (or entire computer) starts to lag shortly after. Doesn't take a genius to connect the dots, especially after this happening several times. > Metrics like the first paint, first meaningful paint and time to interactive Those are metrics for maximizing amount of people not closing your site immediately; not for minimizing the misery they have to suffer through.

Chyzwar 8y ago
> Of course they can. The user happily works on their computer. They open your site. Their browser (or entire computer) starts to lag shortly after. Doesn't take a genius to connect the dots, especially after this happening several times. Most users have 20 and more websites/tabs open at the same time. Most users do not even know what is a memory. Funny enough for most users, after initial load JavaScript rich SPA will be perceived as more snappy than a server-side rendered page but it will use more resources on the client side. > Those are metrics for maximizing amount of people not closing your site immediately; not for minimizing the misery they have to suffer through. These metrics are what is important for users. Users do not care how much resources your application consumes. What matter is performance perceived by the users. https://developers.google.com/web/fundamentals/performance/user-centric-performance-metrics https://developers.google.com/web/fundamentals/performance/u...