App Quality Dashboard

Kurti Wallpaper

3.3 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 13.86 Sec
  • Launch time: Icon 5.00 Sec
  • Application size: Icon 16.22 MB
  • Last tested on : 02/05/2017
  • Build ID
    :   v1.3
  • Chhi Score
    :   3.3
  • Change Rate
    :   +3.12 %

Insights (27)

What to fix?

10 Risk(s) are due to Threads in CPU exceeding the threshold.
Build v1.2 did better in CPU . Spikes in CPU contributed to score drop by 7.69%
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.
App launch time went up by 12.77% initlizate network calls after few seconds of loading the resources. View details
Fixing CPU risks could drastically improve Chhi Score. There are 11 CPU risks.
The app has a high performance risk for the phone manufacturer(s) YU, Asus, LYF, Micromax, Motorola, Karbonn, Panasonic. Check coverage report for more details.
The app's Memory score has improved by 3.33% compared to build v1.2! Good job!
1 Risk(s) are due to CPU Load in CPU exceeding the threshold.
The app took 5.00 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
Utilization of CPU is close to the threshold.
14 tests need immediate attention. View performance graph.
26.19 MB of App Dalvik utilized by activity com.support.photo.SplashActivity. View details
Printing logs on callbacks would make debugging easy for tests run in our platform
There is high probability of identifying risks running the apps with conditions
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Testability: Providing login / sign-up details could very well improve depth of bot clicks
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.
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
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.
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!
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Caching: Use LruCache for data caching to optimize memory usage
The app's Network score has improved by 2.38% compared to build v1.2! Good job!
Well done, Network consumption has come down by 17.5 % compared to build v1.2
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1256 in Lifestyle

1251
1252
1253
1254
1255
back-to-top