App Quality Dashboard

WebMDRx

3.0 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 15.77 Sec
  • Launch time: Icon 2.86 Sec
  • Application size: Icon 4.97 MB
  • Last tested on : 16/03/2017
  • Build ID
    :   v1.3
  • Chhi Score
    :   3.0
  • Change Rate
    :   +50 %

What to fix?

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 CPU risks could drastically improve Chhi Score. There are 5 CPU risks.

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

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

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

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

Build v1.2.1 did better in Memory . Spikes in Memory contributed to score drop by 9.68%

The app's Network score has improved by 44.44% compared to build v1.2.1! Good job!

1 Risk(s) are due to CPU Load in CPU exceeding the threshold.

Utilization of CPU is close to the threshold.

7 tests need immediate attention. View performance graph.

The app's CPU score has improved by 16.67% compared to build v1.2.1! Good job!

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

Utilization of Memory is close to the threshold.

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

33.66 MB of App Dalvik utilized by activity com.webmd.webmdrx.HomeActivity. View details

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

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

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

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

Well done, Network consumption has come down by 25.36 % compared to build v1.2.1

Screen coverage

competition benchmark

This app is ranked #686 in Health & Fitness

681
682
683
684
685
back-to-top