With Lazy Load - RT 8.2ms
40
Average Test Runtime
2500 ms
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.
Average FPS
46.6 FPS
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
Average CPU usage
102.3 %
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
2 s

Impacted threads:

- mqt_js for 1.5s

- UI Thread for 0.5s

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.
Average RAM usage
179.5 MB
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)
With Lazy Load - RT 22.6ms
40
Average Test Runtime
2631 ms
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.
Average FPS
46.5 FPS
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
Average CPU usage
103.3 %
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
2 s

Impacted threads:

- mqt_js for 1.5s

- UI Thread for 0.5s

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.
Average RAM usage
179.2 MB
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)
With Lazy Load - RT 246.4ms
40
Average Test Runtime
2764 ms
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.
Average FPS
45.9 FPS
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
Average CPU usage
104.5 %
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
2 s

Impacted threads:

- mqt_js for 1.5s

- UI Thread for 0.5s

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.
Average RAM usage
179.4 MB
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)
With Lazy Load - RT 2670.4ms
33
Average Test Runtime
2519 ms
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.
Average FPS
44.8 FPS
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
Average CPU usage
120.3 %
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
2 s

Impacted threads:

- mqt_js for 1.5s

- UI Thread for 0.5s

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.
Average RAM usage
175.4 MB
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)
Without lazy load - RT 8.2ms
34
Average Test Runtime
2410 ms
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.
Average FPS
44.5 FPS
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
Average CPU usage
116.9 %
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
2 s

Impacted threads:

- mqt_js for 1.5s

- UI Thread for 0.5s

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.
Average RAM usage
175.7 MB
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)
Without lazy load - RT 22.6ms
32
Average Test Runtime
2725 ms
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.
Average FPS
43.3 FPS
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
Average CPU usage
121.6 %
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
2 s

Impacted threads:

- mqt_js for 1.5s

- UI Thread for 0.5s

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.
Average RAM usage
175.6 MB
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)
Without lazy load - RT 246.4ms
30
Average Test Runtime
3671 ms
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.
Average FPS
44 FPS
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
Average CPU usage
130.8 %
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
2.7 s

Impacted threads:

- mqt_js for 2s

- UI Thread for 0.7s

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.
Average RAM usage
183.9 MB
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)
Without lazy load - RT 2670.4ms
38
Average Test Runtime
11634 ms
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.
Average FPS
51.9 FPS
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
Average CPU usage
129.5 %
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
6.6 s

Impacted threads:

- mqt_js for 6s

- UI Thread for 0.6s

- mqt_native_modu for 0.1s

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.
Average RAM usage
222.5 MB
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)
With Lazy Load - RT 8.2ms
With Lazy Load - RT 22.6ms
With Lazy Load - RT 246.4ms
With Lazy Load - RT 2670.4ms
Without lazy load - RT 8.2ms
Without lazy load - RT 22.6ms
Without lazy load - RT 246.4ms
Without lazy load - RT 2670.4ms
00240024004800480072007200960096001200012000Frame rate (FPS)6060545448484242363630302424181812126600
Download SVG
Download PNG
Download CSV
With Lazy Load - RT 8.2ms
With Lazy Load - RT 22.6ms
With Lazy Load - RT 246.4ms
With Lazy Load - RT 2670.4ms
Without lazy load - RT 8.2ms
Without lazy load - RT 22.6ms
Without lazy load - RT 246.4ms
Without lazy load - RT 2670.4ms
00240024004800480072007200960096001200012000Total CPU Usage (%)225.9225.9203.3203.3180.7180.7158.1158.1135.5135.5113.0113.090.490.467.867.845.245.222.622.60.00.0
Download SVG
Download PNG
Download CSV
(mqt_js) (With Lazy Load - RT 8.2ms)
(mqt_js) (With Lazy Load - RT 22.6ms)
(mqt_js) (With Lazy Load - RT 246.4ms)
(mqt_js) (With Lazy Load - RT 2670.4ms)
(mqt_js) (Without lazy load - RT 8.2ms)
(mqt_js) (Without lazy load - RT 22.6ms)
(mqt_js) (Without lazy load - RT 246.4ms)
(mqt_js) (Without lazy load - RT 2670.4ms)
00240024004800480072007200960096001200012000CPU Usage per thread (%)100.0100.090.090.080.080.070.070.060.060.050.050.040.040.030.030.020.020.010.010.00.00.0
Download SVG
Download PNG
Download CSV
Threads
With Lazy Load - RT 8.2ms
With Lazy Load - RT 22.6ms
With Lazy Load - RT 246.4ms
With Lazy Load - RT 2670.4ms
Without lazy load - RT 8.2ms
Without lazy load - RT 22.6ms
Without lazy load - RT 246.4ms
Without lazy load - RT 2670.4ms
00240024004800480072007200960096001200012000RAM Usage (MB)25725723123120620618018015415412912910310377775151262600
Download SVG
Download PNG
Download CSV
Showing average of 10 test iterations