These are complex interactions! Tools like Lighthouse provide _visibility_ to what was previously invisible. But they are not talismans. Saying "X gets 100 on LH" is specifically meaningful, but only when quantified (which hardware? which test environment? where in the network?)
-
-
Ah, so LH is really just a small piece of the puzzle. You could run it locally and everything looks great. But WPT shows you what it's like to load the app on a real phone + network. That's very interesting.
-
Exactly. LH is trying it's level best when run via devtools to emulate things without being super invasive; we could do a better job of network conditioning if we actually installed a driver and slowed things to a crawl while testing, e.g.
- 2 more replies
New conversation -
-
-
But the difference between the LH reports from http://web.dev and http://webpagetest.org/easy should give you a sense for how important it is to be running your tests on the real HW you're trying to optimize around: …https://lighthouse-dot-webdotdevsite.appspot.com/lh/html?url=https://open.fda.gov/ … vs. https://www.webpagetest.org/lighthouse.php?test=190829_F7_a00e889c76d1c198ec401361ec901904&run=3 …pic.twitter.com/zS364KZyJo
-
A 25 point difference (out of 100). If you were a decision maker, and your team told you "we score 85!" and then I show up in a meeting with you and say "wow, 60, you've failed pretty badly"...that would be an unwelcome surprise. Hence the value of real-hw testing = )
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.