App Quality Dashboard

AJIO

1.3 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 18.40 Sec
  • Launch time: Icon 8.15 Sec
  • Application size: Icon 11.44 MB
  • Last tested on : 29/03/2017
  • Build ID
    :   v3.0
  • Chhi Score
    :   1.3
  • Change Rate
    :   -13.33 %

What to fix?

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

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

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

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

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.9 did better in Memory . Spikes in Memory contributed to score drop by 10%

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

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

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

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

24 tests need immediate attention. View performance graph.

The app's CPU score has improved by 28.57% compared to build v2.9! Good job!

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

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

The app's Network score has improved by 58.82% compared to build v2.9! Good job!

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

48.78 MB of App Dalvik utilized by activity com.ril.ajio.activity.HomeActivity. View details

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

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

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

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!

Well done, Network consumption has come down by 32.51 % compared to build v2.9

Screen coverage

competition benchmark

This app is ranked #729 in Shopping

724
725
726
727
728
back-to-top