App Quality Dashboard


1.1 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 25.67 Sec
  • Launch time: Icon 2.86 Sec
  • Application size: Icon 13.86 MB
  • Last tested on : 09/05/2017
  • Build ID
    :   v4.0.7
  • Chhi Score
    :   1.1
  • Change Rate
    :   -71.79 %

What to fix?

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

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

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

Your App CPU 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.

Potential risk in CPU: Utilization has gone up by 50% compared to build v4.0.3

27 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build v4.0.3, CPU score was 2.0

Utilization of CPU is close to the threshold.

Build v4.0.3 did better in Network . Spikes in Network contributed to score drop by 6.38%

Build v4.0.3 did better in Memory . Spikes in Memory contributed to score drop by 7.69%

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

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

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

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

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

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

435 apps having similar CPU load have low Chhi Scores

Caching: Use LruCache for data caching to optimize memory usage

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

Your average App Dalvik usage surged by 11.64%, Your memory score is 3.6

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

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

51.02 MB of App Dalvik utilized by activity View details

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

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

Screen Coverage

competition benchmark

This app is ranked #1271 in News & Magazines