App Quality Dashboard

Vrat(Fast) Recipe

3.0 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 21.08 Sec
  • Launch time: Icon 12.02 Sec
  • Application size: Icon 7.20 MB
  • Last tested on : 06/05/2017
  • Build ID
    :   v1.0.3
  • Chhi Score
    :   3.0
  • Change Rate
    :   +20 %

What to fix?

Build v1.0.1 did better in Network . Spikes in Network contributed to score drop by 29.55%

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

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

Build v1.0.1 did better in CPU . Spikes in CPU contributed to score drop by 7.14%

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

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

17 tests need immediate attention. View performance graph.

App size increased by 42.01% See how to optimize.

The app's Memory score has improved by 12.5% compared to build v1.0.1! Good job!

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

Consider re-merging the code from build v1.0.1, Network score was 4.4

The app took 12.02 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.

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

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

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

64.75 MB of App Dalvik utilized by activity com.fireball.upvasfastrecipehindi.PrefernceActivity. View details

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

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

App makes 1456.86 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.

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

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

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1675 in Lifestyle