Magic Earth Pro

1.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




High Risk






  • Install time: Icon 27.33 Sec
  • Launch time: Icon 0.92 Sec
  • Application size: Icon 32.72 MB
  • Last tested on : 12/04/2017
  • Build ID
    :   v7.
  • Chhi Score
    :   1.3
  • Change Rate
    :   +18.18 %

What to fix?

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

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 Network risks could drastically improve Chhi Score. There are 3 Network risks.

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

Potential risk in Network: Utilization has gone up by29.41% compared to build v7.1.17.9.F86674D.2699AC0

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

Build v7.1.17.9.F86674D.2699AC0 did better in CPU . Spikes in CPU contributed to score drop by 21.05%

The app's memory score is 1.8 due to high memory utilization. Needs to be fixed as priority.

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

Consider re-merging the code from build v7.1.17.9.F86674D.2699AC0, Network score was 1.7

Utilization of CPU is close to the threshold.

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

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

7 tests need immediate attention. View performance graph.

The app's Memory score has improved by 12.5% compared to build v7.1.17.9.F86674D.2699AC0! Good job!

Consider re-merging the code from build v7.1.17.9.F86674D.2699AC0, CPU score was 3.8

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

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

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

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

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

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

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

Network utilization on Karbonn Titanium Machfive exceeded 1024 KB, you might want to consider bringing it down

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Total Network data consumed was 5444.67KB in Karbonn Titanium Machfive , 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.

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

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

27.13 MB of App Dalvik utilized by activity com.route66.maps5.mvc.SearchAddressActivity. View details

Screen coverage

competition benchmark

This app is ranked #455 in Maps & Navigation