App Quality Dashboard


2.8 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 39.91 Sec
  • Launch time: Icon 4.36 Sec
  • Application size: Icon 25.48 MB
  • Last tested on : 13/05/2017
  • Build ID
    :   v1.3.5
  • Chhi Score
    :   2.8
  • Change Rate
    :   -9.68 %

What to fix?

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

Build v1.3.3 did better in CPU . Spikes in CPU contributed to score drop by 12%

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.

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

Build v1.3.3 did better in Memory . Spikes in Memory contributed to score drop by 10.71%

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

The app took 4.36 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

23 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

The app's Network score has improved by 61.9% compared to build v1.3.3! Good job!

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

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

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

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

Total Network data consumed was 1050.26KB in Lenovo VIBE K4 Note , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

Caching: Use LruCache for data caching to optimize memory usage

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

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

51.34 MB of App Dalvik utilized by activity com.paywithoper.oper.HomeActivity. View details

Your average App Dalvik usage surged by 11.6%, Your memory score is 2.5

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

Network utilization on Lenovo VIBE K4 Note exceeded 1024 KB, you might want to consider bringing it down

App makes 1050.26 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

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

Well done, Network consumption has come down by 45.17 % compared to build v1.3.3

Screen Coverage

competition benchmark

This app is ranked #509 in Shopping