One thing I've noticed is that almost all new web frameworks I come across nowadays seems to be catered towards search engine optimization (i.e.: getting 99/100 on Google PageSpeed Insights).
It's a very specific kind of performance. It doesn't measure long running apps, interactions and visualizations.
When you play a video game you might have to download and install it first, which might take quite a while, but we don't say "this game has bad performance" because of that.
Lighthouse measures that first second or first few seconds after you visit a site at position 0/0. It doesn't care about how much bloat comes after you scroll. It discourages you to pre-load resources (including JS and CSS) which you don't _immediately_ need for that first hit.
It is really about content and marketing websites with low interaction. You can absolutely make good interactive applications that also get a high Lighthouse score, but the overlap is not necessarily always feasible or the best tradeoff to make.
hoten|3 years ago
dgb23|3 years ago
When you play a video game you might have to download and install it first, which might take quite a while, but we don't say "this game has bad performance" because of that.
Lighthouse measures that first second or first few seconds after you visit a site at position 0/0. It doesn't care about how much bloat comes after you scroll. It discourages you to pre-load resources (including JS and CSS) which you don't _immediately_ need for that first hit.
It is really about content and marketing websites with low interaction. You can absolutely make good interactive applications that also get a high Lighthouse score, but the overlap is not necessarily always feasible or the best tradeoff to make.
httpsterio|3 years ago