App Quality Dashboard

Joule

1.4 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

High Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 60.38 Sec
  • Launch time: Icon 2.78 Sec
  • Application size: Icon 61.21 MB
  • Last tested on : 11/05/2017
  • Build ID
    :   v2.48.3
  • Chhi Score
    :   1.4
  • Change Rate
    :   -46.15 %

Insights (33)

What to fix?

App launch time went up by INF% 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
Fixing CPU risks could drastically improve Chhi Score. There are 7 CPU risks.
7 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
Potential risk in CPU: Utilization has gone up by 34.78% compared to build v2.47.2
Build v2.47.2 did better in Memory . Spikes in Memory contributed to score drop by 9.52%
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.
7 Risk(s) are due to Threads in CPU exceeding the threshold.
Fixing Network risks could drastically improve Chhi Score. There are 7 Network risks.
The app has a high performance risk for the phone manufacturer(s) Lenovo, YU, Karbonn, Micromax, LYF, Panasonic, Motorola. Check coverage report for more details.
13 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
Consider re-merging the code from build v2.47.2, CPU score was 2.3
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
81 apps having similar CPU load have low Chhi Scores
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
App makes 16147.12 KB of network requests. Moving this to a background thread will improve load speed. View details
44.01 MB of App Dalvik utilized by activity com.chefsteps.circulator.MainActivity. View details
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Total Network data consumed was 16147.12KB 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 Karbonn Titanium Machfive exceeded 1024 KB, you might want to consider bringing it down
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Caching: Use LruCache for data caching to optimize memory usage
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
Your average App Dalvik usage surged by 2.66%, Your memory score is 1.9
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.
Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #380 in Food & Drink

375
376
377
378
379
back-to-top