App Quality Dashboard

Crochet Edging

1.6 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

Medium Risk

/5

Competition

#

 

Category

Rank

  • Install time: 7.40 Sec
  • Launch time: 6.47 Sec
  • Application size : 6.67 MB
  • Last tested on : 17/03/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   1.6
  • Change Rate
    :   0%

Insights (27)

What to fix?

13 Risk(s) are due to Threads in CPU 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.
Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage
12 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 12 High Risk(s).
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Fixing CPU risks could drastically improve Chhi Score. There are 13 CPU risks.
2 Risk(s) are due to App Total in Memory exceeding the threshold.
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Micromax, LYF, Lenovo, YU, Asus, Motorola, Karbonn, Panasonic. Check coverage report for more details.
The app took 6.47 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 Memory is close to the threshold.
18 tests need immediate attention. View performance graph.
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.
54.27 MB of App Dalvik utilized by activity ganz.crochet.edging.Dashboard_000. View details
Printing logs on callbacks would make debugging easy for tests run in our platform
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Caching: Use LruCache for data caching to optimize memory usage
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!
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
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
574 apps having similar CPU load have low Chhi Scores
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
There is high probability of identifying risks running the apps with conditions
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #2942 in Lifestyle

2937
2938
2939
2940
2941
back-to-top