0 views collected around this technical thread.
This article traces the evolution from HTTP/1.1 to HTTP/3, explains QUIC's design and its advantages over TCP, and examines how features like connection migration, head‑of‑line blocking elimination, congestion control, and flow control improve latency and reliability for modern web applications.
This article explains how to configure Nginx for high‑performance static websites by setting up proper caching, gzip compression, cross‑origin resource sharing and anti‑hotlinking rules, and also includes a brief promotional segment for AI‑related products and services.
This article examines video preloading techniques for web pages, comparing the HTML5 video element's preload attribute with Media Source Extensions (MSE) chunked streaming, detailing their configurations, loading processes, implementation steps, advantages, drawbacks, and best-use scenarios to improve playback experience.
During performance tuning of Alibaba.com’s PC new‑user homepage, the Time To First Byte became acceptable while the First Contentful Paint remained 3 seconds slower, revealing that CSS download and parsing blocked rendering and that inlining critical CSS dramatically reduced FCP latency.
This article explains how to use Service Workers to apply a Stale‑While‑Revalidate caching strategy, detailing the three‑step process, essential APIs, code examples for intercepting and cloning responses, and a complete Express‑based demo to improve first‑visit page performance.
This guide explains how to install Locust, write a Python test script, launch the tool, configure load parameters, analyze real‑time results, and explore advanced features such as custom clients and distributed testing for web performance evaluation.
Despite long‑standing criticism that PHP is outdated, slow, and cumbersome, the article explains why the language still matters and how FrankenPHP—a Go‑based server—injects modern performance, deployment simplicity, and future‑ready features to revitalize PHP for contemporary web development.
This article explains how a motion‑effects platform decouples design and development by automatically converting sequence‑frame animations into multiple formats (APNG, WEBP, AVIF, video), provides a runtime that dynamically selects the optimal format, and offers batch conversion APIs to improve performance and reduce engineering overhead.
A 2024 analysis by Nikita Prokopov of uncompressed JavaScript file sizes across a range of popular websites shows sizes varying from a tiny 0.1 MB for jQuery to over 12 MB for heavyweight platforms like YouTube and Booking.com, highlighting the diversity of front‑end payloads.
This article explains how to configure Nginx for static sites by setting up caching policies, gzip compression, cross‑origin resource sharing, and anti‑hotlinking rules, while also providing practical code examples and discussing the underlying HTTP cache mechanisms.
After initially adopting Tailwind CSS for rapid UI development in a React real‑time chat app, our team reverted to SASS combined with CSS Modules because the growing utility‑class markup hurt readability, increased build times, and bloated the CSS bundle, ultimately delivering a more maintainable codebase and noticeably better performance.
This article explains how to configure Nginx for high‑performance static sites by setting up proper caching rules, enabling gzip compression, handling cross‑origin requests, and preventing hotlinking, complete with practical code examples and detailed workflow analysis.
This comprehensive guide explains how to identify and resolve slow web page performance by addressing hardware resources, network configuration, and both front‑end and back‑end optimizations such as server upgrades, CDN usage, HTTP/2, image compression, code minification, caching, and efficient database queries.
Airbnb tracks five real‑user performance metrics—Time To First Contentful Paint, Time To First Meaningful Paint, First Input Delay, Total Blocking Time, and Cumulative Layout Shift—using a mix of browser APIs and custom polyfills, combines them into a weighted Page Performance Score, and leverages that score to guide trade‑off decisions and detect regressions.
Airbnb created the Page Performance Score (PPS), a unified 0‑100 metric that aggregates platform‑specific initial‑load and post‑load user‑centric measurements for Web, iOS, and Android, using weighted curves to enable cross‑page, cross‑team comparisons, track organizational weighted averages, and evolve with new metrics while preserving a stable scale.
This article explores critical latency metrics—from nanosecond-level CPU operations to intercontinental network delays—illustrating how each contributes to web performance, and provides real‑world measurements for various connection types, data processing tasks, and user‑perceived response times to help developers optimize user experience.
This article explains the fundamentals of HTTP caching, including how it works, the different cache types, key cache-control directives, and the testing scenarios where testers must be aware of cache behavior to ensure performance, data consistency, and security.
This article explains why Lighthouse removed the Time to Interactive (TTI) metric after version 10, describes how TTI was calculated, discusses its inaccuracies, and introduces the more reliable replacement metrics such as Total Blocking Time (TBT), First Input Delay (FID) and Interaction to Next Paint (INP) for assessing web performance.
This article explains how Content Delivery Networks (CDNs) address internet performance challenges by bringing content closer to users, detailing their working principles, key components such as GSLB and caching, and common application scenarios like website acceleration, file download, and streaming.
To address fragmented TV OS versions, low‑end hardware, and SDK fragmentation, the Kiwi App team defined unified performance metrics and applied optimizations—resource merging, server‑side rendering, offline caching, HTTP/2 networking, parallel loading, WebView pre‑heating, and page pre‑rendering—cutting average H5 load time from over five seconds to about two seconds and increasing conversion and payment success rates, with plans to keep loads under two seconds.