App Quality Dashboard

Telemundo Arizona

0.4 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 58.43 Sec
  • Launch time: 12.53 Sec
  • Application size : 37.28 MB
  • Last tested on : 10/04/2017
  • Build ID
    :   v5.4
  • Chhi Score
    :   0.4
  • 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.

Your App Memory 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

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

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

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

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

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

Make sure your App's Dalvik 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) Lenovo, LYF. Check coverage report for more details.

Utilization of CPU is close to the threshold.

2 Risk(s) are due to App Dalvik in Memory exceeding the threshold.

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

7 tests need immediate attention. View performance graph.

The app's memory score is 0.5 due to high memory utilization. Needs to be fixed as priority.

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

435 apps having similar CPU load have low Chhi Scores

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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.

101.00 MB of App Dalvik utilized by activity 2269. View details

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

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

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

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

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

competition benchmark

This app is ranked #1366 in News & Magazines

1361
1362
1363
1364
1365
back-to-top