App Quality Dashboard

Wizz Air

1.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 25.33 Sec
  • Launch time: --- 3.00 Sec
  • Application size: Icon 18.39 MB
  • Last tested on : 11/03/2017
  • Build ID
    :   v4.5.0
  • Chhi Score
    :   1.9
  • Change Rate
    :   +5.56 %

What to fix?

1 Risk(s) are due to Threads in CPU 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.

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

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

Build v4.4.0 did better in CPU . Spikes in CPU contributed to score drop by 7.41%

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

Utilization of CPU is close to the threshold.

8 tests need immediate attention. View performance graph.

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

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

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

34.31 MB of App Dalvik utilized by activity com.wizzair.WizzAirApp.ui.HomeActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

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

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

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

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

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

Well done, Network consumption has come down by 50.33 % compared to build v4.4.0

competition benchmark

This app is ranked #401 in Maps & Navigation

396
397
398
399
400
back-to-top