App Quality Dashboard

Résultats Foot

2.1 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 60.38 Sec
  • Launch time: Icon 12.74 Sec
  • Application size: Icon 20.81 MB
  • Last tested on : 23/03/2017
  • Build ID
    :   v4.0.1
  • Chhi Score
    :   2.1
  • Change Rate
    :   +75 %

What to fix?

Build v4.0.0 did better in Memory . Spikes in Memory contributed to score drop by 5.56%

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

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

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

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

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

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.

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

The app's CPU score has improved by 40%

23 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

61.43 MB of App Dalvik utilized by activity com.perform.livescores.views.activities.MainActivity. View details

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

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

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

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

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

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

Your average App Dalvik usage surged by 14.44%, Your memory score is 3.4

153 apps having similar CPU load have low Chhi Scores

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

The app's Network score has improved by 53.57% compared to build v4.0.0! Good job!

Well done, Network consumption has come down by 70.42 % compared to build v4.0.0

Screen coverage

competition benchmark

This app is ranked #298 in Sports