Prioritize improvements using measurements.
- measurement
- asset budget
- image format decisions
- font cost
- layout stability
Record before-and-after measurements for a page and explain each change.
- Open the result in a browser and inspect the HTML and computed CSS.
- Test at narrow and wide widths and use the keyboard for interactive elements.
- Write down one thing you changed after testing.
A performance audit compares a baseline to measured results. Inspect resource sizes and loading order, then target the dominant cost: images, fonts, CSS, or layout instability. Use consistent test conditions and note whether the change helps the user's main task. A smaller file is not automatically a better experience if it delays visible content or reduces readability.
Optimizing every tiny asset before measuring can waste effort. A single lab score is not a complete account of real usage.
Measure a page, choose the largest practical bottleneck, make one change, and write a short before-and-after report with the test conditions.
- Rebuild the core idea without copying the example line by line.
- Explain the key HTML or CSS choice in your own words.
- Test the result at a narrow width and with keyboard navigation where relevant.
Open example.html in a browser. Edit style.css, save, and refresh.
Try: Measure load and layout stability, then explain one useful optimization.