App Quality Dashboard

Priceline

4.0 / 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 31.55 Sec
  • Launch time: Icon 1.09 Sec
  • Application size: --- 17.92 MB
  • Last tested on : 18/04/2017
  • Build ID
    :   v4.7.140
  • Chhi Score
    :   4.0
  • Change Rate
    :   0%

Insights (33)

What to fix?

Fixing Network risks could drastically improve Chhi Score. There are 6 Network 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.
6 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
16 Risk(s) are due to Threads in CPU exceeding the threshold.
5 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 5 High Risk(s).
Fixing CPU risks could drastically improve Chhi Score. There are 16 CPU risks.
Build v4.6.139 did better in CPU . Spikes in CPU contributed to score drop by 4.76%
Utilization of Memory is close to the threshold.
20 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
1 Risk(s) are due to CPU Load in CPU exceeding the threshold.
Build v4.6.139 did better in Memory . Spikes in Memory contributed to score drop by 2.7%
The app has a high performance risk for the phone manufacturer(s) Asus, LYF, Lenovo, Panasonic, Motorola, YU, Micromax. Check coverage report for more details.
The app's Network score has improved by 5% compared to build v4.6.139! Good job!
Optimize the app to render elements at 60 FPS for buttery smooth experience.
66.94 MB of App Dalvik utilized by activity com.priceline.android.negotiator.stay.commons.ui.activities.StaySearchActivity. View details
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Your average App Dalvik usage surged by 3.14%, Your memory score is 3.6
Printing logs on callbacks would make debugging easy for tests run in our platform
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.
Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
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.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Testability: Providing login / sign-up details could very well improve depth of bot clicks
There is high probability of identifying risks running the apps with conditions
Total Network data consumed was 1529.68KB 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
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
App makes 1529.68 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
Caching: Use LruCache for data caching to optimize memory usage
Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #197 in Travel & Local

192
193
194
195
196
back-to-top