App Quality Dashboard

Telegraph Android Tablet

1.6 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 29.56 Sec
  • Launch time: 5.44 Sec
  • Application size : 16.85 MB
  • Last tested on : 16/03/2017
  • Build ID
    :   v3.3.1
  • Chhi Score
    :   1.6
  • Change Rate
    :   0%

What to fix?

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

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

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

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

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

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

The app took 5.44 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) YU, Motorola, Lava, Lenovo, Asus, LYF, Panasonic. Check coverage report for more details.

Utilization of CPU is close to the threshold.

22 tests need immediate attention. View performance graph.

Total Network data consumed was 5868.26KB 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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

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

60.50 MB of App Dalvik utilized by activity uk.co.telegraph.kindlefire.ui.editionreader.EditionReaderActivity. View details

Screen coverage

competition benchmark

This app is ranked #1118 in News & Magazines

1113
1114
1115
1116
1117
back-to-top