App Quality Dashboard

CGV

2.4 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 19.67 Sec
  • Launch time: Icon 0.77 Sec
  • Application size: Icon 15.32 MB
  • Last tested on : 03/05/2017
  • Build ID
    :   v4.4.1
  • Chhi Score
    :   2.4
  • Change Rate
    :   0%

What to fix?

2 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.

The app'sNetwork score has improved by33.33%!

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

3 tests need immediate attention. View performance graph.

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

37.58 MB of App Dalvik utilized by activity com.cjs.cgv.movieapp.intro.IntroActivity. View details

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!

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

Network utilization on Samsung Galaxy J7 exceeded 1024 KB, you might want to consider bringing it down

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

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

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

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

Network utilization on LYF-WATER exceeded 1024 KB, you might want to consider bringing it down

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

Screen Coverage

competition benchmark

This app is ranked #1493 in Entertainment

1488
1489
1490
1491
1492
back-to-top