App Quality Dashboard

RussianBrides

1.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 28.78 Sec
  • Launch time: Icon 3.41 Sec
  • Application size: Icon 13.27 MB
  • Last tested on : 30/04/2017
  • Build ID
    :   v2.2.0
  • Chhi Score
    :   1.8
  • Change Rate
    :   +5.88 %

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 16 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

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

16 Risk(s) are due to Threads in CPU 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.

The app's Memory score has improved by 11.54% compared to build v2.1.0! Good job!

The app's CPU score has improved by 36.36%

Build v2.1.0 did better in Network . Spikes in Network contributed to score drop by 2%

17 tests need immediate attention. View performance graph.

Utilization of Memory is close to the threshold.

Utilization of CPU is close to the threshold.

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

213 apps having similar CPU load have low Chhi Scores

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

Caching: Use LruCache for data caching to optimize memory usage

51.70 MB of App Dalvik utilized by activity com.sdv.np.ui.authorization.AuthActivity. View details

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.

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

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

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

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

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

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

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 #636 in Social

631
632
633
634
635
back-to-top