Time taken to run the test.
Can be helpful to measure Time To Interactive of your app, if the test is checking app start for instance.

Frame Per Second. Your app should display 60 Frames Per Second to give an impression of fluidity. This number should be close to 60, otherwise it will seem laggy.
See this video for more details

An app might run at 60FPS but might be using too much processing power, so it's important to check CPU usage.
Depending on the device, this value can go up to 100% x number of cores. For instance, a Samsung A10s has 4 cores, so the max value would be 400%.

High CPU usage by a single process can cause app unresponsiveness, even with low overall CPU usage. For instance, an overworked JS thread in a React Native app may lead to unresponsiveness despite maintaining 60 FPS.

If an app consumes a large amount of RAM (random-access memory), it can impact the overall performance of the device and drain the battery more quickly.
It’s worth noting that results might be higher than expected since we measure RSS and not PSS (See here for more details)