App Quality Dashboard

TamilMatrimony

3.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 25.00 Sec
  • Launch time: Icon 1.57 Sec
  • Application size: Icon 9.01 MB
  • Last tested on : 21/02/2017
  • Build ID
    :   5.2
  • Chhi Score
    :   3.3
  • Change Rate
    :   -5.71 %

What to fix?

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

Build 2.1 did better in Memory . Spikes in Memory contributed to score drop by 5.88%

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

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.

6 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

The app's CPU score has improved by 3.33% compared to build 2.1! Good job!

Utilization of Memory is close to the threshold.

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

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

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!

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

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

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

36.60 MB of App Dalvik utilized by activity com.bharatmatrimony.login.SplashScreen. View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Well done, Network consumption has come down by 35.98 % compared to build 2.1

The app's Network score has improved by 6.98% compared to build 2.1! Good job!

Screen coverage

competition benchmark

This app is ranked #386 in Social

381
382
383
384
385
back-to-top