Give important content a head start
The first screen should communicate who the developer is and what they build. A long loading sequence or a heavy decorative effect can delay the information a visitor actually came to see.
Prioritize the main portrait when it is visible immediately. Give images known dimensions to reserve their space, and provide appropriate responsive sizes so a narrow device does not need the same image as a large desktop.
Use motion deliberately
A short text entrance or a small transform can add character without making an entire page continuously redraw. Expensive effects deserve a clear purpose and should be measured on devices with less processing power.
CSS illustrations can also avoid additional image requests for decorative project artwork. That does not make them universally better; the right choice depends on the content and the cost of drawing it.
Measure before claiming a score
A successful production build confirms that a site can compile. It does not establish real-world loading speed, responsiveness, or visual stability. Those require measurements in the browser and, ideally, observations from actual visits.
Performance improvements should be described with their evidence. Clear limitations are more useful than a perfect score that has not been measured.