App Quality Dashboard

KFC

1.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 9.00 Sec
  • Launch time: Icon 3.39 Sec
  • Application size: --- 4.30 MB
  • Last tested on : 10/03/2017
  • Build ID
    :   v2.5.0
  • Chhi Score
    :   1.8
  • Change Rate
    :   -47.06 %

What to fix?

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

Potential risk in Network: Utilization has gone up by50% compared to build 2.4.0

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

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.

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

Build 2.4.0 did better in Memory . Spikes in Memory contributed to score drop by 12.9%

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

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

3 tests need immediate attention. View performance graph.

Consider re-merging the code from build 2.4.0, Network score was 2.4

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.

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

The app's CPU score has improved by 4.76% compared to build 2.4.0! Good job!

Utilization of CPU is close to the threshold.

Caching: Use LruCache for data caching to optimize memory usage

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

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

Total Network data consumed was 1466.67KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

38.10 MB of App Dalvik utilized by activity com.kfc.app.MainActivity. View details

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

Your average App Dalvik usage surged by 5.8%, Your memory score is 2.7

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

Screen coverage

Test Flows YU Yuphoria Zenfone 2 Laser Micromax Canvas A1 AQ4502 Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Success

  • Success

  • Risk

  • Risk

competition benchmark

This app is ranked #2752 in Lifestyle

2747
2748
2749
2750
2751
back-to-top