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 (26)

What to fix?

App launch time went up by 34.44% initlizate network calls after few seconds of loading the resources. View details
Fixing CPU risks could drastically improve Chhi Score. There are 8 CPU risks.
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.
8 Risk(s) are due to Threads in CPU exceeding the threshold.
The app's Memory score has improved by 20.83% compared to build v1.4.0! Good job!
The app's CPU score has improved by 9.52% compared to build v1.4.0! Good job!
App size increased by 34.15% See how to optimize.
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) YU, Asus, Panasonic, Lenovo, LYF, Karbonn, Micromax. Check coverage report for more details.
12 tests need immediate attention. View performance graph.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
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.
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app 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.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
56.27 MB of App Dalvik utilized by activity com.travelyaari.refund.RefundActivity. View details
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Optimize the app to render elements at 60 FPS for buttery smooth experience.
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.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Caching: Use LruCache for data caching to optimize memory usage
Well done, Network consumption has come down by 29.98 % compared to build v1.4.0
The app's Network score has improved by 7.32% compared to build v1.4.0! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #572 in Travel & Local

567
568
569
570
571
back-to-top