App Quality Dashboard

ChennaiSub

3.6 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

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 %

What to fix?

3 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

Fixing Network risks could drastically improve Chhi Score. There are 3 Network risks.

2 Risk(s) are due to Threads in CPU exceeding the threshold.

2 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 2 High Risk(s).

Fixing CPU risks could drastically improve Chhi Score. There are 2 CPU risks.

Utilization of CPU is close to the threshold.

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's Network score has improved by 14.29% 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.

3 tests need immediate attention. View performance graph.

Testability: Providing login / sign-up details could very well improve depth of bot clicks

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

42.33 MB of App Dalvik utilized by activity com.rail.chennai.RailTime. View details

Optimize the app to render elements at 60 FPS for buttery smooth experience.

Network utilization on Panasonic P55 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

Caching: Use LruCache for data caching to optimize memory usage

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

App makes 1084.53 KB of network requests. Moving this to a background thread will improve load speed. View details

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

There is high probability of identifying risks running the apps with conditions

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Well done, Network consumption has come down by 18.07 % compared to build v1.07

Screen coverage

competition benchmark

This app is ranked #346 in Travel & Local

341
342
343
344
345
back-to-top