App Quality Dashboard


1.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




High Risk






  • Install time: Icon 11.50 Sec
  • Launch time: Icon 2.10 Sec
  • Application size: Icon 6.88 MB
  • Last tested on : 05/05/2017
  • Build ID
    :   v3.4.2
  • Chhi Score
    :   1.9
  • Change Rate
    :   -9.52 %

What to fix?

Fixing Network risks could drastically improve Chhi Score. There are 5 Network 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.

Potential risk in Network: Utilization has gone up by5.88% compared to build v3.3.4

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

Build v3.3.4 did better in Memory . Spikes in Memory contributed to score drop by 11.43%

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

The app's CPU score has improved by 6.9% compared to build v3.3.4! Good job!

Utilization of CPU is close to the threshold.

App size increased by 19.44% See how to optimize.

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

10 tests need immediate attention. View performance graph.

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

Your average App Dalvik usage surged by 0.67%, Your memory score is 3.1

53.48 MB of App Dalvik utilized by activity com.subsplash.thechurchapp.MainActivity. View details

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

Screen Coverage

competition benchmark

This app is ranked #1878 in Education