App Quality Dashboard

Burgos

0.9 / 5

Chhi Score

This app is performing

Poor

Memory

High Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 6.33 Sec
  • Launch time: Icon 0.17 Sec
  • Application size: Icon 4.68 MB
  • Last tested on : 27/05/2017
  • Build ID
    :   v120
  • Chhi Score
    :   0.9
  • Change Rate
    :   +200 %

Insights (28)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 4 CPU risks.
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.14 did better in CPU . Spikes in CPU contributed to score drop by 11.54%
Your App Memory 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
5 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 5 High Risk(s).
4 Risk(s) are due to Threads in CPU exceeding the threshold.
4 Risk(s) are due to App Dalvik in Memory exceeding the threshold.
Build v4.14 did better in Network . Spikes in Network contributed to score drop by 2.17%
The app'sMemory score has improved by140%!
The app has a high performance risk for the phone manufacturer(s) LYF, Panasonic, Lava. Check coverage report for more details.
The app's memory score is 1.2 due to high memory utilization. Needs to be fixed as priority.
6 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
5 Risk(s) are due to App Total in Memory exceeding the threshold.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Testability: Providing login / sign-up details could very well improve depth of bot clicks
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
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Caching: Use LruCache for data caching to optimize memory usage
37.00 MB of App Dalvik utilized by activity 17859. View details
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
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #1128 in Travel & Local

1123
1124
1125
1126
1127
back-to-top