Help for owners
My app feels slow and laggy for customers
Short answer
A slow app is either slow on the phone (heavy screens, big images, work done on the main thread) or slow waiting for the server (slow answers, poor network). Find out which by timing one action on a good connection, then on a poor one. The fix and the person who does it differ.
Does this sound like your situation?
- Screens take a long time to show their data.
- Scrolling stutters or buttons react late.
- It is fine on my new phone and slow on customers' older phones.
- It was fast with a few users and slowed as data grew.
- It is slow mainly on mobile data, or only at busy times.
Why does this happen?
The app does heavy work on the main thread
Android vitals lists app startup time and slow rendering among the quality measures Google Play collects, from users who allow it. Work that blocks the screen, such as large lists, unoptimised images or heavy processing, makes an app feel stuck.
Confirmed by developer.android.com
The server answers slowly
Each screen waits for the server's answer. Slow database queries or an undersized server delay every screen, however well the app itself is built.
Technical detail: A statement waited for a lock held by another transaction and gave up (error 1205)
The network is poor
Google's guidance for crash reproduction notes that users frequently move in and out of mobile and Wi-Fi coverage, and that network behaviour should be treated as a normal operating condition. An app that was only tested on office Wi-Fi may feel slow in the field.
Confirmed by developer.android.com
It was only tested on new phones
Older and cheaper devices have less memory and slower processors. A screen that is fine on a modern phone can lag on theirs.
What can I do about it today?
- Find one exact action that is slowFor example opening the order list. Write down the steps, the phone model and how long it takes.
- Try it on Wi-Fi and on mobile dataIf only mobile data is slow, the app downloads too much or the server is far away.
- Try an older phoneBorrow one. If it is slow only there, the app is too heavy for modest devices.
- Check the Console's own reportsIn Play Console, Android vitals shows crashes, startup time and slow rendering for the users who share data.
- Avoid a rewrite as a first reactionMost slow screens have one or two causes, and finding them is cheaper than starting again.
When should I bring someone in?
- The slowness comes with longer waiting times for customers or lost orders.
- It got worse as data grew.
- Your developer says the app is fine, but users disagree.
How do I handle it?
- Time the app and the server separatelyI measure how long the server takes to answer and how long the phone takes to show it.
- Look at the worst screens firstThe slowest, most-used screens decide how the whole app feels.
- Fix the causeQueries, caching, image sizes and screen work, one at a time with before-and-after measurements.
- Check on an older phoneI confirm the improvement on modest hardware and on a weak connection, not only on a new device.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is it my phone?
If other apps are fast on the same phone and yours is not, the app or its server is the cause.
Will a faster server fix it?
Only if the server is the slow part. Measure before paying for more.
Is my website slow too?
That is a different set of causes. See my page on a very slow website.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.