App Quality Dashboard

ইংরেজীতে কথা বলার ১২৫ ফর্মুলা ~ English 125 Spoken Formula

1.6 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




Medium Risk






  • Install time: Icon 11.27 Sec
  • Launch time: Icon 3.06 Sec
  • Application size: Icon 3.13 MB
  • Last tested on : 24/03/2017
  • Build ID
    :   v1.2
  • Chhi Score
    :   1.6
  • Change Rate
    :   -5.88 %

What to fix?

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

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

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.

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

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

Build v1.1 did better in Network . Spikes in Network contributed to score drop by 28.57%

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

Build v1.1 did better in Memory . Spikes in Memory contributed to score drop by 8%

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

App size increased by 25.2% See how to optimize.

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

Consider re-merging the code from build v1.1, Network score was 2.8

Utilization of Network is close to the threshold.

The app's CPU score has improved by 7.69%

14 tests need immediate attention. View performance graph.

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

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

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.

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

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

318 apps having similar CPU load have low Chhi Scores

Your average App Dalvik usage surged by 11.02%, Your memory score is 2.3

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

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

Total Network data consumed was 1025.34KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

46.82 MB of App Dalvik utilized by activity studio.smssimpletemplate.CategoryActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1354 in Books & Reference