App Quality Dashboard

JW.ORGポッドキャスト

  • Install time: 23.33 Sec
  • Launch time: 6.10 Sec
  • Application size : 10.68 MB
  • Last tested on : 10/05/2017
  • Build ID
    :   v4.0
  • CHHI Score
    :   1.8
  • Change Rate
    :   0%

1.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

Category

Rank

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.

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

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

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

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

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

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

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

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.

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

5 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

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

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

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

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

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

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

Total Network data consumed was 1264.77KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

35.87 MB of App Dalvik utilized by activity com.appyet.activity.MainActivity. View details

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

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

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

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

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

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

Screen coverage

Test Flows YU Yuphoria Zenfone 2 Laser Lenovo A6000 Samsung Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Risk

  • Risk

  • Risk

  • Success

  • Risk

Scenario 2

  • Risk

competition benchmark

This app is ranked #1264 in Books & Reference

1259
1260
1261
1262
1263
back-to-top