The problem is that nobody really does "mobile-first". ~everybody designs/builds on desktop, and few know about or use chrome://inspect as they core of their workflow: https://developers.google.com/web/tools/chrome-devtools/remote-debugging …https://twitter.com/adactio/status/1180144204871327744 …
-
-
Ground truth is a $100-200 Android, attached over USB via chrome://inspect, or automated via
@patmeenan's genius http://webpagetest.org/easy Anything else is just lying to yourself.Show this thread -
Free idea: there should be a service like BrowserStack that builds a DevTools extension that lets you subscribe to see/experience your dev environment on real hardware by default. Opening DevTools should never reflect your local device capabilities by default.
Show this thread
End of conversation
New conversation -
-
-
Be very cool if DevTools showed warnings in the console output on poor performing pages.
-
Lighthouse is there, but no one seems to care...? I’m guessing this is common: “It cannot be that bad, something must be wrong with Lighthouse, so I keep my code”
End of conversation
New conversation -
-
-
It's a small thing, but it always bothered me that the Network panel always hides the uncompressed size (unless you go out of your way to reveal it). Half of our tools report compressed sizes, and the other half uncompressed ones. Makes it hard to talk about perf budgets.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Do you anyone who might be able to improve that?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.