App Quality Dashboard

AOL

1.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 19.55 Sec
  • Launch time: Icon 1.21 Sec
  • Application size: Icon 13.45 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v4.4.0.8
  • Chhi Score
    :   1.7
  • Change Rate
    :   0%

What to fix?

2 Risk(s) are due to Data Sent/Received in Network 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.

Build v4.3.0.5 did better in Network . Spikes in Network contributed to score drop by 21.05%

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

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

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

Build v4.3.0.5 did better in Memory . Spikes in Memory contributed to score drop by 4%

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

The app's CPU score has improved by 18.18%

19 tests need immediate attention. View performance graph.

Consider re-merging the code from build v4.3.0.5, Network score was 3.8

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

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

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

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

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

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

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

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

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

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

435 apps having similar CPU load have low Chhi Scores

46.37 MB of App Dalvik utilized by activity com.aol.mobile.aolapp.ui.activity.MainActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1082 in News & Magazines

1077
1078
1079
1080
1081
back-to-top