App Quality Dashboard

ChennaiSub

3.6 / 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 5.88 Sec
  • Launch time: Icon 3.96 Sec
  • Application size: Icon 1.18 MB
  • Last tested on : 27/03/2017
  • Build ID
    :   v1.08
  • Chhi Score
    :   3.6
  • Change Rate
    :   -2.7 %

Insights (29)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 2 CPU risks.
2 Risk(s) are due to Threads in CPU exceeding the threshold.
Fixing Network risks could drastically improve Chhi Score. There are 3 Network risks.
3 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
Utilization of CPU is close to the threshold.
The app's Network score has improved by 14.29% compared to build v1.07! Good job!
3 tests need immediate attention. View performance graph.
The app took 3.96 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
The app's CPU score has improved by 2.94% compared to build v1.07! Good job!
The app has a high performance risk for the phone manufacturer(s) Lenovo, Panasonic, Motorola. Check coverage report for more details.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
42.33 MB of App Dalvik utilized by activity com.rail.chennai.RailTime. View details
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
App makes 1084.53 KB of network requests. Moving this to a background thread will improve load speed. View details
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
There is high probability of identifying risks running the apps with conditions
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
Printing logs on callbacks would make debugging easy for tests run in our platform
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Total Network data consumed was 1084.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
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
Network utilization on Panasonic P55 exceeded 1024 KB, you might want to consider bringing it down
Well done, Network consumption has come down by 18.07 % compared to build v1.07
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #346 in Travel & Local

341
342
343
344
345
back-to-top