Performance is not exclusively a development task. Photographs, video, fonts and external embeds determine how much data a page must load. When these choices happen after design, developers may spend time optimising material that never needed to be included.

Give every image a purpose and a display context. A card does not need the same file as a large hero, and a photograph need not be wider than its intended display area. Prepare suitable dimensions and check visual quality after compression rather than judging file size alone.

Use video when it communicates something an image or text cannot convey equally well. A large background clip can burden initial loading without helping the visitor. A poster image and user-initiated playback are often more appropriate for video that people genuinely need to watch.

Review content loaded from external services as well. Maps, social feeds and tracking tools can introduce many additional requests. Include them where they have a clear function, not simply because the administration interface makes them easy to add to every page.

Content structure also affects visual stability. Reserve space for images, messages and elements that arrive later. Readable copy and a clear layout help visitors begin their task while less important parts of the page are still being prepared, rather than waiting for everything at once.

Editorial guidance should specify image dimensions, video rules and checks for new embeds. Review speed on real content pages, particularly on mobile devices. This helps prevent a well-built website from gradually becoming slower with each new article or campaign update.