← Back to blog
Engineering

Why every Deecite site is fast by default

Performance isn’t a toggle you find in settings. It’s the only mode Deecite ships — and a handful of deliberate constraints are what keep it that way.

MO
Maya Okonkwo
May 22, 2026 · 6 min read

When someone publishes a site on Deecite, they’re not thinking about cache headers or image formats. They typed what they wanted, watched it appear, and hit deploy. The fact that the result loads in well under a second on a phone halfway around the world is not luck — it’s the default, and keeping it the default takes work you never see.

The fastest request is the one you never make

Most slow sites are slow because they ask the browser to do too much: dozens of round-trips, megabytes of unused script, fonts that block the first paint. Deecite starts from the opposite premise. Every page ships only what it needs to render, and nothing it doesn’t. There is no general-purpose runtime waiting to wake up — just the markup and styles for the page in front of you.

That restraint is the single biggest lever on performance, and it’s one we get to pull for everyone at once.

Speed isn’t a feature we sell. It’s a property we refuse to give up.

A global edge, by default

Published sites are served from a content delivery network with points of presence close to your visitors, so the first byte arrives quickly no matter where the request comes from. Static assets are fingerprinted and cached aggressively; the HTML is served fresh. You don’t configure any of it — connecting a custom domain is the only step, and even then the certificate is issued automatically.

Constraints that pay off

A few rules, applied everywhere, are what make the defaults hold:

  • Images are resized and re-encoded to modern formats on upload, then served at the size the layout actually uses.
  • Fonts are subset and preloaded so text paints immediately rather than flashing in late.
  • Sites render meaningful content on the first response — there is no blank screen waiting for scripts.
You don’t have to think about any of this

Every point above is on by default and applies to free sites too. There is no performance tab, because there is nothing to turn on.

The goal was never to give people a hundred dials to tune. It was to make the fast path the only path — so that a baker’s first website is just as quick as one built by a team that obsesses over this for a living.

MO
Written by
Maya Okonkwo · Engineering

Maya leads the rendering and infrastructure work at Deecite — the part that turns a finished site into something fast and secure on the open web.

More from the blog

Guides

Bring your own domain in under five minutes

Two DNS records and a verify button. A walkthrough of connecting a custom domain and how automatic SSL works behind the scenes.

May 14, 20264 min read
Product

What we shipped this spring

Custom domains, a faster preview, and a redesigned content tab. A roundup of everything that landed over the last few months.

May 2, 20265 min read
Product

The CMS and the design tool, and why they’re separate

One changes what your site says, the other changes how it looks. Keeping them apart is a feature — here’s the thinking behind the split.

Apr 18, 20265 min read