Speed
The page is finished before anyone asks for it.
Your pages are built the moment you publish, not the moment somebody visits. A visitor is handed the finished page from a server near them — there is nothing left to work out. About 180 milliseconds, measured rather than promised.
Nothing to work out
The page already exists. Nobody’s server has to assemble it while your visitor waits.
No waiting to publish
Press Publish and it is out. A two-hundred-page site goes live as fast as a two-page one.
No traffic bill
Serving is not metered. A hundred thousand visitors cost the same as none.
What happens when someone visits
Three steps, and two of them usually do not run.
A nearby server answers
That is the whole story for almost every visitor: the finished page is already sitting on a server close to them and it is simply handed over, in about 180 milliseconds. Neither of the steps below happens.
Or it is put together, once
The very first visit after you publish a change has nothing waiting, so the page is assembled and then kept. About 2.3 seconds, for one person, one time. Everybody after them is back on step one.
And it stays that way
It is only rebuilt when you publish something that actually changes it. Nothing throws it away on a timer, so a page you have not touched in a year has been instant for a year.
Why most site builders are not like this
Building the page on every visit is normal. It is also the slow way.
Most site platforms put the page together fresh every single time somebody asks for it — look up the content, apply the theme, assemble the page, send it. That is why “speed plugins” are an industry, and why every WordPress site eventually has one.
Assembled on every visit
- The same work, repeated for every single visitor.
- A busy day is a problem, and sometimes a bill.
- Speed becomes a plugin, then a plugin that fights another plugin.
- You never notice, because your own visits are always the fast ones.
Built when you publish
- The work happens once, when you press Publish.
- A busy day is the same page being handed out more often.
- There is nothing to configure, because this is simply how it works.
- Everyone gets the same page you looked at.
The rest of the page weight
Pictures are usually the problem, so they are handled.
On most small business sites the images are ninety per cent of the bytes. Getting that wrong costs more than every other performance decision combined, and it is exactly the part nobody wants to do by hand.
The smallest one that works
Every picture is offered in newer formats as well as familiar ones — measured at 34–44% smaller for the same quality. Each visitor’s browser quietly takes the best version it understands, and older ones still get a picture.
The right size for the screen
A phone is sent a phone-sized picture and a large monitor a large one — and never a size bigger than the original really is, which is the common mistake that downloads more and looks worse.
Nothing jumps about
The space a picture will fill is held before it arrives, so text does not shuffle down the page while things load — the thing that makes you tap the wrong link on a phone.
Performance questions
Why is it fast?
Because the page is already built. Publishing does the work once; after that a visitor is simply handed the finished page from a server near them. There is nothing to look up and nothing to assemble, so there is very little left that could be slow.
Is there a build step or a deploy queue?
No. Press Publish and it is out. Nothing rebuilds the whole site and nothing queues up behind anybody else — a site with two hundred pages publishes as quickly as one with two, because the work follows what you changed rather than how big the site is.
How long does a change take to go live?
Seconds. The pages that actually changed are refreshed as part of publishing, and the first visitor to each of them gets the new version, which is then kept for everybody after them.
Do I need a CDN, a caching plugin or an image optimiser?
No, and there is nowhere to install one. All of it is simply how the product serves pages — not an add-on, not a higher tier, and not something you have to switch on.
What about Core Web Vitals?
Core Web Vitals is Google’s name for a handful of speed measurements it uses when ranking. The half decided by how a page is delivered is handled for you. The half decided by what is on the page — how heavy your pictures are, how much is crammed in — is still yours, though the AI is careful about it by default.
Does a busy day cost me more?
No. Serving pages is not metered — there is no bandwidth charge and no request charge. Credits pay for AI editing and for keeping the site online, and a hundred thousand visitors cost exactly what none do.