Do you have to choose between a flashy website and a fast one?
On this page07 sections
Usually, no. But that does not mean the two come free together. Every impressive element carries a load: files to download, code to run, a second of waiting. The question is not whether to give up on visual ambition. It is which pieces earn the weight they add.
The question is often framed wrongly
“Flashy or fast?” puts the two at opposite ends of one axis. In practice a page can be plain and slow, or striking and fast. The cause of slowness is usually not the ambition of the design but its execution: an image far larger than needed, an unused library loaded on every page, an unoptimised video.
A more useful starting point: does the impressive part of this page actually help the visitor decide, or does it only show off?
How visitors feel speed
Users do not time a second; they feel waiting. When did something meaningful appear? Did the page respond when they tapped? Did content jump while loading? These map onto technical measurements and overlap with the signals Google tracks under Core Web Vitals, but the feeling is what matters most.
Design has a strong tool here: sequencing. If the headline and core message appear first and heavy elements arrive behind them, the page feels usable before it has fully loaded. Speed is sometimes not about making the page smaller but about choosing what comes first.
Where the cost of spectacle gets paid
The usual suspects are familiar: autoplaying background video, large full-screen images, several font families, complex scroll-driven animation, third-party widgets. Each looks harmless alone; together they weigh the page down.
The load is not only download time. When animation libraries keep the browser busy, especially on a mid-range phone, the page responds late to touch. A transition that looks smooth on a designer's powerful machine may stutter elsewhere.
Accessibility belongs in the same discussion. Respecting the system-level “reduce motion” preference for people who are bothered by movement is both courtesy and a technical responsibility.
Where spectacle genuinely earns its place
For a studio, an architecture office or a product launch, the visual experience is part of explaining the work. A striking transition or a large image carries information there: it shows quality, scale and texture. Asking such a site to “keep it simple” can mean telling the story incompletely.
Applying the same approach to a booking page, to someone looking for pricing, or to a person who needs to contact you quickly from a phone works the other way. When the page's job is not clear before the flourish is chosen, decoration can block the path that matters.
A practical method: ask for a reason behind every element
When a heavy element is proposed during design, a simple question helps: what does the page lose without it? If the answer is atmosphere, brand feeling or explaining the product, that can be a real reason. If the answer is “it looks nice”, another solution may be worth finding.
Then look for lighter ways to deliver it: a poster frame instead of a long video, serving the large image at a suitable size and format, starting animation only when it enters the viewport, dropping fonts that are not needed.
This can feel like a constraint, yet it often sharpens the design. A hierarchy built from fewer elements reads better.
Check on a real device before deciding
A site that feels fast on a desktop can behave very differently on a slow mobile connection. Before deciding anything, open the site on a real phone, ideally on a limited connection, and watch when the first meaningful content arrives.
The Core Web Vitals report in Google Search Console highlights problem pages when enough real-user data exists. Tools such as Lighthouse give a one-off lab measurement. They complement each other, but neither replaces what a person actually feels.
Path first, decoration second
Rather than choosing, set an order: the route a visitor wants to take should be clear first, then spectacle that strengthens that route can be added. In a page built that way, impressive elements are not weight; they carry the message.
If you already have a site, the safest step is to find the three heaviest elements and ask for the reason behind each. Some will stay, some will get lighter, some will disappear. The page usually thanks you for it.