App Quality Dashboard

Quikr

1.1 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 35.35 Sec
  • Launch time: Icon 17.53 Sec
  • Application size: Icon 15.04 MB
  • Last tested on : 20/06/2017
  • Build ID
    :   v8.86
  • Chhi Score
    :   1.1
  • Change Rate
    :   -47.62 %

What to fix?

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

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

Build v9.08 did better in Memory . Spikes in Memory contributed to score drop by 2.94%

Potential risk in CPU: Utilization has gone up by 28.57% compared to build v9.08

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

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

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

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 v9.08 did better in Network . Spikes in Network contributed to score drop by 3.13%

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

Utilization of Memory is close to the threshold.

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

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

17 tests need immediate attention. View performance graph.

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

200 apps having similar CPU load have low Chhi Scores

Caching: Use LruCache for data caching to optimize memory usage

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.

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

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

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

59.29 MB of App Dalvik utilized by activity com.quikr.userv2.login.LoginActivity. View details

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

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

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #761 in Shopping

756
757
758
759
760
back-to-top