Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Every small content change takes ages to appear on my website

Short answer

A site that rebuilds every page on each change gets slower as content grows. The usual remedy is to regenerate only the pages that changed. Next.js documents this as incremental static regeneration, which updates static content without rebuilding the whole site and avoids long builds on large page counts.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I fix a typo and it takes minutes before the live site shows it.
  • Publishing two articles in a row makes the second one wait in a queue.
  • My editors stopped updating the site because it is slow.
  • My developer says builds will keep getting longer as pages are added.
  • The hosting build sometimes times out or fails halfway.

Why does this happen?

  1. Every page is built again, whether it changed or not

    A fully static site produces all pages during one build. With hundreds or thousands of pages, that single build takes time even for a one-word change.

  2. Each page waits for content from the CMS

    During the build, the site fetches content for each page from your content system. Many requests, large images and a slow response add minutes.

  3. The framework may be able to regenerate pages individually

    Next.js documents incremental static regeneration: it updates static content without rebuilding the entire site and handles large numbers of pages without long build times. It also supports on-demand revalidation, so a page can be refreshed when its content is published.

  4. Some setups cannot use it

    The same documentation states that this feature is not supported in a static export, and that with multiple server instances the default cache is per instance. A site hosted as plain files needs a different approach or a different hosting setup.

  5. Images and heavy steps run on every build

    Resizing images, generating search indexes or calling extra services inside the build all add to its time and can often be cached or moved elsewhere.

What can I do about it today?

  1. Time itNote how long one small edit takes from publish to live, and how long a full deployment takes in your hosting dashboard. A number is easier to act on than a feeling.
  2. Count your pagesAsk your developer how many pages the site builds and which ones rarely change. This shows whether regeneration would help.
  3. Batch your editsIf every publish triggers a build, group small edits instead of publishing one at a time, so builds do not queue.
  4. Ask what kind of hosting it isIs it a static export, or does it run on a server? The answer decides which options exist.
  5. Do not remove content to speed it upDeleting pages or images to shorten builds can break links and search traffic. Ask first.

When should I bring someone in?

  • Builds fail or time out in your hosting dashboard.
  • Editors need live content quickly, such as prices or stock, and cannot wait.
  • Your developer is no longer available and nobody knows how the build is set up.

How do I handle it?

  1. Measure where the time goesI read the build log to see whether the time is spent fetching content, rendering pages or processing images.
  2. Choose per page typeRarely changing pages stay static. Frequently changing ones are regenerated on a schedule or when published.
  3. Connect publishing to the right pagesA publish action in the CMS refreshes only the affected page and the lists that include it.
  4. Cache what does not changeProcessed images and repeated content requests are cached between builds.
  5. Test with a copy firstThe change goes to a preview environment, with a tested way back to the previous setup.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is a slower build a sign my site is badly made?

Not necessarily. Builds grow with the page count. It becomes a problem when editors cannot publish comfortably.

Will visitors see a slow site meanwhile?

Build time affects how fast changes go live, not how fast a finished page loads for visitors.

Can this be fixed on any site?

It depends on the framework and hosting. I would need to see how the site is built before saying what is possible.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.