good evening 👋 · open for projects · --:--
← all notes

your website should load in under a second

A slow website is the most expensive kind of cheap. It looks perfectly fine in a meeting — on your new laptop, on the office wi-fi, with everything already cached. Then a real person opens it on a three-year-old phone with two bars of signal, waits, and leaves before your hero image has even finished loading. Speed is not a vanity metric for developers to brag about. It is money — yours — quietly leaking out the bottom of every page.

what slow actually costs

The numbers are brutal and consistent: a large share of visitors abandon a page that takes more than about three seconds, and the drop-off gets steeper with every second after that. Google has used speed as a ranking signal for years, so a slow site is also a less findable one. And if there is a checkout involved, every stutter between "add to cart" and "paid" is a chance for the sale to evaporate. Slow doesn't just annoy people; it sends them, and their money, elsewhere — usually to a competitor whose page was ready when theirs wasn't.

"but it's fast for me"

This is the trap almost everyone falls into. You test your own site on the best possible device and the best possible connection, and it flies. Your customers are not on your setup. They are on mid-range phones, on patchy mobile data, on the train. If you only ever judge speed from your desk, you are grading the one exam your visitors never sit. The version that matters is the one a stranger gets on a Tuesday with half a signal.

how to actually check yours

You can measure this yourself in five minutes. Run your URL through Google's PageSpeed Insights or the Lighthouse tab built into Chrome — both give you a mobile score and, more usefully, a list of what is slowing you down. Then do the honest test: open the site on your own phone, off wi-fi, and count the seconds out loud until you can use it. If you reach "four", your visitors reached "goodbye". Tools give you the diagnosis; your thumb gives you the truth.

what actually makes a site slow

  • Huge, unoptimised images. The number one culprit, by a mile.
  • A pile of plugins, scripts and trackers, each adding weight — far more common on a plugin-heavy WordPress site that nobody has pruned in a while.
  • Fonts and third-party embeds that block the page from drawing anything at all.
  • No caching and no CDN, so every visitor fetches everything from scratch, from far away.

what makes it fast

  • Right-sized images in modern formats — usually the single biggest win available.
  • Shipping less: fewer scripts, and only the code a given page actually needs.
  • Caching hard and serving from a CDN, so the site comes from somewhere near the visitor.
  • Measuring on real devices and real networks, not just your laptop.

fast and beautiful aren't enemies

There is a stubborn myth that a striking, animated site has to be a heavy one — that you choose between looking good and loading fast. You don't. A page can be full of personality and still be light, if the weight goes into craft instead of clutter: clean code, images at the right size, animation that runs on the browser's own muscle rather than a stack of libraries. This site is the proof — it waves, springs and plays, and it still loads quickly. Heaviness is a symptom of carelessness, not of ambition.

fast is also findable

Here is the bonus: a fast page is one a crawler — and an AI answer engine — can load, read and quote. If a bot times out before your page renders, it simply isn't in the answer. Speed and being found are not two projects. They are the same one.

Under a second is not a luxury; it is the baseline we build to. Your visitors will never thank you for it — they will just quietly stay. 👋

like how we think?

[email protected]
hand-coded in spain 👋