App Quality Dashboard

ES File Explorer

2.0 / 5

Chhi Score

This app is performing


Medium Risk


High Risk


Medium  Risk








  • Install time: Icon 29.87 Sec
  • Launch time: Icon 4.27 Sec
  • Application size: Icon 15.11 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v4.
  • Chhi Score
    :   2.0
  • Change Rate
    :   +81.82 %

What to fix?

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

Must fix: App crashed because of 941): java.lang.RuntimeException: here 941): at Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

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

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

Utilization of CPU is close to the threshold.

24 tests need immediate attention. View performance graph.

Karbonn Titanium Machfive, Panasonic P55, YU Yuphoria has moved from Good to Medium risk due to RISK . View details

21 Risk(s) are due to CPU Load in CPU exceeding the threshold.

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

The app's Memory score has improved by 2.94% compared to build v4.1.6.2! Good job!

High CPU utilization on Panasonic P55, Threads & CPU load is above the average utilization across your competitors

App size increased by 35.15% See how to optimize.

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

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

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

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

The app has crashed on few device(s)! View details

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

36.84 MB of App Dalvik utilized by activity View details

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

Caching: Use LruCache for data caching to optimize memory usage

144 apps having similar CPU load have low Chhi Scores

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

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

The app's Network score has improved by 11.63% compared to build v4.1.6.2! Good job!

Well done, Network consumption has come down by 63.82 % compared to build v4.1.6.2

Screen Coverage

competition benchmark

This app is ranked #927 in Productivity