cerise.

Why this page shows up in the blink of an eye

A cerise post is prepared once, when you save it. After that, it opens in an instant.

By Luke SidneyOct 16, 20261 min readSite speedToolsEn français

A woman runs a jade roller under her eye

Your client opens your site between two metro stops, on a three-year-old phone. If the page is slow, she does not read it. She will never tell you: she will just close the tab.

cerise is built so that moment never comes. Here is how, without the jargon.

The work happens once, not on every visit

Most sites rebuild the page for every visitor: they reread the text, format it, assemble the pieces, then send it. A hundred visits, a hundred times the same work.

cerise does that work once, when you press Save. The text is formatted, checked, cleaned, then stored ready to serve. When a client arrives, the page is already made: it comes out of the drawer and goes straight to her.

Nothing useless in the page

A cerise post loads no scripts. No ad tracker, no chat window, no banner that animates. Fonts and images come from the site itself, not from five different servers. What reaches the phone is your text, its layout and its images, nothing else.

What about the numbers?

You may see load times in milliseconds on this site. Each one is measured, with the date and the method written next to it. A number nobody measured is not shown. That is a house rule.

What it changes for you

Nothing to tune, nothing to optimise. You write, you save, and the page is fast because it was designed to be. Your only job is the text.

Your turn

Try it on this post

Open this post in the editor, change a sentence, publish. Everything works, nothing is kept.

Next post

Writing

One photo, one caption

A picture without a caption is a shop window without a label. The Figure component keeps them together.

Oct 12, 2026 · 1 min read

More to read

← All posts
View the raw textHide the raw text

This is the text as it was typed. The page is built from it when it is saved.

Your client opens your site between two metro stops, on a three-year-old phone. If the page is
slow, she does not read it. She will never tell you: she will just close the tab.

cerise is built so that moment never comes. Here is how, without the jargon.

## The work happens once, not on every visit

Most sites rebuild the page for every visitor: they reread the text, format it, assemble the
pieces, then send it. A hundred visits, a hundred times the same work.

cerise does that work **once**, when you press Save. The text is formatted, checked, cleaned, then
stored ready to serve. When a client arrives, the page is already made: it comes out of the
drawer and goes straight to her.

## Nothing useless in the page

A cerise post loads no scripts. No ad tracker, no chat window, no banner that animates. Fonts and
images come from the site itself, not from five different servers. What reaches the phone is your
text, its layout and its images, nothing else.

<Callout type="note">
This blog does not measure your visits and sets no advertising cookie. It has nothing to ask you
before you read.
</Callout>

## What about the numbers?

You may see load times in milliseconds on this site. Each one is measured, with the date and the
method written next to it. A number nobody measured is not shown. That is a house rule.

## What it changes for you

Nothing to tune, nothing to optimise. You write, you save, and the page is fast because it was
designed to be. Your only job is the text.