App Quality Dashboard

Mega Curioso

3.0 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 29.63 Sec
  • Launch time: Icon 1.29 Sec
  • Application size: Icon 10.69 MB
  • Last tested on : 20/04/2017
  • Build ID
    :   v1.8.3d
  • Chhi Score
    :   3.0
  • Change Rate
    :   -14.29 %

What to fix?

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

15 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 15 High Risk(s).

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

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.

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

Build v1.8.2d did better in CPU . Spikes in CPU contributed to score drop by 3.23%

Build v1.8.2d did better in Network . Spikes in Network contributed to score drop by 20.83%

Build v1.8.2d did better in Memory . Spikes in Memory contributed to score drop by 18.18%

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

19 tests need immediate attention. View performance graph.

App size increased by 25.62% See how to optimize.

Utilization of CPU is close to the threshold.

7 Risk(s) are due to App Total in Memory exceeding the threshold.

Utilization of Network is close to the threshold.

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

Consider re-merging the code from build v1.8.2d, Memory score was 3.3

Consider re-merging the code from build v1.8.2d, Network score was 2.4

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Total Network data consumed was 1123.89KB in Samsung Galaxy Note II N7100 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

Your average App Dalvik usage surged by 16.03%, Your memory score is 2.7

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

Network utilization on Moto G (3rd 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

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

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

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

56.50 MB of App Dalvik utilized by activity com.gruponzn.megacurioso.activities.ArticleActivity. View details

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

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

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

Screen coverage

competition benchmark

This app is ranked #475 in News & Magazines

470
471
472
473
474
back-to-top