App Quality Dashboard


2.5 / 5

Chhi Score

This app is performing




High Risk




Medium Risk






  • Install time: Icon 13.82 Sec
  • Launch time: Icon 2.22 Sec
  • Application size: --- 9.25 MB
  • Last tested on : 22/02/2017
  • Build ID
    :   1.7
  • Chhi Score
    :   2.5
  • Change Rate
    :   +8.7 %

What to fix?

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

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

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

Potential risk in CPU: Utilization has gone up by 5.88% compared to build 1.6

11 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

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.

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

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

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

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

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!

435 apps having similar CPU load have low Chhi Scores

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

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

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

60.02 MB of App Dalvik utilized by activity com.divum.ibn.RefinedHomeActivity. View details

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

The app's Memory score has improved by 10.53% compared to build 1.6! Good job!

Well done, Network consumption has come down by 16.18 % compared to build 1.6

The app's Network score has improved by 8.57% compared to build 1.6! Good job!

Screen Coverage

competition benchmark

This app is ranked #613 in News & Magazines