App Quality Dashboard

NRZ.de

1.4 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

High Risk

/5

Competition

#

 

Category

Rank

  • Install time: 7.67 Sec
  • Launch time: 11.35 Sec
  • Application size : 2.04 MB
  • Last tested on : 06/05/2017
  • Build ID
    :   v1.4.3
  • Chhi Score
    :   1.4
  • Change Rate
    :   0%

Insights (30)

What to fix?

18 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 18 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 5 CPU risks.
Fixing Network risks could drastically improve Chhi Score. There are 16 Network risks.
16 Risk(s) are due to Data Sent/Received in Network 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.
5 Risk(s) are due to Threads in CPU exceeding the threshold.
Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.
The app has a high performance risk for the phone manufacturer(s) Karbonn, Samsung, Micromax, Motorola, YU, Panasonic, LYF, Lenovo. Check coverage report for more details.
The app took 11.35 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.
19 tests need immediate attention. View performance graph.
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Printing logs on callbacks would make debugging easy for tests run in our platform
Total Network data consumed was 7179.59KB 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
Network utilization on Samsung Duos Galaxy J7 exceeded 1024 KB, you might want to consider bringing it down
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.
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.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
App makes 7179.59 KB of network requests. Moving this to a background thread will improve load speed. View details
Caching: Use LruCache for data caching to optimize memory usage
38.96 MB of App Dalvik utilized by activity de.funkedigital.wrapper.live.MainActivity. View details
Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
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
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1187 in News & Magazines

1182
1183
1184
1185
1186
back-to-top