Alois Reitbauer interviewed at Velocity 2012
summary
Problems center on third‑party content like CDNs social widgets and ads and on measuring when users actually see content not just full load times. Browsers partially implement navigation timing while Safari and legacy browsers lack it so teams use polyfills and JavaScript hooks. Claims: resource timing data that native APIs promise in about 1–1.5 years can be approximated today, and JavaScript instrumentation (DOM hooks and framework-specific hooks) measures render and event execution times. A combined browser server and synthetic approach is required.
AI-written summary · about
