App Quality Dashboard

Speedtest

1.0 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: 15.33 Sec
  • Launch time: 1.65 Sec
  • Application size : 15.16 MB
  • Last tested on : 05/03/2017
  • Build ID
    :   3.2.29
  • Chhi Score
    :   1.0
  • Change Rate
    :   0%

Testing depth

Covered

15%

Uncovered

85%

Depth Details

What to fix?

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

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

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

Your App Memory 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

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

1 tests need immediate attention. View performance graph.

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.

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

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

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

42.81 MB of App Dalvik utilized by activity com.ookla.speedtest.softfacade.MainActivity. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

Screen coverage

Test Flows YU Yuphoria Samsung Duos Galaxy J7

Install app

  • Risk

  • Success

Scenario 2

  • Success

competition benchmark

This app is ranked #1821 in Tools

1816
1817
1818
1819
1820
back-to-top