App Quality Dashboard

Web Browser

1.1 / 5

Chhi Score

This app is performing


High Risk


Medium Risk




High Risk






  • Install time: Icon 6.57 Sec
  • Launch time: Icon 3.19 Sec
  • Application size: Icon 2.45 MB
  • Last tested on : 22/03/2017
  • Build ID
    :   v1.1.6
  • Chhi Score
    :   1.1
  • Change Rate
    :   -31.25 %

What to fix?

6 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

3 Risk(s) are due to Data Sent/Received in Network 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.

Potential risk in Memory: Utilization has gone up by36.36% compared to build v2.2.3

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

Fixing Network risks could drastically improve Chhi Score. There are 3 Network risks.

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

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

Consider re-merging the code from build v2.2.3, Memory score was 2.2

The app's memory score is 1.4 due to high memory utilization. Needs to be fixed as priority.

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.

6 tests need immediate attention. View performance graph.

The app's CPU score has improved by 38.89% compared to build v2.2.3! Good job!

2 Risk(s) are due to App Total in Memory exceeding the threshold.

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Network utilization on LYF 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

Your average App Dalvik usage surged by 2.9%, Your memory score is 1.4

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

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

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

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

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

52.17 MB of App Dalvik utilized by activity www.ijoysoft.browser.activities.MainActivity. View details

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

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

Total Network data consumed was 3076.87KB in YU Yuphoria , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

Screen coverage

Test Flows YU Yuphoria LYF Zenfone 2 Laser LG Nexus 5X Samsung Duos Galaxy J7

Install app

  • Risk

  • Risk

  • Risk

  • Success

  • Risk

Scenario 2

  • Risk

  • Risk

competition benchmark

This app is ranked #735 in Social