App Quality Dashboard

Call Blocker

3.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 5.61 Sec
  • Launch time: --- 3.00 Sec
  • Application size: --- 1.32 MB
  • Last tested on : 08/03/2017
  • Build ID
    :   v1.0.78
  • Chhi Score
    :   3.3
  • Change Rate
    :   -5.71 %

What to fix?

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

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

Build 1.0.72 did better in CPU . Spikes in CPU contributed to score drop by 16%

Build 1.0.72 did better in Memory . Spikes in Memory contributed to score drop by 8.82%

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 1.0.72 did better in Network . Spikes in Network contributed to score drop by 4.35%

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

20 tests need immediate attention. View performance graph.

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

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

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

57.80 MB of App Dalvik utilized by activity com.androidrocker.callblocker.OptionsActivity. View details

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

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

Your average App Dalvik usage surged by 3.75%, Your memory score is 3.1

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

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

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

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

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.

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

Screen Coverage

competition benchmark

This app is ranked #729 in Business