1.9 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 44.11 Sec
  • Launch time: Icon 1.60 Sec
  • Application size: --- 40.99 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v11.18.1.15578
  • Chhi Score
    :   1.9
  • Change Rate
    :   -47.22 %

What to fix?

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

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

Build v11.13.1.14801 did better in Memory . Spikes in Memory contributed to score drop by 8.82%

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

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

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 31.58% compared to build v11.13.1.14801

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

Consider re-merging the code from build v11.13.1.14801, CPU score was 1.9

9 tests need immediate attention. View performance graph.

45.06 MB of App Dalvik utilized by activity View details

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

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

98 apps having similar CPU load have low Chhi Scores

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Your average App Dalvik usage surged by 37.87%, Your memory score is 3.1

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

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

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

Screen Coverage

competition benchmark

This app is ranked #521 in Communication