App Quality Dashboard

Wifi Analyzer

2.6 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 4.48 Sec
  • Launch time: Icon 3.78 Sec
  • Application size: Icon 1.53 MB
  • Last tested on : 15/02/2017
  • Build ID
    :   3.10.5-L
  • Chhi Score
    :   2.6
  • Change Rate
    :   -18.75 %

What to fix?

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.

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

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

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

Build 3.10.3-L did better in Memory . Spikes in Memory contributed to score drop by 20.69%

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

Build 3.10.3-L did better in Network . Spikes in Network contributed to score drop by 2.44%

18 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build 3.10.3-L, Memory score was 2.9

The app took 3.78 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

Utilization of CPU is close to the threshold.

The app's CPU score has improved by 5% compared to build 3.10.3-L! Good job!

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

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

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

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

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.

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

Caching: Use LruCache for data caching to optimize memory usage

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!

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

39.78 MB of App Dalvik utilized by activity com.farproc.wifi.analyzer.MainScreen. View details

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

Screen Coverage

competition benchmark

This app is ranked #1450 in Tools

1445
1446
1447
1448
1449
back-to-top