Speed
The page is finished before anyone asks for it.
Publishing builds each page and keeps it ready on a nearby server. A cached page measured about 180 milliseconds through the real edge.
Ready to serve
Changes publish in seconds
Traffic is included
What happens when someone visits
Published once, then kept ready.
A nearby server answers
The finished page is already on a server close to the visitor. A cached page measured about 180 milliseconds through the real edge.
A changed page is refreshed
Publishing refreshes what changed and keeps the result ready. The next visitor gets the new version, and that same finished page serves everyone after them.
And it stays that way
It is refreshed only when you publish something that changes it. A page you leave alone stays ready without being rebuilt on every visit.
Why most site builders are not like this
Building every page on demand adds work to every visit.
Every WordPress site eventually needs a speed plugin because most builders assemble the page fresh on every visit. MightyBuilder pages are already built.
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.
- The serving setup works automatically on every site.
- Everyone gets the same page you looked at.
The rest of the page weight
Images account for most of a small site’s page weight.
On most 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 to 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.
Stable image layout
The space a picture will fill is held before it arrives, so text does not shuffle down the page while things load. That shuffle is what makes you tap the wrong link on a phone.
Performance questions
Why is it fast?
Publishing builds the page once. After that, visitors receive the finished page from a nearby server without waiting for it to be assembled.
Is there a build step or a deploy queue?
No. Press Publish and the changed pages go live. Publishing follows the size of the change, so a two-hundred-page site can publish one edit as quickly as a two-page site.
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. Page delivery, caching and responsive images are built into MightyBuilder and work automatically.
What about Core Web Vitals?
Core Web Vitals is Google’s name for a handful of speed measurements it uses when ranking. Fast delivery, responsive images and stable image layouts are handled automatically, and the AI builds with the weight of the finished page in mind.
Does a busy day cost me more?
No. Serving pages never costs credits and there are no usage-based traffic charges. On Pro, a busy month costs exactly what a quiet one does.