Hugo

Hugo is the fastest mainstream generator by a wide margin, which changes what goes wrong with it. The guides below are rarely about making a small Hugo site fast; they are about what happens at tens of thousands of pages, when template cost multiplies across languages, image processing dominates cold builds, module downloads outweigh rendering in CI, and a single build runs out of memory on a standard runner.

The build-time guides come first, then the ones about Hugo’s strongest built-in feature — multilingual sites — and then deployment and migration. Every number was measured with hyperfine or Hugo’s own template metrics on the site described in each guide.

Cold build time by stage on a 4,000-page Hugo repository Vertical bars from the render hooks and caching guide. On a cold build of a 4,000-page repository, image processing took 96 seconds, Markdown about 19 seconds and partials about 16 seconds, 131 seconds in total. With the resource cache, partialCached and a stable cacheDir the same build took 34 seconds. Where a cold Hugo build spends its time 96 s Image processing 19 s Markdown 16 s Partials 34 s Whole build, all caches warm
Measured with hyperfine on the repository in the render hooks and caching guide; image processing dominates until its cache is warm.

Choosing the Right Static Site Generator for Production

Number of Hugo guides of each kind Vertical bars: How-tos 27, Fixes 3, Comparisons 2 and Concepts 5. Hugo guides by kind 27 How-tos 3 Fixes 2 Comparisons 5 Concepts
37 guides use Hugo in depth; each is listed below under the section it belongs to.

Core Web Vitals Optimization for SSGs

  • Art Direction with the Picture ElementHow-toServe different crops of a hero image to mobile and desktop with picture and media queries in Astro, Eleventy and Hugo, without hurting LCP or causing layout shift.
  • Generating Open Graph Images at Build TimeHow-toRender a unique social preview image for every page at build time with Satori and resvg, cache the output, and wire og:image tags into Astro, Hugo or Eleventy.
  • Lazy-Loading Images Without Hurting LCPHow-toloading="lazy" saves bytes below the fold but delays the LCP image when applied to it. How to decide per image, per template, in Astro, Hugo and Eleventy.
  • Optimizing WebP Images in Hugo Without PluginsHow-toGenerate WebP at build time using only Hugo's built-in image processing — no Node, no plugins, no system libraries. Requires the hugo-extended edition for WebP.

Production-Ready Deployment & CI/CD for SSGs

Topics with the most Hugo guides Horizontal bars, largest first: Hugo Build Times for Large Repositories 12, SSG Framework Selection Matrix 5, Image Optimization Pipelines in Astro 4, Migrating Between Static Site Generators 3, Technical SEO for Static Sites 3 and Incremental Builds and Build Caching for SSGs 3. Where Hugo comes up Hugo Build Times for Large Repositories 12 SSG Framework Selection Matrix 5 Image Optimization Pipelines in Astro 4 Migrating Between Static Site Generators 3 Technical SEO 3 Incremental Builds and Build Caching 3
Topic pages give the wider context for each group; the numbers count only guides that use this tool in depth.

Often used with Hugo

  • Astro17 shared guidesIslands, content collections, astro:assets and deployment.
  • Eleventy15 shared guidesIncremental builds, image pipelines and the data cascade.
  • Jekyll5 shared guidesPlugins, reproducible builds, upgrades and migration away.
  • GitHub Actions3 shared guidesCaching, matrix builds, reusable workflows and pinning.
  • Vercel3 shared guidesNon-Next.js generators, the Build Output API and caching.
  • Next.js2 shared guidesStatic export for content sites, its limits and alternatives.