Fixes

A fix starts where you are: with something you can see. The page jumps as it loads. Lighthouse gives a different score on every run of the same commit. A build that used to finish in a couple of minutes now runs out of memory on the CI runner. Readers with a tab open across a deploy report that search stopped working. Each guide here names the symptom in its title, shows how to confirm which of the usual causes you actually have, and then fixes that cause — with the before and after numbers.

They are grouped by topic below. Layout-shift and LCP fixes dominate because those are the Core Web Vitals that static sites fail most often in the field while passing in the lab; the build-time fixes follow, and then the operational ones.

From symptom to verified fix Four stages. Observe the symptom in field data or logs. Reproduce it locally under throttling. Identify which of the known causes applies. Apply the fix and verify in the field that the number moved. How a fix is structured Observe field data or logs Reproduce throttled, locally Identify the cause one of the known few Fix and verify field number moves
Field data comes first and last: a fix is only done when the field number moves, not when the lab score does.

Accessibility for Static Sites

Number of fixes per topic, largest first Horizontal bars. Cumulative Layout Shift Fixes for Static Sites 8, Largest Contentful Paint Optimization for Static Sites 6, Astro vs Eleventy for Documentation Sites 4, Hugo Build Times for Large Repositories 3, Jekyll Plugin Ecosystem 2, Rollbacks and Deploy Safety for Static Sites 2, Accessibility for Static Sites 2 and Technical SEO for Static Sites 2. Topics with the most fixes Cumulative Layout Shift Fixes 8 Largest Contentful Paint Optimization 6 Astro vs Eleventy for Documentation… 4 Hugo Build Times for Large Repositories 3 Jekyll Plugin Ecosystem 2 Rollbacks and Deploy Safety 2 Accessibility 2 Technical SEO 2
The 8 topics with the most fixes, out of 30 topics that have any.

Astro vs Eleventy for Documentation Sites

Docs Frameworks: Docusaurus, Starlight and VitePress

Hugo Build Times for Large Repositories

Internationalization for Static Sites

Jekyll Plugin Ecosystem

Migrating Between Static Site Generators

Next.js Static Export for Content Sites

Search for Static Sites

Technical SEO for Static Sites

CDN Caching Rules for SSGs

CSS and JavaScript Asset Optimization

Cumulative Layout Shift Fixes for Static Sites

Font Loading Strategies for Static Sites

Image Optimization Pipelines in Astro

JavaScript Hydration & Partial Rendering

Number of fixes in each section Vertical bars: Framework selection 18, Performance 24 and Deployment 13. As a share of all guides in the section: Framework selection 15%, Performance 23%, Deployment 11%. Fixes in each section 18 Framework selection 24 Performance 13 Deployment
55 fixes in total. As a share of each section: framework selection 15%, performance 23%, deployment 11%.

Largest Contentful Paint Optimization for Static Sites

Performance Budgets and Lighthouse CI

  • Reducing Lighthouse Score Variance in CIWhy Lighthouse numbers jump between identical CI runs, and the six changes that shrank LCP spread from 800 ms to 90 ms so timing budgets can safely fail builds.

Resource Hints and Navigation Speed

Third-Party Script Performance on Static Sites

Cloudflare Pages Edge Caching Setup

GitHub Actions for Automated SSG Builds

Incremental Builds and Build Caching for SSGs

Monitoring Static Sites in Production

Netlify vs Vercel Deployment Strategies

Preview Environments for Pull Requests

Rollbacks and Deploy Safety for Static Sites

Security Headers and Hardening for Static Sites

Serverless Functions for Static Sites

Testing Static Sites in CI

Other kinds of guide

  • How-tosA task, end to end, with configuration and measured results.
  • ComparisonsWeighs two or more options against measured criteria.
  • ConceptsExplains how something works and when it matters.