Aman Nadeem· 3 min read
Deliver the content with the page
A portfolio visitor should be able to read your work without waiting for a client application to boot. Server-rendered HTML gives the browser the headings, links and content in the first response.
Interactive elements still have a place. A small navigation enhancement is useful; shipping a full application runtime for static paragraphs usually adds work without helping the reader.
Give images a budget
Choose an image size that matches its rendered role. A small portrait does not need a multi-megapixel source. Generate a modern format, retain a practical fallback and declare width and height to reserve the right space.
Load below-the-fold media lazily. Give priority only to the image that actually matters for the initial view; marking every image as urgent defeats the purpose.
Measure the experience, not a promise
Largest Contentful Paint describes how quickly the main content appears. Interaction to Next Paint captures responsiveness to user input. Cumulative Layout Shift measures unexpected visual movement.
Local checks can identify regressions, but they do not establish what real visitors experience. Evaluate the deployed site on mobile connections and use field data when enough traffic is available.
Keep improvements maintainable
Shared metadata, predictable asset paths and a small rendering layer make it easier to preserve performance as new pages arrive. Every new widget should justify its network and execution cost.
Performance is an ongoing constraint on the design, not a score to claim before the site is live.