We are encountering the following Android vitals issues:
- Slow warm start (4%)
- Excessive frozen frames (12%)
These issues are more prevalent on devices with xhdpi screen density (DPI).
We believe the root cause is the banner ads from AdMob. When we disabled the banner ads from AdMob, we noticed a decline in these issues.
I suspect that AdMob might be using the WebView component for rendering, which is known to be resource-intensive and can affect performance.
AdMob accounts for 50% of our total revenue, so disabling it entirely would have a significant impact on our earnings. However, we also recognize the importance of Android vitals for our app's ranking in the Google Play store.
Has anyone else experienced similar problems with AdMob? And would switching to native ads potentially address these concerns?
Thank you.
Top comments (1)
While I have never heard, nor used AdMob before I did look into it. A lot of the optimization tips I found were on financial gain over runtime. This stack overflow post spirals into this old conversation thread.
While they're both older that the dinosaurs, it does look like there's two variations of troubleshooting I'm seeing. One being reverting the version from the sub-optimal one, to an older and perhaps more optimal one. Another being refactoring your code so that the initial view takes place in the background. As the longest loading seems to be the initial one, while creating a cookie.
Not entirely sure, just what I gleaned off of the threads. Best of luck, and good scrounging! Make your $$$