@slightlylate what's your go to setup for testing slow connections and devices?
-
-
Replying to @NickColley
Best and easiest testbed today is
@patmeenan's outstanding https://www.webpagetest.org/easy It's real devices attached to high-quality link conditioning. Gold standard.1 reply 0 retweets 3 likes -
For private/internal testing, I carry physical devices; primarily Moto G4's and Android Go devices. The Alcatel 1X is available on Amazon: https://www.amazon.com/Alcatel-1X-Unlocked-Smartphone-T-Mobile-x/dp/B07CB6SHKS … Network emulation in these situations is trickier.
1 reply 0 retweets 1 like -
Chrome DevTool's network throttling is a bit of a fudge, and the slower the link you're trying to emulate, the harder it is to have confidence.
2 replies 0 retweets 1 like -
WPT uses dummynet(4). DevTools uses IPC throttling between the browser and renderer processes, which is less accurate and can't emulate everything (e.g. packet loss).
1 reply 0 retweets 0 likes -
MacOS has a dummynet configuration app in XCode (called "Network Link Conditioner"): https://nshipster.com/network-link-conditioner/ … Pat Meenan also made a Windows equivalent called winShaper:https://calendar.perfplanet.com/2016/testing-with-realistic-networking-conditions/ …
1 reply 0 retweets 1 like
Googler's have access to WIFI SSIDs that are pre-configured with aggressive link conditioning, so for us testing public sites, we can just put a slow device on one of those slow networks. Otherwise, best case scenario is WPT.
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.