App Quality Dashboard

Travelyaari

3.1 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 22.23 Sec
  • Launch time: Icon 2.56 Sec
  • Application size: Icon 6.05 MB
  • Last tested on : 07/04/2017
  • Build ID
    :   v2.0.0
  • Chhi Score
    :   3.1
  • Change Rate
    :   +14.81 %

Insights (28)

What to fix?

8 Risk(s) are due to Threads in CPU exceeding the threshold.
App launch time went up by 34.44% initlizate network calls after few seconds of loading the resources. View details
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.
9 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 9 High Risk(s).
Fixing CPU risks could drastically improve Chhi Score. There are 8 CPU risks.
App size increased by 34.15% See how to optimize.
12 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
The app's Memory score has improved by 20.83% compared to build v1.4.0! Good job!
Utilization of Memory is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Panasonic, Lenovo, Micromax, Karbonn, LYF, Asus, YU. Check coverage report for more details.
The app's CPU score has improved by 9.52% compared to build v1.4.0! Good job!
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
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
There is high probability of identifying risks running the apps with conditions
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
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
Caching: Use LruCache for data caching to optimize memory usage
56.27 MB of App Dalvik utilized by activity com.travelyaari.refund.RefundActivity. View details
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
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.
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
The app's Network score has improved by 7.32% compared to build v1.4.0! Good job!
Well done, Network consumption has come down by 29.98 % compared to build v1.4.0
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #572 in Travel & Local

567
568
569
570
571
back-to-top