App Quality Dashboard


3.5 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk


Medium Risk






  • Install time: Icon 55.86 Sec
  • Launch time: Icon 3.65 Sec
  • Application size: Icon 60.59 MB
  • Last tested on : 11/05/2017
  • Build ID
    :   v5.29.7 Domain 333
  • Chhi Score
    :   3.5
  • Change Rate
    :   +105.88 %

What to fix?

Build v5.26.02 did better in CPU . Spikes in CPU contributed to score drop by 30.3%

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

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

Must fix: App crashed because of FATAL EXCEPTION: AsyncTask #9 Process: com.cedarfair.valleyfair PID: 12486 java.lang.RuntimeExc... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

1 Risk(s) are due to Data Sent/Received in Network 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.

1 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 1 High Risk(s).

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

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

Utilization of Memory is close to the threshold.

Consider re-merging the code from build v5.26.02, CPU score was 3.3

The app's Network score has improved by 191.67% compared to build v5.26.02! Good job!

9 tests need immediate attention. View performance graph.

LYF-WATER health improved from High risk to Medium risk eliminating CRASH

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

App size increased by 271.72% See how to optimize.

Utilization of CPU is close to the threshold.

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

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

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

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

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

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

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

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

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

81.57 MB of App Dalvik utilized by activity com.avai.amp.lib.MainActivity. View details

The app has crashed on few device(s)! View details

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

Total Network data consumed was 1084.86KB in Lenovo VIBE K4 Note , 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

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

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

The app's Memory score has improved by 19.35% compared to build v5.26.02! Good job!

Well done, Network consumption has come down by 93.01 % compared to build v5.26.02

Screen coverage

competition benchmark

This app is ranked #388 in Travel & Local