Count what visitors must download

A page can look simple while loading large images, multiple font files, analytics, and embedded media. List the resources needed for the first useful view. Distinguish necessary content from decoration. An effect that adds little meaning should have a small cost.

Set a project-specific budget for page weight and requests. The number is a decision tool, not a universal standard. For a text-led site, question why a visitor would need several megabytes before reading the opening paragraph.

Optimize the largest costs first

Use images sized for their display purpose and formats appropriate to their content. Give images dimensions so the layout can reserve space. Load offscreen imagery appropriately, while allowing the main visible content to appear promptly. Avoid adding a large dependency for a minor interaction.

System fonts can remove external font requests, although typography still needs careful spacing and sizing. A static site can also be slow if its assets are unnecessarily large. Architecture alone does not replace resource discipline.

Measure conditions that resemble real use

Test a narrow viewport, a slower connection profile, and a direct visit to an article. Inspect layout movement and the time until useful content appears. Record the test conditions so a later measurement can be compared fairly.

Treat a synthetic score as a diagnostic, not a promise about every visitor. When a new feature increases cost, decide whether its value justifies that cost. Performance work becomes easier when it is part of design review rather than a final rescue step.

Further reading

Original sources and related references. These links lead to independent websites; inclusion does not imply a partnership or endorsement.

Browse the complete resource shelf →