App Quality Dashboard

Telemundo Puerto Rico

0.2 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Medium  Risk

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 56.75 Sec
  • Launch time: Icon 0.84 Sec
  • Application size: Icon 46.47 MB
  • Last tested on : 21/03/2017
  • Build ID
    :   v5.4
  • Chhi Score
    :   0.2
  • Change Rate
    :   -33.33 %

What to fix?

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

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

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

Must fix: App crashed because of 9359): FATAL EXCEPTION: f 9359): Process: com.nbcuni.telemundostations.puertorico PID: 9359 935... Users with phone manufactured by Panasonic 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

Fixing CPU risks could drastically improve Chhi Score. There are 11 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

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

Utilization of Memory is close to the threshold.

Samsung Duos Galaxy J7, Karbonn Titanium Machfive, Panasonic P55 has moved from Good to Medium risk due to RISK . View details

Utilization of CPU is close to the threshold.

The app has a high performance risk for the phone manufacturer(s) Panasonic, Samsung, Karbonn, Lenovo. Check coverage report for more 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.

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

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

11 tests need immediate attention. View performance graph.

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

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

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

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

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

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

435 apps having similar CPU load have low Chhi Scores

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

93.00 MB of App Dalvik utilized by activity 1924. View details

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

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

Screen coverage

Test Flows Panasonic P55 Karbonn Titanium Machfive Lenovo VIBE K4 Note Samsung Duos Galaxy J7

Install app

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Crash

  • Risk

  • Risk

  • Success

Scenario 2

  • Risk

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #1404 in News & Magazines

1399
1400
1401
1402
1403
back-to-top