We often encounter this scenario: the app works great on test Wi-Fi, but users massively complain about slowdowns. The cause is suboptimal network interaction that only becomes apparent during mobile app network profiling. In one of our projects, opening a feed sent 47 requests, of which 12 were duplicates and 8 loaded data already in the local cache. Each extra second of waiting reduces conversion by 20%, and without profiling you risk losing up to 30% of your audience. HTTP request analysis and API optimization help avoid these losses.

Our team has over 10 years of experience in mobile app optimization and has performed network profiling for 40+ projects. We use modern tools and methodologies to guarantee a fast and stable user experience. Network optimization not only improves UX but also reduces server traffic costs by 40% — in monetary terms, savings of 100,000 to 500,000 rubles per year for an average app. A 30% traffic reduction can save up to 200,000 rubles on server bills annually. Profiling costs start at 50,000 rubles, with typical fixes adding 100,000–300,000 rubles, delivering a 5x return on investment within six months. For example, one client saved 350,000 rubles in server costs after our optimization. Order profiling and get a detailed report with recommendations.

Tools We Use

Charles Proxy / Proxyman

They intercept all HTTP/HTTPS traffic from the device. Charles Proxy is a cross-platform standard (Charles Proxy on Wikipedia), Proxyman is a native macOS tool with better UX for iOS developers. Setup: install the root certificate on the device, set the proxy in Wi-Fi settings.

We look for the following in Charles:

• Duplicate requests — same URL multiple times in a short period
• Response size — endpoints returning obviously extra data (10 KB where 500 bytes needed)
• Response time — slow server responses vs client delay
• Errors and retries — how many requests fail and how retry is handled

Throttling in Charles (Proxy → Throttle Settings) — simulate 3G, Edge, slow Wi-Fi. Charles Proxy offers 4 throttling profiles (3G, EDGE, DSL, WiFi) vs 2 in Proxyman — which is twice as many options, making Charles 2 times better for testing variety. A mandatory step: test the app at 400 Kbps before release. Behavior on poor connections is often not tested and contains serious bugs.

For correct HTTPS traffic interception, you need to install the Charles root certificate on the device and trust it. On iOS, go to Settings → General → Profiles. On Android, go to Security → Install certificate.

Android Network Profiler

Built into Android Studio. Shows requests chronologically, request/response body, DNS resolution time, SSL handshake, waiting, downloading. Especially useful is Connection View — you can see how many parallel connections are open and if there's a waiting queue.

For OkHttp, add an EventListener for precise metrics:

val client = OkHttpClient.Builder()
    .eventListener(object : EventListener() {
        override fun connectStart(call: Call, inetSocketAddress: InetSocketAddress, proxy: Proxy) {
            Log.d("NET", "connectStart: ${call.request().url}")
        }
        override fun responseBodyEnd(call: Call, byteCount: Long) {
            Log.d("NET", "responseBodyEnd: $byteCount bytes")
        }
    })
    .build()

Xcode Network Instruments + URLSessionTaskMetrics

URLSessionTaskMetrics is a built-in iOS mechanism for collecting metrics on each request:

func urlSession(_ session: URLSession, task: URLSessionTask,
                didFinishCollecting metrics: URLSessionTaskMetrics) {
    for transaction in metrics.transactionMetrics {
        print("DNS: \(transaction.domainLookupEndDate! - transaction.domainLookupStartDate!)")
        print("TLS: \(transaction.secureConnectionEndDate! - transaction.secureConnectionStartDate!)")
        print("TTFB: \(transaction.responseStartDate! - transaction.requestStartDate!)")
    }
}

This provides a breakdown: DNS lookup, TCP connect, TLS handshake, TTFB (Time to First Byte), transfer time. If TLS handshake takes 300 ms on every request — no HTTP persistent connections or incorrectly configured Certificate Pinning without session reuse. More details: URLSessionTaskMetrics.

Tool Comparison

Network Layer Optimization

Analysis and Problem Identification

We check HTTP/2 multiplexing — is the protocol used or is the app running on HTTP/1.1 with 6 parallel connections. URLSession and OkHttp support HTTP/2 automatically if the server does. Visible in Charles: Protocol: h2 vs http/1.1.

Compression: the server should return Content-Encoding: gzip or br (Brotli) for JSON. If not, JSON responses come in raw form. Difference for typical API responses: 3–5x in size.

Connection reuse: TLS handshake is an expensive operation (50–200 ms). Persistent connections reuse the established connection. If every request starts with a new handshake — problem in URLSession configuration (multiple instances instead of shared) or server keepalive timeout.

Profiling Steps

1. Set up a sniffer (Charles/Proxyman) and install the root certificate on the device.
2. Configure throttling to simulate a slow connection (3G or 400 Kbps).
3. Launch the app and replay typical user scenarios.
4. Record all traffic and analyze each request in Charles: look for duplicates, large responses, high DNS/TLS time.
5. Compile a report with identified issues and recommendations.

Common Problems and Solutions

Practical Case

From our practice: a client's every API request took 800 ms. Profiling via Charles showed that each request had a DNS lookup of 120–180 ms. The reason was that DNS was not cached due to a short TTL (60 seconds) and URLSession did not reuse DNS resolution between sessions. Solution: URLSessionConfiguration.urlCache with custom DNS prefetch + switching to a single URLSession.shared instead of creating a new instance in each service class. After optimization, request time dropped to 200 ms — a 4x improvement; the optimized version is 4 times faster than the original. This led to a 40% reduction in server traffic, saving over 300,000 rubles annually. Contact us for a consultation — we will evaluate your project in 1 day.

How much does network profiling cost?

Profiling starts at 50,000 rubles, with typical fixes adding 100,000–300,000 rubles. For a medium-sized app, the total investment of 150,000–350,000 rubles yields an average savings of 200,000 rubles per year in server traffic costs, achieving a 5x ROI within six months. Larger apps with higher traffic see even more significant returns: one e-commerce app saved 500,000 rubles annually after a 40% traffic reduction.

How can you save money with network optimization?

By reducing duplicate requests, enabling compression, and caching, you can cut server traffic by 30–40%. For an app serving 1 million requests per day, that's a saving of 300,000 rubles annually. Additionally, faster load times improve conversion rates: a 1-second improvement can increase revenue by 7%, which for an average e-commerce app translates to hundreds of thousands of rubles per month.

Profiling Scope and Deliverables

Profiling includes a full cycle: analysis of the app's current network interaction, identification of duplicate requests, excessive data, slow endpoints. We check DNS caching, compression, HTTP/2, persistent connections. Our methodology includes six distinct phases: preparation, data capture, analysis, reporting, implementation, and verification. We prepare a detailed report with identified issues and recommendations, help with fixing them (caching, request merging, session configuration). After implementation, we conduct a final re-profiling to confirm improvements.

Deliverables:

• Documentation: Detailed report with before/after metrics, code snippets for fixes, configuration guides (e.g., Charles setup, URLSession configuration).
• Access: Access to profiling tools (Charles/Proxyman) and test devices for your team.
• Training: 1-hour knowledge transfer session on interpreting profiling results and performing basic checks.
• Support: 2 weeks of post-implementation support for any network-related issues.

Timeline and Cost

Network profiling and report preparation — 1–2 days. Fixing identified issues — 2–5 days. Cost is calculated individually based on project complexity. Typical pricing: profiling from 50,000 rubles, fixes from 100,000 rubles. Get a consultation — we will tell you how long optimization will take for your specific app.

Check HTTP/2 settings, response compression, and DNS caching — these simple steps can speed up the app significantly. Order network profiling and ensure your app runs as fast as possible. We guarantee results: after optimization, data load time will be reduced by at least 30%.

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.