July 4, 2026 · Joaquim
Making a website feel expensive (without making it slow)
I spent today polishing this site until it felt like a five-figure build. The surprise: the expensive feeling comes from restraint, about three kilobytes of it.
I sell websites, which means this site is my storefront. Today I gave it the same treatment I give client sites: I wanted it to feel like a five-figure build from the moment it loads. What I learned along the way surprised me enough to write down.
My first instinct was to add more. There are component marketplaces full of spectacular things: spinning three-dimensional robots, particle storms, scenes that follow your mouse around like an eager puppy. I almost grabbed one. Then I checked what it would cost the site: one to two megabytes of JavaScript before a single word of text shows up. On a phone with average signal, that is seconds of staring at nothing.
That is the trap. The things that look premium in a demo are usually the things that make a site slow, and slow is the least premium feeling on the internet. Nobody has ever admired a loading spinner.
Where the expensive feeling actually comes from
Watch a high-end site closely and you will notice the luxury is in small movements. Content rises gently into place as you scroll. Cards lift a few pixels when your cursor touches them. A button catches the light when you hover. Nothing shouts. Everything responds.
So that is what I built. This site now has scroll reveals, a staggered entrance on the headline, cards that lift with a soft glow, a sweep of light across the buttons, and on desktop an ambient glow that quietly follows your cursor. The total cost of all of it is about three kilobytes. The three-dimensional robot would have cost five hundred times more.
The rules I followed
Three rules kept this honest. First, the headline never fades in, because Google measures how quickly the biggest thing on screen appears (they call it Largest Contentful Paint, or LCP), and a fade-in delays that number. The headline moves, but it never hides. Second, anyone who tells their device they prefer reduced motion gets a perfectly still page; every animation simply switches off. Third, if JavaScript fails to load, every word is still visible. Decoration should never hold the content hostage.
Proof, not promises
The homepage also has a new section I am a little proud of. It shows this site's actual Google PageSpeed scores, pulled from a real audit, with a link so you can run the test yourself while you are reading. I wrote the code so the section refuses to render made-up numbers. If there is no real audit saved, it shows nothing at all.
Every client site gets this same treatment. The expensive feeling costs a few kilobytes and some restraint, and speed never has to pay for it.