Performance is usually treated as a clean-up task at the end of a project. In my experience it is a design decision that has to be made at the start, alongside typography and layout.
On a 3D-driven web project I worked on, treating load time as part of the brief brought it down by 45%. The gains did not come from one clever trick. They came from asking, for every asset and every script, what it was buying the visitor.
Habits that help
- Budget first. Decide what the page may weigh before building it.
- Load what is visible. Defer everything that is below the fold or behind an interaction.
- Pause what is off-screen. Animation and 3D should stop when nobody can see them.
- Respect the device. Small screens and reduced-motion settings get a lighter experience, not a broken one.
Measure, then argue
Opinions about speed are cheap. Lighthouse runs, real-device testing and a before-and-after number settle most debates. I will write up the process in more detail in a longer article.
Leave a Reply