Tumblr

2.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 36.40 Sec
  • Launch time: Icon 1.56 Sec
  • Application size: Icon 25.61 MB
  • Last tested on : 20/04/2017
  • Build ID
    :   v8.3.0.00
  • Chhi Score
    :   2.3
  • Change Rate
    :   0%

What to fix?

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.

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

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

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

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

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

Potential risk in CPU: Utilization has gone up by 20% compared to build v8.2.0.00

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

Utilization of CPU is close to the threshold.

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

13 tests need immediate attention. View performance graph.

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

Utilization of Memory is close to the threshold.

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

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.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

213 apps having similar CPU load have low Chhi Scores

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

76.89 MB of App Dalvik utilized by activity com.yahoo.mobile.client.share.activity.SignUpActivity. View details

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

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

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 Panasonic P55 LYF Karbonn Titanium Machfive Zenfone 2 Laser Micromax Canvas A1 AQ4502 Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Success

Scenario 2

  • Success

competition benchmark

This app is ranked #585 in Social

580
581
582
583
584
back-to-top