App Quality Dashboard

Wedding Dresses

2.5 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 8.58 Sec
  • Launch time: Icon 0.79 Sec
  • Application size: Icon 9.90 MB
  • Last tested on : 26/05/2017
  • Build ID
    :   v3.117
  • Chhi Score
    :   2.5
  • Change Rate
    :   -26.47 %

What to fix?

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

Build v2.0 did better in CPU . Spikes in CPU contributed to score drop by 14.29%

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

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

Build v2.0 did better in Network . Spikes in Network contributed to score drop by 12.5%

1 Risk(s) are due to Data Sent/Received in Network 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.

Build v2.0 did better in Memory . Spikes in Memory contributed to score drop by 31.25%

Consider re-merging the code from build v2.0, Memory score was 3.2

App size increased by 12.5% See how to optimize.

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v2.0, Network score was 4.0

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

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

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

23 tests need immediate attention. View performance graph.

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.

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

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

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

Your average App Dalvik usage surged by 2.31%, Your memory score is 2.2

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!

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

37.88 MB of App Dalvik utilized by activity com.ansca.corona.CoronaActivity. View details

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

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.

Caching: Use LruCache for data caching to optimize memory usage

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

App makes 3079.18 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

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

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

Screen coverage

competition benchmark

This app is ranked #2218 in Lifestyle

2213
2214
2215
2216
2217
back-to-top