App Quality Dashboard


1.6 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




High Risk






  • Install time: Icon 27.31 Sec
  • Launch time: Icon 2.71 Sec
  • Application size: Icon 14.13 MB
  • Last tested on : 25/03/2017
  • Build ID
    :   v3.36
  • Chhi Score
    :   1.6
  • Change Rate
    :   -60.98 %

What to fix?

Potential risk in Network: Utilization has gone up by76% compared to build 3.34

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.

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

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

Build 3.34 did better in Memory . Spikes in Memory contributed to score drop by 41.46%

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

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

Build 3.34 did better in CPU . Spikes in CPU contributed to score drop by 48.78%

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

10 tests need immediate attention. View performance graph.

Consider re-merging the code from build 3.34, CPU score was 4.1

App size increased by 12.14% See how to optimize.

Consider re-merging the code from build 3.34, Network score was 5.0

Consider re-merging the code from build 3.34, Memory score was 4.1

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

55.03 MB of App Dalvik utilized by activity com.bittorrent.client.Main. View details

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

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

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

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.

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

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

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

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!

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

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

Screen Coverage

competition benchmark

This app is ranked #511 in Video Players & Editors