App Quality Dashboard

Power Clean

1.2 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 12.00 Sec
  • Launch time: Icon 1.63 Sec
  • Application size: Icon 4.57 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v2.9.4.1
  • Chhi Score
    :   1.2
  • Change Rate
    :   -70 %

Insights (28)

What to fix?

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
Fixing CPU risks could drastically improve Chhi Score. There are 3 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.
3 Risk(s) are due to Threads in CPU exceeding the threshold.
Potential risk in CPU: Utilization has gone up by 56.52% compared to build v2.9.3.6
Build v2.9.3.6 did better in Memory . Spikes in Memory contributed to score drop by 2.56%
3 Risk(s) are due to CPU Load in CPU exceeding the threshold.
Build v2.9.3.6 did better in Network . Spikes in Network contributed to score drop by 8.33%
App size increased by 29.83% See how to optimize.
Consider re-merging the code from build v2.9.3.6, CPU score was 2.3
The app has a high performance risk for the phone manufacturer(s) Lenovo. Check coverage report for more details.
3 tests need immediate attention. View performance graph.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
347 apps having similar CPU load have low Chhi Scores
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Caching: Use LruCache for data caching to optimize memory usage
There is high probability of identifying risks running the apps with conditions
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Your average App Dalvik usage surged by 34.81%, Your memory score is 3.8
Printing logs on callbacks would make debugging easy for tests run in our platform
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
46.80 MB of App Dalvik utilized by activity com.lionmobi.powerclean.activity.MainActivity. View details
Unlock more fixes
competition benchmark

This app is ranked #1794 in Tools

1789
1790
1791
1792
1793
back-to-top