App Quality Dashboard


2.4 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




High Risk






  • Install time: Icon 36.68 Sec
  • Launch time: Icon 1.80 Sec
  • Application size: Icon 15.43 MB
  • Last tested on : 13/05/2017
  • Build ID
    :   v1.13.11
  • Chhi Score
    :   2.4
  • Change Rate
    :   -38.46 %

What to fix?

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 56% compared to build v1.13.4

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

Potential risk in Network: Utilization has gone up by72.73% compared to build v1.13.4

Fixing Network risks could drastically improve Chhi Score. There are 18 Network risks.

18 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

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

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

Build v1.13.4 did better in Memory . Spikes in Memory contributed to score drop by 11.9%

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v1.13.4, Network score was 4.4

Consider re-merging the code from build v1.13.4, CPU score was 2.5

25 tests need immediate attention. View performance graph.

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

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

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

App makes 2392.30 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Your average App Dalvik usage surged by 52.14%, Your memory score is 3.7

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

200 apps having similar CPU load have low Chhi Scores

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

Total Network data consumed was 2392.30KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

128.61 MB of App Dalvik utilized by activity com.hkm.hbstore.MainActivity. View details

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

Screen Coverage

competition benchmark

This app is ranked #579 in Shopping