App Quality Dashboard

Telemundo 40

0.3 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 45.26 Sec
  • Launch time: Icon 8.10 Sec
  • Application size: Icon 37.48 MB
  • Last tested on : 17/03/2017
  • Build ID
    :   v5.4
  • Chhi Score
    :   0.3
  • Change Rate
    :   0%

What to fix?

Build 5.3.1 did better in Network . Spikes in Network contributed to score drop by 18.6%

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

App launch time went up by 151.9% initlizate network calls after few seconds of loading the resources. View details

Potential risk in CPU: Utilization has gone up by 56.52% compared to build 5.3.1

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

23 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 23 CPU risks.

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

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

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

Consider re-merging the code from build 5.3.1, CPU score was 2.3

23 tests need immediate attention. View performance graph.

Consider re-merging the code from build 5.3.1, Network score was 4.3

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

Utilization of CPU is close to the threshold.

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

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

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

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

435 apps having similar CPU load have low Chhi Scores

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

90.00 MB of App Dalvik utilized by activity 1142. View details

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1378 in News & Magazines

1373
1374
1375
1376
1377
back-to-top