App performance optimisation: faster starts, smoother screens

Why app speed matters, which performance metrics to watch, and practical ways to improve start-up time, scrolling, network use, battery and app size.

By the UK Technology Hub teamPublished 4 minute read

The short answer

Fast, smooth apps keep users; slow ones get deleted and earn poor reviews. Focus on quick start-up, smooth scrolling and animations, efficient network use, optimised images, sensible memory use, low battery impact and a reasonable download size. Measure real-world performance with monitoring tools, set performance budgets and test on mid-range devices, not just the latest phones.

Users notice slow apps immediately: a long splash screen, stuttering lists, spinners everywhere. Performance affects retention, ratings and app store visibility, as both Apple and Google consider quality signals. Here's where to focus.

Key performance metrics

  • Start-up time: how long until the app is usable after tapping the icon. Cold starts, when the app isn't in memory, are the slowest.
  • Frame rendering: smooth screens draw frames within the display's refresh window, around 16 milliseconds at 60 frames per second and less on faster displays. Dropped frames cause visible stutter.
  • Responsiveness: how quickly the app reacts to taps. On Android, a frozen main thread can cause "Application Not Responding" errors; see our guide to fixing Android ANRs.
  • Network latency and data use.
  • Memory use and crashes. Our guide to fixing iOS crashes on launch covers a common crash scenario.
  • Battery impact.
  • App size.

Speed up start-up

  • Do only essential work before showing the first screen.
  • Defer non-critical initialisation, such as analytics and secondary SDKs.
  • Load data asynchronously and show content progressively.
  • Reduce the number of third-party SDKs initialised at launch.
  • Cache recent data to show immediately while refreshing.

Smooth scrolling and animations

  • Keep heavy work off the main thread.
  • Use list components that recycle views efficiently.
  • Avoid complex nested layouts.
  • Load and decode images in the background.
  • Profile animations and simplify where frames drop.

Network efficiency

  • Request only the data a screen needs.
  • Combine requests where possible.
  • Cache responses and use conditional requests.
  • Compress payloads.
  • Paginate long lists.
  • Handle poor connections gracefully with retries and timeouts.

Images and media

  • Serve images sized for the device.
  • Use efficient formats.
  • Cache images on the device.
  • Lazy-load images as users scroll.
  • Stream video rather than downloading whole files.

Memory

  • Release resources when screens close.
  • Avoid holding large images in memory unnecessarily.
  • Fix memory leaks found by profiling tools.

Battery

  • Batch background work.
  • Use platform scheduling tools for background tasks.
  • Limit location updates to the accuracy and frequency needed.
  • Avoid unnecessary wake-ups and polling.

App size

Large apps put users off downloading, especially on limited data plans. Reduce size by removing unused resources and libraries, compressing assets and using platform features like app bundles and on-demand resources.

Cross-platform considerations

React Native and Flutter apps can perform very well, but performance depends on avoiding unnecessary re-renders, keeping heavy work off the UI thread and using native modules where needed. Profile on real devices.

Monitor real-world performance

Lab tests on fast phones hide problems. Use performance monitoring tools that collect data from real users' devices, and check the Android vitals dashboard in Google Play Console and Xcode Organizer metrics for iOS. Track performance by device type, OS version and region.

Set performance budgets

Agree targets, such as cold start under two seconds on a mid-range device, and check them in automated tests before each release. Budgets stop gradual slowdowns as features are added.

Test on realistic devices

Test on mid-range and older devices that represent your users, with slow networks and low battery modes. That's where performance problems appear.

Performance and app store ratings

Users rarely praise a fast app, but they're quick to complain about a slow one. Reviews mentioning lag, freezing or battery drain hurt ratings and downloads. Monitoring performance by device and OS version lets you spot problems early, often before they appear in reviews.

Prioritising fixes

Start with the issues affecting the most users on the most important screens: start-up, the home screen, search and checkout or booking flows. A small improvement on a heavily used screen beats a large improvement on a rarely visited one.

Communicate improvements

When you make the app noticeably faster, mention it in release notes. Users appreciate visible care for quality, and positive changes can encourage better reviews.

Treat performance as a feature with an owner, a budget and regular reviews, rather than something fixed only when users complain.

How we help

Our mobile app development team profiles and optimises iOS and Android apps. Our app development service sets performance budgets and monitoring, and our web app team optimises the APIs that feed your app.

Frequently asked questions

What's a good app start-up time?

Aim for the app to be usable within about two seconds on a typical device. Faster is better.

Why is my app slow on some phones but not others?

Older or budget devices have less processing power and memory. Test and optimise on representative devices.

Do app stores consider performance?

Yes. Both stores use quality signals such as crashes and responsiveness, which can affect visibility.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

All web & mobile apps guides