App Quality Dashboard

Motor-Talk

2.9 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Medium Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 18.33 Sec
  • Launch time: Icon 0.99 Sec
  • Application size: --- 14.35 MB
  • Last tested on : 04/04/2017
  • Build ID
    :   v1.4.8
  • Chhi Score
    :   2.9
  • Change Rate
    :   -3.33 %

Insights (30)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 7 CPU risks.
1 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
7 Risk(s) are due to Threads in CPU exceeding the threshold.
Build v1.4.7 did better in CPU . Spikes in CPU contributed to score drop by 3.13%
Build v1.4.7 did better in Memory . Spikes in Memory contributed to score drop by 3.57%
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.
Utilization of CPU is close to the threshold.
The app's memory score is 2.7 due to high memory utilization. Needs to be fixed as priority.
The app has a high performance risk for the phone manufacturer(s) YU, Samsung, Karbonn, Panasonic, Asus, Micromax, Lenovo. Check coverage report for more details.
Utilization of Network is close to the threshold.
11 tests need immediate attention. View performance graph.
The app's Network score has improved by 6.67% compared to build v1.4.7! Good job!
61.35 MB of App Dalvik utilized by activity net.motortalk.android.board.tutorial.TutorialActivity. View details
Caching: Use LruCache for data caching to optimize memory usage
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
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Your average App Dalvik usage surged by 12.47%, Your memory score is 2.7
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
Printing logs on callbacks would make debugging easy for tests run in our platform
Network utilization on Panasonic P55 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 & Optimize launch time using Flatbuffers for storage and rendering performance.
App makes 1361.53 KB of network requests. Moving this to a background thread will improve load speed. View details
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Total Network data consumed was 1361.53KB in Panasonic P55 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #483 in Social

478
479
480
481
482
back-to-top