App Quality Dashboard


3.1 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 18.59 Sec
  • Launch time: Icon 1.28 Sec
  • Application size: --- 7.48 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v4.2.1
  • Chhi Score
    :   3.1
  • Change Rate
    :   -3.13 %

What to fix?

Build v4.2.0 did better in Memory . Spikes in Memory contributed to score drop by 3.23%

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

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

Build v4.2.0 did better in CPU . Spikes in CPU contributed to score drop by 3.45%

Fixing CPU risks could drastically improve Chhi Score. There are 6 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.

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

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

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

2 Risk(s) are due to App Dalvik in Memory exceeding the threshold.

14 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Build v4.2.0 did better in Network . Spikes in Network contributed to score drop by 2.17%

Utilization of Memory is close to the threshold.

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

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

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

Your average App Dalvik usage surged by 15.43%, Your memory score is 3.0

147.99 MB of App Dalvik utilized by activity com.application.zomatomerchant.ZomatoActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #155 in Food & Drink