App Quality Dashboard


0.9 / 5

Chhi Score

This app is performing


High Risk


Medium Risk




Medium Risk






  • Install time: Icon 18.61 Sec
  • Launch time: Icon 3.87 Sec
  • Application size: Icon 14.35 MB
  • Last tested on : 20/04/2017
  • Build ID
    :   v3.19.0
  • Chhi Score
    :   0.9
  • Change Rate
    :   +200 %

What to fix?

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

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

Your App Memory is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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.

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

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

The app's CPU score has improved by 4.76% compared to build v3.17.2! Good job!

26 tests need immediate attention. View performance graph.

Make sure your App's Dalvik isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

The app'sMemory score has improved by140%!

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

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

The app took 3.87 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

The app's memory score is 1.2 due to high memory utilization. Needs to be fixed as priority.

Build v3.17.2 did better in Network . Spikes in Network contributed to score drop by 2.44%

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

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

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

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

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

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

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

92.00 MB of App Dalvik utilized by activity 4795. View details

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

Screen Coverage

competition benchmark

This app is ranked #775 in Shopping