Measure, then fix. Almost every real win is fewer bytes, fewer round trips, or less main-thread work.
6 articles
Listed inCore Web VitalsPerformanceon
Why Interaction to Next Paint punishes long tasks rather than slow servers, how to find the blocking work in a trace, and the four fixes that move the number.
Listed inCore Web VitalsPerformanceon
The reference definition: what counts as an interaction, how the score is computed from the worst ones, and the thresholds.
Listed inUsing DevToolsPerformanceon
Performance traces, the network waterfall, coverage, and memory snapshots — where the answers are.
Listed inLighthousePerformanceon
Lab audits, how they differ from field data, and reading a report without chasing the score.
Listed inCore Web VitalsPerformanceon
LCP, INP, and CLS — what each one measures, and the fix that usually moves it.
Listed inPerformancePerformanceon
The critical rendering path, the cost of JavaScript, and the budget that keeps a page from regressing.