App Quality Dashboard


3.1 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 16.57 Sec
  • Launch time: Icon 0.78 Sec
  • Application size: Icon 4.98 MB
  • Last tested on : 28/02/2017
  • Build ID
    :   v1.4
  • Chhi Score
    :   3.1
  • Change Rate
    :   -8.82 %

What to fix?

Build 1.3 did better in CPU . Spikes in CPU contributed to score drop by 33.33%

Build 1.3 did better in Network . Spikes in Network contributed to score drop by 44%

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

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.

Build 1.3 did better in Memory . Spikes in Memory contributed to score drop by 17.65%

Utilization of CPU is close to the threshold.

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

14 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build 1.3, CPU score was 3.3

Consider re-merging the code from build 1.3, Memory score was 3.4

Your average App Dalvik usage surged by 17.49%, Your memory score is 2.8

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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!

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

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

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

57.65 MB of App Dalvik utilized by activity com.herman.suntube.gui.activities.PreferencesActivity. View details

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

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

Screen Coverage

competition benchmark

This app is ranked #30 in Others