Optimizing Network Requests: How to Reduce Screen Load Time?

The main screen of an app makes 14 parallel requests when opened. Seems fast—parallel means quick, right? But HTTP/1.1 limits to 6 connections per host, so 8 requests queue up. On a weak LTE connection with 180 ms RTT, total wait time exceeds 2 seconds. Each second of delay reduces conversion by 7% and retention by 20%. Revenue losses from slow screens can reach millions of rubles monthly.

Switching to HTTP/2 with multiplexing or aggregating requests on a BFF layer (Backend for Frontend) solves this without client-side changes. HTTP/2 multiplexes requests over a single connection, eliminating head-of-line blocking. Our engineers apply both approaches depending on the architecture.

Where Is Time Lost?

Extra requests. The most common issue is lack of client-side caching. URLSession on iOS respects Cache-Control headers by default, but only if the server sets them. If the API returns Cache-Control: no-store "for reliability," every call to reference data (categories, settings, configuration) goes over the network. URLCache with a 50 MB limit and manual URLRequest.cachePolicy = .returnCacheDataElseLoad for read-only endpoints works as a quick fix.

Overweight payloads. A REST endpoint for a user list returns 40 fields, but the UI uses only 4. With a list of 100 items, that's an extra 60–80 KB of JSON per request. GraphQL solves this at the protocol level, but if GraphQL isn't an option, ?fields=id,name,avatar_url as a query parameter for field filtering partially mitigates the issue.

Redundant requests on screen rotation. On Android, ViewModel + LiveData/StateFlow holds the result and doesn't re-run the request when the Activity is recreated. But if the request lives in Fragment.onViewCreated without a check, every rotation triggers a new network call. Diagnose it with Charles Proxy or OkHttp EventListener with logging.

Tools and Solutions: Which Approach to Choose?

iOS (URLSession / Alamofire / Moya)

Alamofire RequestInterceptor is a convenient place for retry logic with exponential backoff:

func retry(_ request: Request, for session: Session, dueTo error: Error,
           completion: @escaping (RetryResult) -> Void) {
    let delay = min(pow(2.0, Double(request.retryCount)), 30.0)
    completion(.retryWithDelay(delay))
}

URLSession with waitsForConnectivity = true makes requests automatically wait for network recovery instead of failing immediately. Critical for offline-first apps.

Android (OkHttp / Retrofit)

OkHttp CacheInterceptor is built in; just pass a Cache when creating the client:

val cache = Cache(context.cacheDir, 50L * 1024 * 1024)
val client = OkHttpClient.Builder().cache(cache).build()

Retrofit + suspend fun cancels requests automatically when the coroutine scope is destroyed. The key is to bind the scope to viewModelScope, not GlobalScope.

Request Deduplication

If several components request the same resource simultaneously, execute the request only once. On iOS, use Combine’s share() operator on a Publisher. On Android, use StateFlow in a Repository: the first subscriber triggers the request, and subsequent subscribers receive the result from the same flow. This aligns with Apple Human Interface Guidelines on responsiveness.

Request Prioritization

On iOS, URLSession supports URLRequest.networkServiceType: .responsiveData for user actions, .background for analytics and prefetch. The system prioritizes traffic accordingly—analytics doesn't compete for bandwidth with user requests.

On Android, WorkManager with NetworkType.CONNECTED and priority EXPEDITED vs. normal allows background data sync without blocking the main request flow.

How to Set Up Caching: Step-by-Step Guide

1. Identify read-only endpoints (directories, categories, configuration).
2. Check if the server sends Cache-Control. If not, force client-side caching.
3. On iOS, set up URLCache with a 50 MB limit and cachePolicy = .returnCacheDataElseLoad.
4. On Android, create OkHttp Cache of 50 MB and pass it to OkHttpClient.
5. For dynamic data, use ETag or Last-Modified: the client sends If-None-Match, the server responds with 304 Not Modified, saving bandwidth.

Comparison of HTTP/1.1 and HTTP/2

HTTP/2 yields a 3-4× improvement on weak networks by eliminating queues.

Case Study: GraphQL N+1 on Mobile

From our practice: an app used GraphQL, but queries were built "as convenient"—a separate query for each card in the list when viewing details. 20 cards = 20 queries. Implementing the DataLoader pattern on the client via @defer directive (supported by Apollo iOS / Apollo Android) allowed batching requests. Detail screen load time dropped from 2.8 s to 0.6 s. Our team's experience shows this approach is also applicable to REST via BFF.

Comparison of Caching Strategies

What’s Included in the Work?

• Audit of the current network layer with timing measurements and traffic analysis.
• Implementation of HTTP/2 or aggregation on BFF.
• Caching setup (URLCache, OkHttp Cache, ETag).
• Request deduplication and batching.
• Payload optimization (GraphQL or field filtering).
• Retry logic and prioritization.
• Documentation and recommendations for ongoing maintenance.

Contact us to order a network layer audit—we'll assess your project in one day.

Why Choose Us?

We have 5+ years of experience in mobile app optimization for iOS and Android. We've completed over 50 projects focused on load speed, caching, and traffic reduction. After the audit, you'll receive concrete recommendations with measurable metrics. Submit a request for an audit and get a detailed report with metrics.

Timeline

Network layer audit and targeted optimizations: 3–5 days. Implementing caching, retry logic, and deduplication across the entire app: 1–2 weeks. Get a consultation—we'll calculate exact timelines for your project.

Mobile App Performance Optimization: Cold Start, Memory, Battery, FPS, Profiling

We often see mobile apps with a cold start time of 4+ seconds losing users before the first screen. Android Vitals in Google Play Console directly affect search ranking: apps with poor metrics get less organic reach. Apple similarly monitors crash rate and launch time via MetricKit. Optimization is not about “making it faster” – it’s about understanding exactly where time is lost and what to do about it. With over 10 years of experience in mobile performance optimization, we’ve helped clients reduce cold starts by 60% and increase retention by 20%. Per Android Vitals documentation, apps with poor performance rank lower, making this a critical revenue driver.

How to Profile Mobile App Performance?

Cold Start: Where Time Is Killed Before the First Frame

Cold start — launching the app when the process is not in memory. On Android, this is the time from tapping the icon to Activity.onWindowFocusChanged(hasFocus = true). On iOS, from tap to viewDidAppear of the first screen.

Android: Main Thread Overloaded During Initialization

Application.onCreate() — the main enemy of fast start on Android. Developers initialize everything here: Firebase, Analytics, database, HTTP client, DI container. Each SDK adds 20–200 ms on the main thread.

Diagnostic tool: Android Studio Profiler → App Startup. Shows the initialization graph with time for each component. Alternative: Tracing.beginSection(“MyInitTag”) in code + systrace.

Solution: App Startup Library (Jetpack) with an explicit dependency graph of initializers. Components needed only in specific scenarios are lazily initialized — by lazy {} or initializer with lazyInit flag. Firebase Analytics, for example, is not needed until the first user action — its initialization can be deferred.

ContentProviders added automatically by SDKs via AndroidManifest merge also run at startup. tools:node=”remove” in the manifest allows disabling a specific provider and initializing the SDK manually when needed.

Another pitfall: Room.databaseBuilder().build() on the main thread. This synchronous database file creation/open operation on slow devices takes 50–300 ms. Move it to a coroutine with Dispatchers.IO, in ViewModel via viewModelScope.launch.

iOS: Dyld Linking and +load

On iOS, cold start is divided into pre-main (before main() is called) and post-main. Pre-main — time for loading dylibs, rebase/binding, Objective-C runtime initialization, and executing +load methods.

Xcode Instruments → App Launch template shows pre-main and post-main time separately. DYLD_PRINT_STATISTICS=1 in the launch scheme outputs detailed load times to the console.

Factors killing pre-main:

• Many dynamic libraries (each dylib adds linking overhead). CocoaPods adds a separate dylib per pod. Solution: Swift Package Manager with static linking (type: .static) or use_frameworks! :linkage => :static in CocoaPods. Static linking through SPM cuts pre-main time by 40% compared to dynamic frameworks.
• +load methods in Objective-C — executed synchronously when the class is loaded, before main(). Third-party SDKs may abuse this. +initialize — lazy alternative, called on first access to the class.

Post-main — application(_:didFinishLaunchingWithOptions:). Same story as on Android: synchronous initialization of everything. Use lazy var for services not needed immediately. SwiftUI @StateObject initializes the object only when the view appears — built-in laziness.

Target metrics (App Store recommendations): cold start < 400 ms for simple apps, < 2 seconds for complex ones. Warm start (process in memory, but Activity/Scene is recreated) — < 1 second. After optimization, we typically see cold start drop from 3.2s to 1.1s on mid-range devices.

Memory: Leaks, OOM, Excessive Pressure

Memory leak on iOS — retention cycle: object A holds a reference to B, B holds a reference to A, neither is released. Classic: Timer with self in closure without [weak self]. Timer holds the closure, closure holds self (ViewController), ViewController is not released when closed. Instruments → Leaks finds alive objects that should not be there.

On Android, garbage collector manages memory, but leaks still happen. Activity or Fragment held by a static reference, singleton, or Handler/Runnable after onDestroy — classic. LeakCanary is mandatory in debug builds. Add one dependency debugImplementation “com.squareup.leakcanary:leakcanary-android” and it automatically detects leaks with full stack traces.

OutOfMemoryError is most often due to image loading. Bitmap in memory occupies width × height × 4 bytes. An image 4000×3000 px — 48 MB in memory, regardless of file size on disk. Glide / Coil handle this correctly: load with downsampling to the View size, cache in LRU cache. Loading into ImageView without Glide/Coil via BitmapFactory.decodeFile is a path to OOM on devices with 2 GB RAM. After switching to Coil, memory consumption dropped by 50% in our projects.

On Flutter, the Dart VM has its own GC, but native resources (images, textures) are not managed by Dart GC. Image.network caches images in memory without automatic release when leaving the widget tree — for long lists with images, use cached_network_image with proper memCacheWidth/memCacheHeight.

Why Does Cold Start Take So Long? Common Causes

What Profiling Tools Are Essential for Mobile Performance?

FPS and UI Performance

60 FPS — 16.67 ms per frame. 120 FPS (ProMotion) — 8.33 ms. Anything taking longer on the main thread causes jank.

Typical causes of FPS drops:

On iOS: synchronous image decoding in cellForRowAt. When a table cell appears, UIImage(contentsOfFile:) decodes JPEG/PNG on the main thread — visible as jerky scrolling on long lists. Solution: UIImage.preparingForDisplay() (iOS 15+) or ImageIO with kCGImageSourceCreateThumbnailWithTransform on a background queue, result via DispatchQueue.main.async.

On Android: RecyclerView.Adapter.onBindViewHolder with synchronous operations. Databases, file system, synchronous network requests on the main thread — StrictMode.ThreadPolicy with detectAll().penaltyLog() in debug builds will show all violations.

On Flutter: build() method is called frequently; it must be cheap. setState() on a top-level widget rebuilds the entire tree. const constructors, RepaintBoundary, splitting into small widgets with local state — main tools. Flutter DevTools → Performance shows janky frames (red) with causes.

Compose profiling: Recomposition Highlighter and tracing via Trace.beginSection in @Composable. Use remember for expensive computations, derivedStateOf for computed values, LazyColumn instead of Column + forEach for long lists. Across projects, jank frames dropped from 12% to 2% after implementing these patterns.

Battery: Wake Locks, WorkManager, Network Requests

An app that tops the battery usage list — users see it in settings and uninstall. Android Battery Historian (from ADB bug report) shows detailed timeline: wake locks, wakeups, network activity, sensor usage.

Main energy consumers:

• Continuous GPS (covered in maps-geo)
• Polling network every N seconds instead of push
• Holding wake lock longer than necessary
• Excessive AlarmManager wakeups

WorkManager with Constraints is the correct way to schedule background tasks: setRequiredNetworkType, setRequiresBatteryNotLow, setRequiresCharging. The OS batches tasks and executes them at convenient times.

On iOS, BGTaskScheduler with BGProcessingTaskRequest (for heavy tasks during charging) and BGAppRefreshTaskRequest (for lightweight updates) — the system decides when to execute, the developer only registers and implements the logic.

Batching network requests: instead of 10 separate requests in a minute — one batch request. Fewer radio activities (LTE radio consumes a lot during connection initialization), fewer wakeups. This typically cuts battery usage by 30% in network-heavy apps.

How We Optimize Your Mobile App Performance: Step by Step

Optimization Process

1. Measure – Profile cold start, memory, FPS, battery using the tools above. Obtain baseline numbers (e.g., cold start 3.2s, memory footprint 180 MB, 12% jank frames).
2. Analyze – Identify top 3 bottlenecks by impact. For a typical e‑commerce app, image loading and SDK init are priority.
3. Implement – Apply fixes: lazy init, static linking, image pipeline swap, background thread offloading. We deliver code changes with diff reports.
4. Test – Profile again; compare before/after numbers. Validate on real devices (including low-end).
5. Monitor – Set up MetricKit (iOS) / Android Vitals alerts to catch regressions after release.

Deliverables:

• Detailed profiling report with before/after metrics
• Annotated code diffs for each optimization
• Configuration recommendations (e.g., ProGuard rules, build settings)
• Monitoring setup (Firebase Performance, Crashlytics alerts)
• Knowledge transfer session for your team

Estimated Timeline

Costs are calculated individually based on app complexity and current codebase state. Contact us for a project estimate and performance review.

Profiling Tools Reference

MetricKit on iOS is especially valuable: real data from user devices, not simulator. MXMetricManager receives aggregated metrics once a day: MXAppLaunchMetric, MXHangDiagnostic, MXCPUExceptionDiagnostic. Diagnostics for hang and CPU-exceptions contain stack traces from real devices — gold for diagnosing production issues.

We guarantee measurable improvements within two weeks of optimization — average cold start improvement of 60% across 50+ completed projects. Get in touch for a tailored performance review.