App Quality Dashboard

trivago

1.3 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 21.67 Sec
  • Launch time: Icon 3.54 Sec
  • Application size: Icon 8.98 MB
  • Last tested on : 25/04/2017
  • Build ID
    :   v4.1.0
  • Chhi Score
    :   1.3
  • Change Rate
    :   -18.75 %

What to fix?

Your App Memory is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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

App launch time went up by 36.68% 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.

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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

Potential risk in Memory: Utilization has gone up by22.73% compared to build v4.0.0

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

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

The app has a high performance risk for the phone manufacturer(s) LYF, Samsung, Motorola. Check coverage report for more details.

3 tests need immediate attention. View performance graph.

Consider re-merging the code from build v4.0.0, Memory score was 2.2

The app's CPU score has improved by 16.67%

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

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.

179 apps having similar CPU load have low Chhi Scores

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

40.27 MB of App Dalvik utilized by activity com.trivago.activities.MainActivity. View details

Network utilization on Samsung Duos Galaxy J7 exceeded 1024 KB, you might want to consider bringing it down

Total Network data consumed was 2064.06KB 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

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!

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.

Printing logs on callbacks would make debugging easy for tests run in our platform

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

App makes 2064.06 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

Screen Coverage

competition benchmark

This app is ranked #1079 in Travel & Local

1074
1075
1076
1077
1078
back-to-top