Frontend Development 16 min read

Web Performance Optimization: Metrics, APIs, and Best Practices

This article explains how to collect real‑user performance data with the W3C Performance APIs, defines key metrics such as first paint and TTI, and provides practical loading, caching, rendering, and framework optimization techniques to improve web page speed and user experience.

TAL Education Technology
TAL Education Technology
TAL Education Technology
Web Performance Optimization: Metrics, APIs, and Best Practices

User experience is a crucial part of web products; fast interaction, smooth animations, clear feedback, simple steps, consistency, prominent content, and accessibility are common traits of high‑quality sites. Performance, especially page load speed, often determines these traits.

Performance Collection – Real‑User Monitoring (RUM) uses the W3C Performance API suite (Navigation Timing, Resource Timing, User Timing, Performance Timeline) to gather metrics such as DOM‑ready, onload, white‑screen time, DNS lookup, TCP handshake, request/response phases, and more from actual users.

Performance Optimization

Loading Optimization Reduce resource size: compress HTML/CSS/JS, use tools like TerserPlugin, PostCSS, enable Gzip on the server. Cache resources: HTTP cache, Local Storage, Cache Storage, IndexedDB, CDN. Adjust resource priority: preload, preconnect, prefetch, lazy‑load, Service Worker. Code splitting: use webpack, tree‑shaking, webpack‑bundle‑analyzer. HTTP/2: multiplexing, header compression, Server Push.

Rendering Optimization Critical render path: delay non‑critical CSS, use async/defer. Non‑blocking JavaScript: requestAnimationFrame, requestIdleCallback, Web Workers, passive event listeners. Reduce render‑tree complexity: simplify DOM/CSSOM, avoid layout thrashing, use transform/opacity, will‑change.

Framework Optimization CSR (Client‑Side Rendering) – fast initial load, skeleton screens. SSR (Server‑Side Rendering) – server renders HTML, better first‑paint and TTI. NSR (Native‑Side Rendering) – hybrid offline templates rendered on device. ESR (Edge‑Side Rendering) – leverage CDN edge to stream static then dynamic content.

Benefit Measurement – Compare core metrics (white‑screen, first‑paint, TTI) across experiment and control groups, correlate with PV/UV and revenue, and monitor per‑browser, device, region, and network conditions.

Conclusion – Performance optimization requires a closed‑loop process: planning, execution, and post‑analysis, combined with business scenarios and front‑end‑back‑end collaboration. Continuous iteration and monitoring are essential for sustained gains.

References

Web Performance Optimization Resources – https://naluduo.vip/Web-Performance-Optimization/reference/

User‑Centric Performance Metrics – https://web.dev/i18n/zh/user-centric-performance-metrics/

Analyzing Web Front‑End Performance with window.performance – https://www.cnblogs.com/y896926473/articles/7466951.html

PWA Application Practice – https://lavas-project.github.io/pwa-book/

Detailed Browser Rendering Process – https://www.jianshu.com/p/7659d714a642

Web Caching Explained – https://zhuanlan.zhihu.com/p/90507417

renderingfrontend optimizationweb performanceLoading SpeedPerformance APIs
TAL Education Technology
Written by

TAL Education Technology

TAL Education is a technology-driven education company committed to the mission of 'making education better through love and technology'. The TAL technology team has always been dedicated to educational technology research and innovation. This is the external platform of the TAL technology team, sharing weekly curated technical articles and recruitment information.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.