App Quality Dashboard

Diamond Khazana

1.5 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

High Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 10.89 Sec
  • Launch time: Icon 2.81 Sec
  • Application size: Icon 3.74 MB
  • Last tested on : 10/04/2017
  • Build ID
    :   v1.0.3
  • Chhi Score
    :   1.5
  • Change Rate
    :   +50 %

Insights (27)

What to fix?

9 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
App launch time went up by 33.66% initlizate network calls after few seconds of loading the resources. View details
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.
Fixing Network risks could drastically improve Chhi Score. There are 9 Network risks.
The app's memory score is 2.2 due to high memory utilization. Needs to be fixed as priority.
The app's Memory score has improved by 69.23% compared to build v1.0.1! Good job!
The app's CPU score has improved by 3.85% compared to build v1.0.1! Good job!
9 tests need immediate attention. View performance graph.
The app has a high performance risk for the phone manufacturer(s) YU, Asus, LYF, Motorola, Karbonn, Lenovo, Lava. Check coverage report for more details.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Caching: Use LruCache for data caching to optimize memory usage
21.38 MB of App Dalvik utilized by activity com.ohoshop.diamondkhazana1469622499.MainActivity. View details
Printing logs on callbacks would make debugging easy for tests run in our platform
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
App makes 1915.50 KB of network requests. Moving this to a background thread will improve load speed. View details
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
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 Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
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
Total Network data consumed was 1915.50KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #706 in Shopping

701
702
703
704
705
back-to-top