Field guide

Keep a content website lightweight

Reduce unnecessary assets, size images carefully, and measure representative pages before claiming performance improvements.

Content updated · Editorial standards

Start with the assets a page actually needs

List stylesheets, scripts, fonts, and images loaded by the homepage and one article. Remove dependencies that provide no visible or functional benefit. A static reading page often needs less JavaScript than its original publishing system. Keep essential content and navigation usable before optional scripts execute.

Size images for the space they occupy

Keep a source copy and export a display version with sufficient detail for its intended use. Compare encoded file size and visible quality rather than assuming a different extension is always smaller. Provide width and height so the browser can reserve space. Load below-the-fold images lazily when that does not interfere with the main content.

Use typography that can load predictably

System fonts avoid a separate font download and keep text available immediately. If the design needs a custom font, use only the styles in use and check the fallback layout. Test long headings and navigation labels with the fallback font because small metric differences can change wrapping.

Measure a visitor route

Measure the homepage, a long article, and a page with a table or interactive control under consistent conditions. Record the tool, device profile, date, and page version with each result. Do not turn a local file preview or a compressed image count into a claim about live Core Web Vitals.

Treat caching as a hosting decision

Confirm compression, MIME types, and cache behavior on the actual server. Version assets before giving them long-lived immutable caching. Keep HTML update behavior compatible with your publication process. A release ZIP can contain optimized files, but it cannot prove that a host serves them efficiently.