App Quality Dashboard

Japanese Tattoos

1.7 / 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: 5.19 Sec
  • Launch time: 0.53 Sec
  • Application size : 2.22 MB
  • Last tested on : 08/04/2017
  • Build ID
    :   v1.0
  • Chhi Score
    :   1.7
  • Change Rate
    :   0%

Insights (30)

What to fix?

Fixing Network risks could drastically improve Chhi Score. There are 12 Network risks.
Fixing CPU risks could drastically improve Chhi Score. There are 14 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.
12 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
11 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 11 High Risk(s).
14 Risk(s) are due to Threads in CPU exceeding the threshold.
Utilization of CPU is close to the threshold.
Utilization of Memory is close to the threshold.
Utilization of Network is close to the threshold.
2 Risk(s) are due to App Total in Memory exceeding the threshold.
16 tests need immediate attention. View performance graph.
The app has a high performance risk for the phone manufacturer(s) Panasonic, Lenovo, LYF, Motorola, Karbonn, YU, Lava, Asus. Check coverage report for more details.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
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!
Total Network data consumed was 2394.53KB 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 Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
45.06 MB of App Dalvik utilized by activity com.google.android.gms.ads.AdActivity. View details
App makes 2394.53 KB of network requests. Moving this to a background thread will improve load speed. View details
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
Printing logs on callbacks would make debugging easy for tests run in our platform
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Caching: Use LruCache for data caching to optimize memory usage
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down
There is high probability of identifying risks running the apps with conditions
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #2893 in Lifestyle

2888
2889
2890
2891
2892
back-to-top