webpagetest lets you simulate different "user seats" aka different loading experienced on devices and bandwidth
@theystolemynick

the speedinfex let's you know how long it takes to fill the page with the pixels. But it has limits. For instance ads might destroy it because they take foreeeeeeever to load @theystolemynick

Another measure is "How many seconds does the page need before you can click on something". Be careful with third part providers like share button services: they might do a lot of extra request in the background and make user wait for the first interaction @theystolemynick

You can use dev tools to measure CPU usage.
Another interesting metric you can find in the Lighthouse tool is "time to interactive" to guess when user can interact with the page. It's a mix between quietness of the CPU and number of requests @theystolemynick

"First input delay" is the delay between the first interaction of the user and the 1st JavaScript callback. A long delay means an "unresponsive" UI (aka laaaaaaag)

Follow

Why is this important? Because we have issues with the execution of JS, especially on mobile.
It means that knowing the hardware of your users is becoming more and more important @theystolemynick

How to deal with that? Well, know your users and check performance on real low-end devices.
You can use the chrome DevTools with Android devices.
There's also CPU throttling feature on chrome desktop but this is not enough you won't emulate the CPU :/
@theystolemynick

Sign in to participate in the conversation
mastodon.design

A Mastodon instance for Designers and Makers of all things — Developers, Engineers, Builders, Creators, Tinkerers & Misfits!Though you make design your life, all that inspires you is also welcome here.