App Quality Dashboard


3.8 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 24.57 Sec
  • Launch time: Icon 1.44 Sec
  • Application size: Icon 10.88 MB
  • Last tested on : 25/04/2017
  • Build ID
    :   v6.3.1
  • Chhi Score
    :   3.8
  • Change Rate
    :   +72.73 %

What to fix?

Build v6.3.0 did better in CPU . Spikes in CPU contributed to score drop by 29.63%

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

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

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.

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

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

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

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

Build v6.3.0 did better in Memory . Spikes in Memory contributed to score drop by 2.86%

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, Lenovo, LYF, Panasonic, YU. Check coverage report for more details.

21 tests need immediate attention. View performance graph.

Utilization of Network is close to the threshold.

The app's Network score has improved by 66.67% compared to build v6.3.0! Good job!

Consider re-merging the code from build v6.3.0, CPU score was 2.7

82.83 MB of App Dalvik utilized by activity com.snapdeal.ui.material.activity.MaterialMainActivity. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

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

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

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

Network utilization on Panasonic P55 exceeded 1024 KB, you might want to consider bringing it down

Total Network data consumed was 1100.39KB in Panasonic P55 , 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 1100.39 KB of network requests. Moving this to a background thread will improve load speed. View details

Well done, Network consumption has come down by 26.82 % compared to build v6.3.0

Screen coverage

competition benchmark

This app is ranked #263 in Shopping