App Quality Dashboard


0.7 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




High Risk






  • Install time: Icon 52.50 Sec
  • Launch time: Icon 0.78 Sec
  • Application size: Icon 21.48 MB
  • Last tested on : 12/06/2017
  • Build ID
    :   v8.7.1
  • Chhi Score
    :   0.7
  • Change Rate
    :   -78.79 %

What to fix?

Potential risk in Network: Utilization has gone up by75% compared to build v8.6.4

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

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

Build v8.6.4 did better in Memory . Spikes in Memory contributed to score drop by 41.94%

16 Risk(s) are due to Data Sent/Received in Network 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

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

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

Consider re-merging the code from build v8.6.4, Network score was 4.8

Consider re-merging the code from build v8.6.4, Memory score was 3.1

16 tests need immediate attention. View performance graph.

Consider re-merging the code from build v8.6.4, CPU score was 2.0

App size increased by 36.38% See how to optimize.

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

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

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

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

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

59.87 MB of App Dalvik utilized by activity View details

Total Network data consumed was 5705.50KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

153 apps having similar CPU load have low Chhi Scores

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

Your average App Dalvik usage surged by 38.82%, Your memory score is 1.8

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

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

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

Screen Coverage

competition benchmark

This app is ranked #414 in Sports