App Quality Dashboard

IndianRailway IRCTC

3.4 / 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 15.22 Sec
  • Launch time: Icon 0.90 Sec
  • Application size: Icon 6.76 MB
  • Last tested on : 25/03/2017
  • Build ID
    :   v3.6.0
  • Chhi Score
    :   3.4
  • Change Rate
    :   +3.03 %

Insights (30)

What to fix?

App launch time went up by 20.45% initlizate network calls after few seconds of loading the resources. View details
5 Risk(s) are due to Threads in CPU 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.
Build v3.5.8 did better in Network . Spikes in Network contributed to score drop by 17.24%
1 Risk(s) are due to App Dalvik in Memory exceeding the threshold. See how to optimize memory and remove 1 High Risk(s).
1 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
Fixing CPU risks could drastically improve Chhi Score. There are 5 CPU risks.
The app has a high performance risk for the phone manufacturer(s) Panasonic, Asus, Lenovo. Check coverage report for more details.
5 tests need immediate attention. View performance graph.
The app's CPU score has improved by 4.35% compared to build v3.5.8! Good job!
Utilization of CPU is close to the threshold.
1 Risk(s) are due to App Dalvik in Memory exceeding the threshold.
Consider re-merging the code from build v3.5.8, Network score was 2.9
191.12 MB of App Dalvik utilized by activity com.indianrail.thinkapps.irctc.IRCTCHomeActivity. View details
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.
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Caching: Use LruCache for data caching to optimize memory usage
Network utilization on Lenovo VIBE K4 Note exceeded 1024 KB, you might want to consider bringing it down
There is high probability of identifying risks running the apps with conditions
Optimize the app to render elements at 60 FPS for buttery smooth experience.
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.
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
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Total Network data consumed was 3452.34KB in Lenovo VIBE K4 Note , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
App makes 3452.34 KB of network requests. Moving this to a background thread will improve load speed. View details
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #449 in Travel & Local

444
445
446
447
448
back-to-top