Build a useful investigation brief
Map the mobile request waterfall
Align tap or navigation time with each request start, response, retry, and content update. Record which requests are serial, which are independent, and which block the first useful action. Compare the same route on a stronger connection to identify transfer and dependency differences.
Measure payload and device work
Capture response sizes, decoded data, script evaluation, image decode, layout, and memory pressure where available. Separate a large transfer from expensive processing after arrival. Check whether mobile receives fields or assets that the first action does not need, while preserving data required for correctness.
Test one wait-reduction experiment
Try one focused change such as combining dependent reads, reducing initial fields, prioritizing the first action, or deferring secondary media. Replay the same device, connection, route, and account state. Confirm loading feedback, cancellation, error recovery, and content order before attributing a shorter wait to success.
What to carry forward
Deliver an evidence-backed mobile brief with the waterfall, first blocking interval, device and connection context, and experiment result. State what remains unmeasured. Investigation is complete when implementation can target one source of waiting and verification can replay the same mobile workflow with a meaningful comparison.
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