App Quality Dashboard

CM Security

  • Install time: Icon 36.07 Sec
  • Launch time: Icon 2.25 Sec
  • Application size: Icon 19.41 MB
  • Last tested on : 03/05/2017

TEST COVERAGE INDEX  

  • Build ID
    :   v3.3.4
  • CHHI Score
    :   0.6
  • Change Rate
    :   -14.29 %

0.6 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

Category

Rank

Notify icon

Get app performance trends

What to fix

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

Your App Memory 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

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

Potential risk in Memory: Utilization has gone up by19.05% compared to build v3.3.3

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.

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

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

13 tests need immediate attention. View performance graph.

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

Build v3.3.3 did better in Network . Spikes in Network contributed to score drop by 16.33%

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

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

Network utilization on Panasonic P55 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

Your average App Dalvik usage surged by 34%, Your memory score is 1.7

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

346 apps having similar CPU load have low Chhi Scores

33.48 MB of App Dalvik utilized by activity ks.cm.antivirus.scan.ScanMainActivity. View details

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

Test Flows Panasonic P55 LYF-WATER Micromax Canvas AQ4502 Lenovo VIBE K4 Note Samsung Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Risk

  • Success

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #1885 in Tools

1880
1881
1882
1883
1884
back-to-top