APM Page Load Time Calibration: From 0 to 2

This article details the evolution of APM (Application Performance Monitor) page load time calibration in Taobao's Android app. It begins by explaining the background of APM and the concept of "page visible time" - measuring from user click to full page presentation and interaction readiness, rather than technical lifecycle stages.

The article traces the journey from initial "visible calculation" using the 8060 algorithm (80% X-axis, 60% Y-axis coverage) to more sophisticated approaches. Key developments include asynchronous visible calculation for performance, element-based differentiation (treating images, text, and interactive elements differently from background elements), and the introduction of view tagging to mark valid/invalid/ignored elements.

Advanced features covered include setting page-specific load thresholds, custom page root views for complex layouts (like tabbed interfaces), and support for H5/Weex containers through JSTracker integration and UC kernel calculations. The article also addresses multi-container scenarios where different frameworks coexist on a single page.

The calibration process significantly improved accuracy by removing non-essential elements from calculations and focusing on core visual content. The article concludes with team introduction and contact information for the Taobao Android Experience Technology Team.