App Quality Dashboard

Al-Quran (Free)

2.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 10.11 Sec
  • Launch time: Icon 0.70 Sec
  • Application size: Icon 5.10 MB
  • Last tested on : 15/05/2017
  • Build ID
    :   v3.0.9
  • Chhi Score
    :   2.3
  • Change Rate
    :   +91.67 %

What to fix?

Build v3.0.7 did better in Memory . Spikes in Memory contributed to score drop by 16.67%

Build v3.0.7 did better in CPU . Spikes in CPU contributed to score drop by 39.39%

App launch time went up by 19.64% initlizate network calls after few seconds of loading the resources. View details

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 5 CPU risks.

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

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

8 tests need immediate attention. View performance graph.

Consider re-merging the code from build v3.0.7, CPU score was 3.3

Utilization of CPU is close to the threshold.

46.28 MB of App Dalvik utilized by activity View details

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

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

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

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

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

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

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

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

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.

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

Your average App Dalvik usage surged by 50.78%, Your memory score is 2.0

Well done, Network consumption has come down by 64.57 % compared to build v3.0.7

The app's Network score has improved by 6.52% compared to build v3.0.7! Good job!

Screen Coverage

competition benchmark

This app is ranked #1077 in Books & Reference