App Quality Dashboard

ZALORA

3.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 29.05 Sec
  • Launch time: Icon 1.54 Sec
  • Application size: Icon 6.69 MB
  • Last tested on : 16/05/2017
  • Build ID
    :   v4.1.4
  • Chhi Score
    :   3.9
  • Change Rate
    :   +50 %

What to fix?

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

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

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

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

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

Utilization of Network is close to the threshold.

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

The app's CPU score has improved by 53.85% compared to build v4.1.2! Good job!

Build v4.1.2 did better in Memory . Spikes in Memory contributed to score drop by 2.5%

20 tests need immediate attention. View performance graph.

The app's Network score has improved by 116.67% compared to build v4.1.2! Good job!

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

42.11 MB of App Dalvik utilized by activity pt.rocket.view.activities.MainFragmentActivity. View details

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

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

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

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

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

Network utilization on Panasonic P55 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Well done, Network consumption has come down by 57.7 % compared to build v4.1.2

Screen Coverage

competition benchmark

This app is ranked #171 in Shopping

166
167
168
169
170
back-to-top