App Quality Dashboard

WIFI Key Recovery

0.7 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

High  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: 16.83 Sec
  • Launch time: 18.10 Sec
  • Application size : 6.61 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v4
  • Chhi Score
    :   0.7
  • Change Rate
    :   0%

Insights (35)

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.clearvisions.wifirecoveryfree PID: 25876 java.lang.NullPoint... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.clearvisions.wifirecoveryfree PID: 25876 java.lang.NullPoint... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.clearvisions.wifirecoveryfree PID: 25876 java.lang.NullPoint... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!
12 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.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Lenovo A6000 crashed at com.appnext.appnextsdk.Appnext.showBubble(Appnext.java:789) View details
Motorola Moto E (2nd gen) crashed at com.appnext.appnextsdk.Appnext.showBubble(Appnext.java:789) View details
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.clearvisions.wifirecoveryfree PID: 25876 java.lang.NullPoint... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!
Fixing CPU risks could drastically improve Chhi Score. There are 12 CPU risks.
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.clearvisions.wifirecoveryfree PID: 25876 java.lang.NullPoint... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!
Oops!, The app crashed on Motorola Moto E (2nd gen), Lenovo A6000 & more devices. View details
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.clearvisions.wifirecoveryfree PID: 25876 java.lang.NullPoint... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!
Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.clearvisions.wifirecoveryfree PID: 25876 java.lang.NullPoint... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.clearvisions.wifirecoveryfree PID: 25876 java.lang.NullPoint... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!
The app took 18.10 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
The app has a high performance risk for the phone manufacturer(s) Panasonic, Asus, Lenovo, YU, Karbonn, Micromax, LYF, Motorola. Check coverage report for more details.
12 tests need immediate attention. View performance graph.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Testability: Providing login / sign-up details could very well improve depth of bot clicks
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.
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
43.09 MB of App Dalvik utilized by activity com.appjolt.winback.AppjoltActivity. View details
8 Tests crashed out of 12 Tests. Check where the app crashed. View details
Caching: Use LruCache for data caching to optimize memory usage
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!
Optimize the app to render elements at 60 FPS for buttery smooth experience.
347 apps having similar CPU load have low Chhi Scores
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1882 in Tools

1877
1878
1879
1880
1881
back-to-top