App Quality Dashboard

Predict your future

3.9 / 5

Chhi Score

This app is performing




Medium Risk




Medium Risk






  • Install time: 15.00 Sec
  • Launch time: 1.34 Sec
  • Application size : 6.78 MB
  • Last tested on : 16/05/2017
  • Build ID
    :   v3.0
  • Chhi Score
    :   3.9
  • Change Rate
    :   0%

What to fix?

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.

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

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

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

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

Utilization of CPU is close to the threshold.

2 tests need immediate attention. View performance graph.

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

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

61.96 MB of App Dalvik utilized by activity View details

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

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Network utilization on LYF-WATER exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #288 in Books & Reference