App Quality Dashboard

Talabat

0.8 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 28.27 Sec
  • Launch time: Icon 2.51 Sec
  • Application size: Icon 10.42 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v4.5.1
  • Chhi Score
    :   0.8
  • Change Rate
    :   +14.29 %

What to fix?

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

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

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

App launch time went up by 118.26% 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 v4.5 did better in Network . Spikes in Network contributed to score drop by 8.7%

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

The app's Memory score has improved by 4.76% compared to build v4.5! Good job!

14 tests need immediate attention. View performance graph.

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

Caching: Use LruCache for data caching to optimize memory usage

81 apps having similar CPU load have low Chhi Scores

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

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!

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

67.74 MB of App Dalvik utilized by activity com.talabat.HomeScreen. View details

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

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #416 in Food & Drink

411
412
413
414
415
back-to-top