App Quality Dashboard

CM Browser

1.2 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 18.56 Sec
  • Launch time: Icon 9.53 Sec
  • Application size: Icon 5.57 MB
  • Last tested on : 03/05/2017
  • Build ID
    :   v5.20.76
  • Chhi Score
    :   1.2
  • Change Rate
    :   -69.23 %

What to fix?

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.

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

Potential risk in CPU: Utilization has gone up by 47.37% compared to build v5.20.75

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

2 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 2 High Risk(s).

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

Build v5.20.75 did better in Memory . Spikes in Memory contributed to score drop by 11.63%

Consider re-merging the code from build v5.20.75, CPU score was 1.9

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

Utilization of Memory is close to the threshold.

26 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

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

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

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

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

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

Your average App Dalvik usage surged by 36.69%, Your memory score is 3.8

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

98 apps having similar CPU load have low Chhi Scores

Caching: Use LruCache for data caching to optimize memory usage

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

51.93 MB of App Dalvik utilized by activity com.ijinshan.browser.screen.BrowserActivity. View details

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

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

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

Well done, Network consumption has come down by 39.45 % compared to build v5.20.75

The app's Network score has improved by 4.35% compared to build v5.20.75! Good job!

Screen coverage

competition benchmark

This app is ranked #581 in Communication