App Quality Dashboard

Le Berry

0.6 / 5

Chhi Score

This app is performing

Poor

Memory

High Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

High Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 21.67 Sec
  • Launch time: Icon 5.00 Sec
  • Application size: Icon 11.65 MB
  • Last tested on : 11/05/2017
  • Build ID
    :   v2.7.1
  • Chhi Score
    :   0.6
  • Change Rate
    :   -60 %

Insights (37)

What to fix?

9 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
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
Potential risk in Memory: Utilization has gone up by40.91% compared to build v2.6
Potential risk in Network: Utilization has gone up by58.62% compared to build v2.6
Fixing CPU risks could drastically improve Chhi Score. There are 27 CPU risks.
27 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 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
Fixing Network risks could drastically improve Chhi Score. There are 9 Network risks.
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.
Consider re-merging the code from build v2.6, Memory score was 2.2
2 Risk(s) are due to CPU Load in CPU exceeding the threshold.
The app has a high performance risk for the phone manufacturer(s) LYF, Lenovo, Karbonn, YU, Panasonic, Asus, Micromax, Motorola. Check coverage report for more details.
App size increased by 61.81% See how to optimize.
27 tests need immediate attention. View performance graph.
Consider re-merging the code from build v2.6, Network score was 2.9
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Caching: Use LruCache for data caching to optimize memory usage
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
435 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
Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down
Total Network data consumed was 2194.45KB 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
App makes 2194.45 KB of network requests. Moving this to a background thread will improve load speed. 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.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Your average App Dalvik usage surged by 7.7%, Your memory score is 1.3
Testability: Providing login / sign-up details could very well improve depth of bot clicks
70.35 MB of App Dalvik utilized by activity com.centrefrance.flux.activities.ActivityArticleList. View details
There is high probability of identifying risks running the apps with conditions
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
Unlock more fixes
competition benchmark

This app is ranked #1358 in News & Magazines

1353
1354
1355
1356
1357
back-to-top