How Your Website Updates
Why a change takes about a minute to appear on your live site, and why that wait is what makes your site load fast.
Dashboard only
You publish a change, open your site, and it still looks the same. Refresh a minute later and there it is. That pause is deliberate, and it’s the same thing that makes your site fast.
Your site is built in advance
Most websites are assembled fresh for every visitor: someone opens a page, a server builds it on the spot. Flexible, but slow, and slower the more people arrive at once.
Lekro works the other way. Your site is built ahead of time into finished pages, stored on servers around the world. When a customer visits, there’s nothing to assemble; the page is already sitting near them, ready to send. That’s why your menu opens instantly whether the visitor is across town or across an ocean, and why a rush of traffic doesn’t slow it down.
Which is why changes take a moment
The trade-off is what you notice. Because the live site is a finished stored copy rather than something rebuilt per view, publishing has to build a fresh copy of the affected pages and distribute it across that network to replace the old one.
That runs automatically and usually settles within about a minute. When you publish and the site looks unchanged, nothing has gone wrong. The new version is in transit.
Three habits that make it a non-issue
- Judge your work in the Design Studio preview, not on the live site. The preview shows your draft instantly with no wait. The live site is only for confirming the final result.
- Wait a beat before checking. Refreshing the instant you publish often catches the old version mid-swap.
- Hard refresh if it lingers. Your own browser also keeps a short-term copy. If a change still isn’t showing after a couple of minutes, hold Shift while reloading to fetch the newest version.
That last one matters more than it sounds: most reports of “my change didn’t publish” turn out to be the browser showing its own cached copy, not a problem with the site.
Nothing to manage
There are no caches to clear and no rebuild button to press. Publish the change, give it a minute, and the site updates itself.
If a change genuinely hasn’t appeared after several minutes and a hard refresh, that’s worth raising with support rather than republishing repeatedly: publishing again rebuilds the same content and won’t resolve it.