App Quality Dashboard


1.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 18.29 Sec
  • Launch time: Icon 1.67 Sec
  • Application size: Icon 9.62 MB
  • Last tested on : 22/03/2017
  • Build ID
    :   v5.2.1
  • Chhi Score
    :   1.9
  • Change Rate
    :   -47.22 %

What to fix?

Build 5.2.0 did better in Memory . Spikes in Memory contributed to score drop by 9.09%

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

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

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 53.21% initlizate network calls after few seconds of loading the resources. View details

Build 5.2.0 did better in CPU . Spikes in CPU contributed to score drop by 21.74%

Utilization of CPU is close to the threshold.

14 tests need immediate attention. View performance graph.

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

App size increased by 18.91% See how to optimize.

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

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

45.57 MB of App Dalvik utilized by activity com.onelouder.baconreader.DetailActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

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

Your average App Dalvik usage surged by 6.22%, Your memory score is 3.0

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

Well done, Network consumption has come down by 41.63 % compared to build 5.2.0

The app's Network score has improved by 27.59% compared to build 5.2.0! Good job!

Screen Coverage

competition benchmark

This app is ranked #967 in News & Magazines