App Quality Dashboard


1.8 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




Medium Risk






  • Install time: Icon 9.29 Sec
  • Launch time: Icon 5.12 Sec
  • Application size: Icon 3.47 MB
  • Last tested on : 04/03/2017
  • Build ID
    :   v4.0.0.0
  • Chhi Score
    :   1.8
  • Change Rate
    :   -5.26 %

What to fix?

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

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

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

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 v3.3.0.0 did better in Memory . Spikes in Memory contributed to score drop by 3.45%

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

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

Build v3.3.0.0 did better in Network . Spikes in Network contributed to score drop by 2.63%

Consider re-merging the code from build v3.3.0.0, CPU score was 1.8

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

18 tests need immediate attention. View performance graph.

The app took 5.12 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

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

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

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

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

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

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

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

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

347 apps having similar CPU load have low Chhi Scores

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

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

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

56.39 MB of App Dalvik utilized by activity com.jrummyapps.fontfix.activities.FontPreviewActivity. View details

Screen Coverage

competition benchmark

This app is ranked #1613 in Tools