Facebook

0.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 38.67 Sec
  • Launch time: Icon 19.35 Sec
  • Application size: Icon 75.82 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v143.0.0.32.90
  • Chhi Score
    :   0.7
  • Change Rate
    :   -68.18 %

Testing depth

Covered

45%

Uncovered

55%

Depth Details

What to fix?

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

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by InFocus might experience a crash on their phone!. Fix now!

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

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

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

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 CPU: Utilization has gone up by 33.33% compared to build v122.0.0.17.71

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Build v122.0.0.17.71 did better in Memory . Spikes in Memory contributed to score drop by 33.33%

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

27 tests need immediate attention. View performance graph.

27 Risk(s) are due to CPU Load in CPU exceeding the threshold.

Utilization of Memory is close to the threshold.

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

Karbonn Titanium Machfive, Panasonic P55, YU Yuphoria has moved from Good to Medium risk due to RISK . View details

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

Consider re-merging the code from build v122.0.0.17.71, CPU score was 1.5

Consider re-merging the code from build v122.0.0.17.71, Memory score was 3.6

3 Tests crashed out of 30 Tests. Check where the app crashed. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

59.08 MB of App Dalvik utilized by activity com.facebook.katana.dbl.activity.FacebookLoginActivity. View details

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

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.

213 apps having similar CPU load have low Chhi Scores

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

The app has crashed on few device(s)! View details

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

The app's Network score has improved by 14.29% compared to build v122.0.0.17.71! Good job!

Well done, Network consumption has come down by 78.94 % compared to build v122.0.0.17.71

competition benchmark

This app is ranked #757 in Social

752
753
754
755
756
back-to-top