App Quality Dashboard

Calorie Counter

  • Install time: 16.20 Sec
  • Launch time: 6.16 Sec
  • Application size : 8.56 MB
  • Last tested on : 13/06/2017
  • Build ID
    :   v2.24
  • CHHI Score
    :   2.9
  • Change Rate
    :   0%

2.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

Category

Rank

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.

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

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

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

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

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

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

24 tests need immediate attention. View performance graph.

Utilization of Network is close to the threshold.

Utilization of CPU is close to the threshold.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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.

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

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

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

42.00 MB of App Dalvik utilized by activity com.google.android.gms.ads.AdActivity. View details

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

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

Network utilization on Lenovo A6000 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

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

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

Screen coverage

Test Flows YU Yuphoria Panasonic P55 LYF-WATER Karbonn Titanium Machfive Zenfone 2 Laser Micromax Canvas AQ4502 Lenovo VIBE K4 Note Lenovo A6000 Samsung Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Success

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #749 in Health & Fitness

744
745
746
747
748
back-to-top