App Quality Dashboard

Thozhil Ullagam

2.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 27.28 Sec
  • Launch time: Icon 0.76 Sec
  • Application size: Icon 16.02 MB
  • Last tested on : 10/06/2017
  • Build ID
    :   v6.1
  • Chhi Score
    :   2.3
  • Change Rate
    :   -37.84 %

What to fix?

Build v6.0 did better in CPU . Spikes in CPU contributed to score drop by 3.33%

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.

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

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

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

Potential risk in Network: Utilization has gone up by39.13% compared to build v6.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).

Utilization of CPU is close to the threshold.

The app's Memory score has improved by 2.86% compared to build v6.0! Good job!

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

10 tests need immediate attention. View performance graph.

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

App size increased by 34.4% See how to optimize.

Utilization of Memory is close to the threshold.

Consider re-merging the code from build v6.0, Network score was 2.3

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

52.57 MB of App Dalvik utilized by activity com.magzter.thozhilullagam.MainActivity. View details

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

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

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

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

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

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

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

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

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 2021.32KB 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

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

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

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

Test Flows YU Yuphoria Panasonic P55 LYF Karbonn Titanium Machfive Zenfone 2 Laser Micromax Canvas A1 Motorola Moto E (2nd gen)

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Success

  • Success

  • Success

  • Success

  • Success

  • Success

  • Risk

Scenario 2

  • Success

  • Success

  • Risk

  • Risk

competition benchmark

This app is ranked #1050 in Business

1045
1046
1047
1048
1049
back-to-top