App Quality Dashboard


2.2 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




High Risk






  • Install time: Icon 62.21 Sec
  • Launch time: Icon 1.15 Sec
  • Application size: Icon 77.00 MB
  • Last tested on : 20/04/2017
  • Build ID
    :   v6.11.1
  • Chhi Score
    :   2.2
  • Change Rate
    :   -4.35 %

What to fix?

Build v5.7.3 did better in CPU . Spikes in CPU contributed to score drop by 16%

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

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

Build v5.7.3 did better in Memory . Spikes in Memory contributed to score drop by 15.38%

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.

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

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

Potential risk in Network: Utilization has gone up by73.33% compared to build v5.7.3

20 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build v5.7.3, Network score was 4.5

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v5.7.3, Memory score was 3.9

App size increased by 1152.03% See how to optimize.

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

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.

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

Caching: Use LruCache for data caching to optimize memory usage

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

Network utilization on Zenfone 2 Laser 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

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

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

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.

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

Your average App Dalvik usage surged by 48.34%, Your memory score is 3.3

67.27 MB of App Dalvik utilized by activity View details

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

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

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

Screen Coverage

competition benchmark

This app is ranked #621 in Shopping