App Quality Dashboard

ES Task Manager

3.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 11.64 Sec
  • Launch time: Icon 1.12 Sec
  • Application size: Icon 3.20 MB
  • Last tested on : 05/05/2017
  • Build ID
    :   v2.0.6.1
  • Chhi Score
    :   3.3
  • Change Rate
    :   -8.33 %

What to fix?

Build v2.0.6 did better in CPU . Spikes in CPU contributed to score drop by 23.53%

Build v2.0.6 did better in Memory . Spikes in Memory contributed to score drop by 8.57%

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

Utilization of CPU is close to the threshold.

App size increased by 160.16% See how to optimize.

7 tests need immediate attention. View performance graph.

Consider re-merging the code from build v2.0.6, CPU score was 3.4

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

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

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

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

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

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

42.36 MB of App Dalvik utilized by activity View details

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

Your average App Dalvik usage surged by 5.59%, Your memory score is 3.2

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

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

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

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

The app's Network score has improved by 2.04% compared to build v2.0.6! Good job!

Well done, Network consumption has come down by 19.41 % compared to build v2.0.6

Screen Coverage

competition benchmark

This app is ranked #740 in Business