A fast site is a decision you make in the project.
How to keep complexity down before it becomes a loading problem.
Redazione SYSTEM ·
Content before interaction
Headings, text and navigation can arrive as HTML. The visitor has to be able to understand the offer even when a script does not load. Interaction adds a possibility, without becoming a prerequisite for reading.
Every script has a cost
Before introducing a library, define which behaviour it is for. An accordion can use native elements. A complex visualisation can justify a dedicated script. Weigh the feature in the context of the whole page.
The right image, at the right size
Define dimensions and proportions to avoid layout shifts. Provide suitable formats and resolutions. Load early what the first screen needs and defer assets below the fold when possible.
Movement has to have an alternative
A sequence must not hide essential information. Consider the keyboard, small screens and the preference for reduced motion. Animating transforms and opacity can reduce layout work, but it does not remove the cost of a complex scene.
Check on real journeys
Measure loading and interactions on mobile, with representative network and hardware. A successful build verifies the packaging, it does not demonstrate perceived performance. Use the data to identify the constraint before adding optimisations.