App Quality Dashboard


0.9 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




High Risk






  • Install time: Icon 21.29 Sec
  • Launch time: Icon 2.69 Sec
  • Application size: Icon 14.76 MB
  • Last tested on : 25/03/2017
  • Build ID
    :   v3.38
  • Chhi Score
    :   0.9
  • Change Rate
    :   -76.92 %

What to fix?

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

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

Potential risk in CPU: Utilization has gone up by 62.96% compared to build v3.36

Potential risk in Network: Utilization has gone up by57.14% compared to build v3.36

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

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

Build v3.36 did better in Memory . Spikes in Memory contributed to score drop by 35.14%

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

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

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

21 tests need immediate attention. View performance graph.

Consider re-merging the code from build v3.36, CPU score was 2.7

Consider re-merging the code from build v3.36, Memory score was 3.7

Consider re-merging the code from build v3.36, Network score was 2.8

Utilization of CPU is close to the threshold.

Total Network data consumed was 5566.97KB 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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Network utilization on Motorola Moto E (2nd gen) 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

140 apps having similar CPU load have low Chhi Scores

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

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.

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

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

Your average App Dalvik usage surged by 24.11%, Your memory score is 2.4

61.65 MB of App Dalvik utilized by activity com.bittorrent.client.onboarding.OnboardingSearchPagerActivity. View details

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!

Network utilization on Lava Iris X8 exceeded 1024 KB, you might want to consider bringing it down

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.

Screen Coverage

competition benchmark

This app is ranked #572 in Video Players & Editors