App Quality Dashboard


2.5 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 19.00 Sec
  • Launch time: Icon 1.31 Sec
  • Application size: Icon 7.32 MB
  • Last tested on : 16/03/2017
  • Build ID
    :   v2.1.4
  • Chhi Score
    :   2.5
  • Change Rate
    :   -28.57 %

What to fix?

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.

Build v2.1.2 did better in Memory . Spikes in Memory contributed to score drop by 32.35%

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

The app's CPU score has improved by 3.03% compared to build v2.1.2! Good job!

The app's memory score is 2.3 due to high memory utilization. Needs to be fixed as priority.

Build v2.1.2 did better in Network . Spikes in Network contributed to score drop by 26.53%

Consider re-merging the code from build v2.1.2, Memory score was 3.4

10 tests need immediate attention. View performance graph.

Utilization of Network is close to the threshold.

42.44 MB of App Dalvik utilized by activity com.rentomojo.activity.CartActivity. View details

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

Your average App Dalvik usage surged by 0.85%, Your memory score is 2.3

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

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!

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.

Caching: Use LruCache for data caching to optimize memory usage

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

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.

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

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

Screen Coverage

competition benchmark

This app is ranked #2250 in Lifestyle