App Quality Dashboard

Haberler

0.9 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 28.47 Sec
  • Launch time: Icon 2.06 Sec
  • Application size: Icon 17.31 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v2.1.2
  • Chhi Score
    :   0.9
  • Change Rate
    :   -75 %

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.

Build v2.1.0 did better in Memory . Spikes in Memory contributed to score drop by 36.84%

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

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

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

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

Potential risk in CPU: Utilization has gone up by 56.52% compared to build v2.1.0

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

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

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

Potential risk in Network: Utilization has gone up by67.57% compared to build v2.1.0

Consider re-merging the code from build v2.1.0, CPU score was 2.3

App size increased by 15.4% See how to optimize.

16 tests need immediate attention. View performance graph.

Panasonic P55 health improved from High risk to Medium risk eliminating CRASH

Consider re-merging the code from build v2.1.0, Network score was 3.7

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

Utilization of Network is close to the threshold.

LYF-WATER health improved from High risk to Medium risk eliminating CRASH

Motorola Moto E (2nd gen) health improved from High risk to Medium risk eliminating CRASH

Consider re-merging the code from build v2.1.0, Memory score was 3.8

Utilization of CPU is close to the threshold.

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

Utilization of Memory is close to the threshold.

Lenovo VIBE K4 Note health improved from High risk to Medium risk eliminating CRASH

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

Network utilization on Panasonic P55 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

62.67 MB of App Dalvik utilized by activity tr.com.yenimedya.haberler.MainActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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.

Your average App Dalvik usage surged by 34.3%, Your memory score is 2.4

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

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

Screen coverage

competition benchmark

This app is ranked #1329 in News & Magazines

1324
1325
1326
1327
1328
back-to-top