App Quality Dashboard

WKRG WX

0.9 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 46.20 Sec
  • Launch time: 10.11 Sec
  • Application size : 16.57 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v4.4.800
  • Chhi Score
    :   0.9
  • Change Rate
    :   0%

What to fix?

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

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

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

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

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

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

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

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

The app has a high performance risk for the phone manufacturer(s) Lenovo. Check coverage report for more details.

Utilization of Memory is close to the threshold.

5 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

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

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

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Network utilization on Lenovo VIBE K4 Note 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

130 apps having similar CPU load have low Chhi Scores

152.32 MB of App Dalvik utilized by activity com.wsi.android.weather.ui.MasterActivity. View details

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

Screen coverage

Test Flows Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

Scenario 2

  • Risk

competition benchmark

This app is ranked #431 in Weather

426
427
428
429
430
back-to-top