App Quality Dashboard

News on Android™

1.1 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




Medium Risk






  • Install time: Icon 16.71 Sec
  • Launch time: Icon 5.33 Sec
  • Application size: Icon 5.68 MB
  • Last tested on : 13/06/2017
  • Build ID
    :   v2.2.2
  • Chhi Score
    :   1.1
  • Change Rate
    :   -8.33 %

What to fix?

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

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 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

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

Build 2.2.0 did better in Memory . Spikes in Memory contributed to score drop by 7.89%

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

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

Utilization of CPU is close to the threshold.

39 tests need immediate attention. View performance graph.

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

The app's Network score has improved by 36.36% compared to build 2.2.0! Good job!

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

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

Network utilization on Coolpad Note 3 exceeded 1024 KB, you might want to consider bringing it down

Total Network data consumed was 1384.91KB in Samsung Galaxy Note II N7100 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

Your average App Dalvik usage surged by 16.17%, Your memory score is 3.5

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

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

Network utilization on Samsung Galaxy Note II N7100 exceeded 1024 KB, you might want to consider bringing it down

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

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

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.

66.44 MB of App Dalvik utilized by activity it.pinenuts.newsengine.PinenutsRssReaderActivity. View details

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

435 apps having similar CPU load have low Chhi Scores

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

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

Well done, Network consumption has come down by 26.97 % compared to build 2.2.0

Screen Coverage

competition benchmark

This app is ranked #1269 in News & Magazines