App Quality Dashboard

Justdial lite

1.2 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 4.50 Sec
  • Launch time: Icon 1.00 Sec
  • Application size: --- 1.41 MB
  • Last tested on : 27/04/2017
  • Build ID
    :   v3.3
  • Chhi Score
    :   1.2
  • Change Rate
    :   -36.84 %

What to fix?

Potential risk in Memory: Utilization has gone up by44.83% compared to build v3.2

Build v3.2 did better in CPU . Spikes in CPU contributed to score drop by 4%

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

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

Your App Memory 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

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

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

4 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v3.2, Memory score was 2.9

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

38.38 MB of App Dalvik utilized by activity com.justdial.jdlite.JdLiteMainActivity. View details

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

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

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

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

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

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

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

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

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

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.

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

Your average App Dalvik usage surged by 24.18%, Your memory score is 1.6

Well done, Network consumption has come down by 18.74 % compared to build v3.2

Screen Coverage

competition benchmark

This app is ranked #1097 in Travel & Local

1092
1093
1094
1095
1096
back-to-top