App Quality Dashboard

O Shopping

1.5 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 5.33 Sec
  • Launch time: Icon 0.94 Sec
  • Application size: Icon 1.19 MB
  • Last tested on : 28/04/2017
  • Build ID
    :   v1.0.4
  • Chhi Score
    :   1.5
  • Change Rate
    :   -25 %

What to fix?

App launch time went up by 70.91% 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.

Build v1.0.2 did better in CPU . Spikes in CPU contributed to score drop by 29.41%

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

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

Build v1.0.2 did better in Memory . Spikes in Memory contributed to score drop by 36.36%

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

Consider re-merging the code from build v1.0.2, Memory score was 3.3

8 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v1.0.2, CPU score was 3.4

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

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

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

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

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

Your average App Dalvik usage surged by 2.8%, Your memory score is 2.1

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Network utilization on Zenfone 2 Laser 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

38.67 MB of App Dalvik utilized by activity com.acjmall.mall.init.activity.InitActivity. View details

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

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

App makes 5242.99 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.

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

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

competition benchmark

This app is ranked #713 in Shopping

708
709
710
711
712
back-to-top