Establish what is happening
Record device, network, and workflow
Write down device class, operating system version, viewport, battery or power state when relevant, connection type, signal conditions, route, account shape, and exact actions. Measure tap or navigation start, request boundaries, first useful content, and completion. Keep privacy-sensitive identifiers out of the trace.
Compare mobile and desktop timelines
Align client timing, request waterfall, server duration, response bytes, parsing, image decode, and interactive readiness for the same workflow. Mark intervals present only on mobile. A slower device and a slower network can compound, so preserve each measured boundary instead of calling the total device latency.
Repeat on a weaker and stronger connection
Use a controlled slower profile and a normal mobile profile with the same device and input. Compare request count, connection reuse where observable, payload size, retries, and rendering. If the delay changes sharply with connection quality, keep server and client work separate from transfer evidence.
What to carry forward
Return a mobile scope statement naming the device and network conditions, blocked action, first divergent interval, and comparison case. Route the next work to server, transfer, client computation, or an unresolved combination. Stop when the evidence says what must be measured next without generalizing from one phone.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow