App Quality Dashboard


3.8 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 26.77 Sec
  • Launch time: Icon 1.44 Sec
  • Application size: Icon 14.57 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v4.1.4
  • Chhi Score
    :   3.8
  • Change Rate
    :   +52 %

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.

Build v4.1.3 did better in CPU . Spikes in CPU contributed to score drop by 18.52%

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

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

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

Consider re-merging the code from build v4.1.3, CPU score was 2.7

Utilization of CPU is close to the threshold.

10 tests need immediate attention. View performance graph.

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

Build v4.1.3 did better in Memory . Spikes in Memory contributed to score drop by 9.76%

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

49.86 MB of App Dalvik utilized by activity com.dhgate.buyermob.activity.SplashActivity. View details

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

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

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

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

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

Your average App Dalvik usage surged by 26.04%, Your memory score is 3.7

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

Well done, Network consumption has come down by 98.19 % compared to build v4.1.3

Screen Coverage

competition benchmark

This app is ranked #254 in Shopping