App Quality Dashboard

Dainik Jagran

2.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 21.23 Sec
  • Launch time: Icon 3.73 Sec
  • Application size: Icon 7.61 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v3.1.2
  • Chhi Score
    :   2.3
  • Change Rate
    :   -41.03 %

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.

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

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

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

Build v3.1.0 did better in CPU . Spikes in CPU contributed to score drop by 5.26%

Potential risk in Network: Utilization has gone up by61.11% compared to build v3.1.0

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

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

Build v3.1.0 did better in Memory . Spikes in Memory contributed to score drop by 5.26%

Consider re-merging the code from build v3.1.0, Network score was 3.6

Utilization of CPU is close to the threshold.

App size increased by 38.36% See how to optimize.

21 tests need immediate attention. View performance graph.

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

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

Total Network data consumed was 1730.03KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

Your average App Dalvik usage surged by 12.08%, Your memory score is 3.6

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

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

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

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

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

60.19 MB of App Dalvik utilized by activity com.hindi.jagran.android.activity.NotificationCenterActivity. View details

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

Network utilization on Lava Iris X8 exceeded 1024 KB, you might want to consider bringing it down

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

Screen Coverage

competition benchmark

This app is ranked #800 in News & Magazines

795
796
797
798
799
back-to-top