App Quality Dashboard


2.4 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk








  • Install time: Icon 37.71 Sec
  • Launch time: Icon 1.62 Sec
  • Application size: Icon 56.29 MB
  • Last tested on : 27/03/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   2.4
  • Change Rate
    :   +50 %

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 13 CPU risks.

Test more often so that you don't break the CPU handling further in your next builds. CPU Score is in danger zone. Heavy battery consumption expected.

Must fix: App crashed because of 3960): FATAL EXCEPTION: main 3960): Process: com.nibbleapps.fitmencook PID: 3960 3960): Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

8 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 8 High Risk(s).

App launch time went up by 10.96% initlizate network calls after few seconds of loading the resources. View details

13 Risk(s) are due to Threads in CPU exceeding the threshold.

The app's Memory score has improved by 18.18% compared to build v1.0! Good job!

Utilization of Memory is close to the threshold.

Utilization of CPU is close to the threshold.

15 tests need immediate attention. View performance graph.

The app has a high performance risk for the phone manufacturer(s) Lenovo, Karbonn, Lava, Motorola, YU, Micromax, Panasonic. Check coverage report for more details.

The app's CPU score has improved by 64.29% compared to build v1.0! Good job!

Motorola Moto E (2nd gen), Lava Iris X8, Karbonn Titanium Machfive has moved from Good to Medium risk due to RISK . View details

1 Risk(s) are due to App Total in Memory exceeding the threshold.

60.93 MB of App Dalvik utilized by activity View details

Caching: Use LruCache for data caching to optimize memory usage

Printing logs on callbacks would make debugging easy for tests run in our platform

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

Testability: Providing login / sign-up details could very well improve depth of bot clicks

3 Tests crashed out of 21 Tests. Check where the app crashed. View details

Optimize the app to render elements at 60 FPS for buttery smooth experience.

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

There is high probability of identifying risks running the apps with conditions

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

The app has crashed on few device(s)! View details

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

The app's Network score has improved by 291.67% compared to build v1.0! Good job!

Well done, Network consumption has come down by 95.37 % compared to build v1.0

Screen coverage

competition benchmark

This app is ranked #261 in Food & Drink