1.9 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 65.40 Sec
  • Launch time: Icon 1.87 Sec
  • Application size: Icon 51.60 MB
  • Last tested on : 03/05/2017
  • Build ID
    :   v17.17
  • Chhi Score
    :   1.9
  • Change Rate
    :   0%

What to fix?

11 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.

5 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 5 High Risk(s).

Build v17.16 did better in Memory . Spikes in Memory contributed to score drop by 3.33%

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

Potential risk in CPU: Utilization has gone up by 35.29% compared to build v17.16

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

11 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build v17.16, CPU score was 1.7

Your average App Dalvik usage surged by 11.02%, Your memory score is 2.9

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

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.

There is high probability of identifying risks running the apps with conditions

179 apps having similar CPU load have low Chhi Scores

Optimize the app to render elements at 60 FPS for buttery smooth experience.

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

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

57.56 MB of App Dalvik utilized by activity View details

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

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.

Caching: Use LruCache for data caching to optimize memory usage

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

The app's Network score has improved by 2.08% compared to build v17.16! Good job!

Well done, Network consumption has come down by 40.48 % compared to build v17.16

Screen coverage

competition benchmark

This app is ranked #973 in Travel & Local