App Quality Dashboard

Lovely Girly pictures

2.5 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 16.78 Sec
  • Launch time: Icon 17.68 Sec
  • Application size: Icon 7.78 MB
  • Last tested on : 03/05/2017
  • Build ID
    :   v2.4
  • Chhi Score
    :   2.5
  • Change Rate
    :   -35.9 %

What to fix?

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

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

Build v2.2 did better in CPU . Spikes in CPU contributed to score drop by 17.86%

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.

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

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

Build v2.2 did better in Memory . Spikes in Memory contributed to score drop by 46.34%

Consider re-merging the code from build v2.2, Memory score was 4.1

Consider re-merging the code from build v2.2, CPU score was 2.8

Utilization of CPU is close to the threshold.

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

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

App size increased by 82.63% See how to optimize.

25 tests need immediate attention. View performance graph.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

106.74 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

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

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

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

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

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

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

Your average App Dalvik usage surged by 51.91%, Your memory score is 2.2

Well done, Network consumption has come down by 39.02 % compared to build v2.2

The app's Network score has improved by 7.32% compared to build v2.2! Good job!

Screen Coverage

competition benchmark

This app is ranked #671 in Photography