[{"data":1,"prerenderedAt":2530},["ShallowReactive",2],{"page:\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci":3,"all-docs-nav":1377,"filed:\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci":2521},{"id":4,"title":5,"body":6,"breadcrumb":1352,"dateModified":1362,"datePublished":1362,"description":1363,"extension":1364,"faq":1365,"meta":1370,"navigation":1371,"path":1372,"seo":1373,"slug":12,"stem":1374,"type":1375,"__hash__":1376},"content\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci\u002Findex.md","Reducing Lighthouse Score Variance in CI",{"type":7,"value":8,"toc":1330},"minimark",[9,13,17,26,31,57,61,64,216,223,318,321,325,441,445,464,468,471,527,531,542,604,608,619,623,630,833,985,989,996,1000,1003,1102,1194,1197,1201,1204,1207,1210,1214,1247,1251,1254,1258,1263,1266,1270,1273,1277,1280,1284,1287,1291,1326],[10,11,5],"h1",{"id":12},"reducing-lighthouse-score-variance-in-ci",[14,15,16],"p",{},"Run Lighthouse ten times on the same page and you get ten different answers. On a laptop the spread is annoying; in CI, where a number above a threshold fails someone's pull request, it is the difference between a check people trust and one they mute. The fix is not a single setting but a handful of changes that each remove one source of noise, until the spread across unchanged builds is small enough to put a threshold above it.",[14,18,19,20,25],{},"This guide measures the spread on a real setup, removes the noise one source at a time, and reports what each change was worth. It supports the timing-budget approach in ",[21,22,24],"a",{"href":23},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002F","Performance Budgets and Lighthouse CI",".",[27,28,30],"h2",{"id":29},"prerequisites","Prerequisites",[32,33,34,42,50],"ul",{},[35,36,37,38,25],"li",{},"Lighthouse CI running in your pipeline — see ",[21,39,41],{"href":40},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site\u002F","Setting Up Lighthouse CI for a Static Site",[35,43,44,45,49],{},"The ability to trigger the workflow repeatedly on an unchanged commit (",[46,47,48],"code",{},"workflow_dispatch",").",[35,51,52,53,56],{},"Somewhere to collect results — the uploaded ",[46,54,55],{},".lighthouseci\u002F"," JSON is enough.",[27,58,60],{"id":59},"measure-the-spread-first","Measure the Spread First",[14,62,63],{},"Before changing anything, quantify the problem. Trigger the Lighthouse job twenty times on the same commit against the same preview URL, and compute the spread (max minus min, and the standard deviation) for each metric.",[65,66,71],"pre",{"className":67,"code":68,"language":69,"meta":70,"style":70},"language-bash shiki shiki-themes github-light github-dark","for i in $(seq 1 20); do gh workflow run lighthouse.yml -f ref=$SHA; sleep 5; done\n# after they finish:\ngh run list -w lighthouse.yml -L 20 --json databaseId -q '.[].databaseId' \\\n  | xargs -I{} gh run download {} -n lighthouse -D runs\u002F{}\nnode scripts\u002Fspread.mjs runs\u002F   # prints min, median, max, stdev per metric\n","bash","",[46,72,73,143,150,186,201],{"__ignoreMap":70},[74,75,78,82,86,89,92,96,100,103,106,109,112,116,119,122,125,128,131,134,137,140],"span",{"class":76,"line":77},"line",1,[74,79,81],{"class":80},"szBVR","for",[74,83,85],{"class":84},"sVt8B"," i ",[74,87,88],{"class":80},"in",[74,90,91],{"class":84}," $(",[74,93,95],{"class":94},"sScJk","seq",[74,97,99],{"class":98},"sj4cs"," 1",[74,101,102],{"class":98}," 20",[74,104,105],{"class":84},"); ",[74,107,108],{"class":80},"do",[74,110,111],{"class":94}," gh",[74,113,115],{"class":114},"sZZnC"," workflow",[74,117,118],{"class":114}," run",[74,120,121],{"class":114}," lighthouse.yml",[74,123,124],{"class":98}," -f",[74,126,127],{"class":114}," ref=",[74,129,130],{"class":84},"$SHA; ",[74,132,133],{"class":94},"sleep",[74,135,136],{"class":98}," 5",[74,138,139],{"class":84},"; ",[74,141,142],{"class":80},"done\n",[74,144,146],{"class":76,"line":145},2,[74,147,149],{"class":148},"sJ8bj","# after they finish:\n",[74,151,153,156,158,161,164,166,169,171,174,177,180,183],{"class":76,"line":152},3,[74,154,155],{"class":94},"gh",[74,157,118],{"class":114},[74,159,160],{"class":114}," list",[74,162,163],{"class":98}," -w",[74,165,121],{"class":114},[74,167,168],{"class":98}," -L",[74,170,102],{"class":98},[74,172,173],{"class":98}," --json",[74,175,176],{"class":114}," databaseId",[74,178,179],{"class":98}," -q",[74,181,182],{"class":114}," '.[].databaseId'",[74,184,185],{"class":98}," \\\n",[74,187,189,192,195,198],{"class":76,"line":188},4,[74,190,191],{"class":80},"  |",[74,193,194],{"class":94}," xargs",[74,196,197],{"class":98}," -I",[74,199,200],{"class":84},"{} gh run download {} -n lighthouse -D runs\u002F{}\n",[74,202,204,207,210,213],{"class":76,"line":203},5,[74,205,206],{"class":94},"node",[74,208,209],{"class":114}," scripts\u002Fspread.mjs",[74,211,212],{"class":114}," runs\u002F",[74,214,215],{"class":148},"   # prints min, median, max, stdev per metric\n",[14,217,218,219,222],{},"The starting point for a blog post template, single run per job, GitHub Actions ",[46,220,221],{},"ubuntu-latest",", Lighthouse 12 mobile:",[224,225,226,248],"table",{},[227,228,229],"thead",{},[230,231,232,236,239,242,245],"tr",{},[233,234,235],"th",{},"Metric",[233,237,238],{},"Min",[233,240,241],{},"Median",[233,243,244],{},"Max",[233,246,247],{},"Spread",[249,250,251,269,286,301],"tbody",{},[230,252,253,257,260,263,266],{},[254,255,256],"td",{},"LCP",[254,258,259],{},"1.62 s",[254,261,262],{},"1.94 s",[254,264,265],{},"2.42 s",[254,267,268],{},"800 ms",[230,270,271,274,277,280,283],{},[254,272,273],{},"TBT",[254,275,276],{},"30 ms",[254,278,279],{},"90 ms",[254,281,282],{},"240 ms",[254,284,285],{},"210 ms",[230,287,288,291,294,296,299],{},[254,289,290],{},"CLS",[254,292,293],{},"0.02",[254,295,293],{},[254,297,298],{},"0.04",[254,300,293],{},[230,302,303,306,309,312,315],{},[254,304,305],{},"Performance score",[254,307,308],{},"84",[254,310,311],{},"93",[254,313,314],{},"98",[254,316,317],{},"14 points",[14,319,320],{},"With an 800 ms spread, any LCP threshold low enough to catch a real regression also fails healthy builds.",[27,322,324],{"id":323},"the-six-sources-of-noise","The Six Sources of Noise",[326,327,328,437],"figure",{},[329,330,337,338,337,342,337,346,337,353],"svg",{"viewBox":331,"role":332,"ariaLabelledBy":333,"xmlns":336},"0 0 760 300","img",[334,335],"lsv-src-title","lsv-src-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[339,340,341],"title",{"id":334},"Where Lighthouse variance comes from",[343,344,345],"desc",{"id":335},"Six sources of noise grouped by where they live. On the runner: CPU contention from neighbouring jobs and differing hardware generations. On the network: latency jitter to the preview host and cold CDN caches. In the page: nondeterministic third-party scripts and A\u002FB experiments. In the tool: a single run treated as a measurement.",[347,348],"rect",{"x":349,"y":349,"width":350,"height":351,"fill":352},"0","760","300","#ffffff",[354,355,357,358,357,366,357,377,357,383,357,386,357,390,357,394,357,398,357,401,357,404,357,410,357,414,357,418,357,424,357,428,357,431,357,434,337],"g",{"style":356},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[359,360,365],"text",{"x":361,"y":362,"fill":363,"style":364},"380","28","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Six sources, four places",[347,367],{"x":368,"y":369,"width":370,"height":371,"rx":372,"fill":373,"opacity":374,"stroke":375,"style":376},"30","52","340","104","12","#ff595e","0.08","#d83b41","stroke-width:1.5px",[359,378,382],{"x":379,"y":380,"fill":363,"style":381},"50","78","font-weight:700","Runner",[359,384,385],{"x":379,"y":371,"fill":363},"1 · CPU contention from other jobs",[359,387,389],{"x":379,"y":388,"fill":363},"128","2 · different hardware per job",[347,391],{"x":392,"y":369,"width":370,"height":371,"rx":372,"fill":393,"opacity":374,"stroke":393,"style":376},"390","#1982c4",[359,395,397],{"x":396,"y":380,"fill":363,"style":381},"410","Network",[359,399,400],{"x":396,"y":371,"fill":363},"3 · latency jitter to the host",[359,402,403],{"x":396,"y":388,"fill":363},"4 · cold CDN cache on first hit",[347,405],{"x":368,"y":406,"width":370,"height":371,"rx":372,"fill":407,"opacity":408,"stroke":409,"style":376},"170","#ffca3a","0.14","#a97b00",[359,411,413],{"x":379,"y":412,"fill":363,"style":381},"196","Page",[359,415,417],{"x":379,"y":416,"fill":363},"222","5 · third parties and experiments",[359,419,423],{"x":379,"y":420,"fill":421,"style":422},"246","#556071","font-size:11px","ads, chat, A\u002FB scripts vary per load",[347,425],{"x":392,"y":406,"width":370,"height":371,"rx":372,"fill":426,"opacity":427,"stroke":426,"style":376},"#6a4c93","0.1",[359,429,430],{"x":396,"y":412,"fill":363,"style":381},"Method",[359,432,433],{"x":396,"y":416,"fill":363},"6 · one run treated as a measurement",[359,435,436],{"x":396,"y":420,"fill":421,"style":422},"no median, no warm-up, unpinned version",[438,439,440],"figcaption",{},"Each source adds its own spread; removing them one at a time shows which ones matter for your setup.",[27,442,444],{"id":443},"fix-1-median-of-several-runs","Fix 1: Median of Several Runs",[14,446,447,448,451,452,455,456,459,460,463],{},"The cheapest and largest improvement. Set ",[46,449,450],{},"numberOfRuns: 5"," and assert with ",[46,453,454],{},"aggregationMethod: 'median'",". Lighthouse CI also offers ",[46,457,458],{},"median-run",", which picks the run with the median performance score and uses all its metrics together; plain ",[46,461,462],{},"median"," takes the median of each metric independently, which is what you want for per-metric budgets.",[27,465,467],{"id":466},"fix-2-warm-the-cdn-before-measuring","Fix 2: Warm the CDN Before Measuring",[14,469,470],{},"A fresh preview deploy has a cold edge cache. The first Lighthouse run fetches every asset from origin; later runs hit the edge. Discard that effect by requesting each URL and its main assets once before collecting:",[65,472,474],{"className":67,"code":473,"language":69,"meta":70,"style":70},"for u in $(node -e \"require('.\u002Flighthouse\u002Furls')(process.env.PREVIEW_URL).forEach(x=>console.log(x))\"); do\n  curl -s -o \u002Fdev\u002Fnull \"$u\"\ndone\n",[46,475,476,500,523],{"__ignoreMap":70},[74,477,478,480,483,485,487,489,492,495,497],{"class":76,"line":77},[74,479,81],{"class":80},[74,481,482],{"class":84}," u ",[74,484,88],{"class":80},[74,486,91],{"class":84},[74,488,206],{"class":94},[74,490,491],{"class":98}," -e",[74,493,494],{"class":114}," \"require('.\u002Flighthouse\u002Furls')(process.env.PREVIEW_URL).forEach(x=>console.log(x))\"",[74,496,105],{"class":84},[74,498,499],{"class":80},"do\n",[74,501,502,505,508,511,514,517,520],{"class":76,"line":145},[74,503,504],{"class":94},"  curl",[74,506,507],{"class":98}," -s",[74,509,510],{"class":98}," -o",[74,512,513],{"class":114}," \u002Fdev\u002Fnull",[74,515,516],{"class":114}," \"",[74,518,519],{"class":84},"$u",[74,521,522],{"class":114},"\"\n",[74,524,525],{"class":76,"line":152},[74,526,142],{"class":80},[27,528,530],{"id":529},"fix-3-block-nondeterministic-third-parties","Fix 3: Block Nondeterministic Third Parties",[14,532,533,534,537,538,25],{},"Analytics, chat widgets, consent managers and A\u002FB testing scripts behave differently on each load. In CI, measure your own code and block them with ",[46,535,536],{},"blockedUrlPatterns",", then measure third-party cost separately and deliberately, as described in ",[21,539,541],{"href":540},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fauditing-third-party-scripts-with-lighthouse\u002F","Auditing Third-Party Scripts with Lighthouse",[65,543,547],{"className":544,"code":545,"language":546,"meta":70,"style":70},"language-js shiki shiki-themes github-light github-dark","collect: {\n  settings: {\n    blockedUrlPatterns: ['*googletagmanager.com*', '*intercom*', '*hotjar*', '*optimizely*'],\n  },\n},\n","js",[46,548,549,557,564,594,599],{"__ignoreMap":70},[74,550,551,554],{"class":76,"line":77},[74,552,553],{"class":94},"collect",[74,555,556],{"class":84},": {\n",[74,558,559,562],{"class":76,"line":145},[74,560,561],{"class":94},"  settings",[74,563,556],{"class":84},[74,565,566,569,572,575,578,581,583,586,588,591],{"class":76,"line":152},[74,567,568],{"class":94},"    blockedUrlPatterns",[74,570,571],{"class":84},": [",[74,573,574],{"class":114},"'*googletagmanager.com*'",[74,576,577],{"class":84},", ",[74,579,580],{"class":114},"'*intercom*'",[74,582,577],{"class":84},[74,584,585],{"class":114},"'*hotjar*'",[74,587,577],{"class":84},[74,589,590],{"class":114},"'*optimizely*'",[74,592,593],{"class":84},"],\n",[74,595,596],{"class":76,"line":188},[74,597,598],{"class":84},"  },\n",[74,600,601],{"class":76,"line":203},[74,602,603],{"class":84},"},\n",[27,605,607],{"id":606},"fix-4-pin-chrome-and-lighthouse","Fix 4: Pin Chrome and Lighthouse",[14,609,610,611,614,615,618],{},"A Chrome or Lighthouse update can shift metrics by several percent. Pin ",[46,612,613],{},"@lhci\u002Fcli"," to a minor version and install a specific Chrome build (",[46,616,617],{},"browser-actions\u002Fsetup-chrome"," with a version input). Upgrade both deliberately, re-measure the spread, and re-baseline budgets in the same pull request.",[27,620,622],{"id":621},"fix-5-detect-or-avoid-slow-runners","Fix 5: Detect or Avoid Slow Runners",[14,624,625,626,629],{},"Lighthouse records a ",[46,627,628],{},"benchmarkIndex"," for the machine it ran on. On shared runners it varied from about 1,100 to 1,900 across the twenty jobs, and TBT correlated with it strongly. Two options: discard runs whose benchmark index is below a floor and re-run, or move the job to a dedicated runner. A self-hosted runner, or a larger GitHub-hosted runner, with no other jobs scheduled, removed most of the TBT spread.",[65,631,633],{"className":544,"code":632,"language":546,"meta":70,"style":70},"\u002F\u002F scripts\u002Fcheck-benchmark.mjs — fail fast on an unusually slow runner\nimport { readdirSync, readFileSync } from 'node:fs';\nconst idx = readdirSync('.lighthouseci').filter((f) => f.startsWith('lhr-'))\n  .map((f) => JSON.parse(readFileSync(`.lighthouseci\u002F${f}`)).environment.benchmarkIndex);\nconst min = Math.min(...idx);\nconsole.log(`benchmarkIndex min ${min}`);\nif (min \u003C 1300) { console.log('Slow runner — re-run the job'); process.exit(78); }\n",[46,634,635,640,657,709,751,774,795],{"__ignoreMap":70},[74,636,637],{"class":76,"line":77},[74,638,639],{"class":148},"\u002F\u002F scripts\u002Fcheck-benchmark.mjs — fail fast on an unusually slow runner\n",[74,641,642,645,648,651,654],{"class":76,"line":145},[74,643,644],{"class":80},"import",[74,646,647],{"class":84}," { readdirSync, readFileSync } ",[74,649,650],{"class":80},"from",[74,652,653],{"class":114}," 'node:fs'",[74,655,656],{"class":84},";\n",[74,658,659,662,665,668,671,674,677,679,682,685,689,692,695,698,701,703,706],{"class":76,"line":152},[74,660,661],{"class":80},"const",[74,663,664],{"class":98}," idx",[74,666,667],{"class":80}," =",[74,669,670],{"class":94}," readdirSync",[74,672,673],{"class":84},"(",[74,675,676],{"class":114},"'.lighthouseci'",[74,678,49],{"class":84},[74,680,681],{"class":94},"filter",[74,683,684],{"class":84},"((",[74,686,688],{"class":687},"s4XuR","f",[74,690,691],{"class":84},") ",[74,693,694],{"class":80},"=>",[74,696,697],{"class":84}," f.",[74,699,700],{"class":94},"startsWith",[74,702,673],{"class":84},[74,704,705],{"class":114},"'lhr-'",[74,707,708],{"class":84},"))\n",[74,710,711,714,717,719,721,723,725,728,730,733,735,738,740,743,745,748],{"class":76,"line":188},[74,712,713],{"class":84},"  .",[74,715,716],{"class":94},"map",[74,718,684],{"class":84},[74,720,688],{"class":687},[74,722,691],{"class":84},[74,724,694],{"class":80},[74,726,727],{"class":98}," JSON",[74,729,25],{"class":84},[74,731,732],{"class":94},"parse",[74,734,673],{"class":84},[74,736,737],{"class":94},"readFileSync",[74,739,673],{"class":84},[74,741,742],{"class":114},"`.lighthouseci\u002F${",[74,744,688],{"class":84},[74,746,747],{"class":114},"}`",[74,749,750],{"class":84},")).environment.benchmarkIndex);\n",[74,752,753,755,758,760,763,766,768,771],{"class":76,"line":203},[74,754,661],{"class":80},[74,756,757],{"class":98}," min",[74,759,667],{"class":80},[74,761,762],{"class":84}," Math.",[74,764,765],{"class":94},"min",[74,767,673],{"class":84},[74,769,770],{"class":80},"...",[74,772,773],{"class":84},"idx);\n",[74,775,777,780,783,785,788,790,792],{"class":76,"line":776},6,[74,778,779],{"class":84},"console.",[74,781,782],{"class":94},"log",[74,784,673],{"class":84},[74,786,787],{"class":114},"`benchmarkIndex min ${",[74,789,765],{"class":84},[74,791,747],{"class":114},[74,793,794],{"class":84},");\n",[74,796,798,801,804,807,810,813,815,817,820,823,826,828,830],{"class":76,"line":797},7,[74,799,800],{"class":80},"if",[74,802,803],{"class":84}," (min ",[74,805,806],{"class":80},"\u003C",[74,808,809],{"class":98}," 1300",[74,811,812],{"class":84},") { console.",[74,814,782],{"class":94},[74,816,673],{"class":84},[74,818,819],{"class":114},"'Slow runner — re-run the job'",[74,821,822],{"class":84},"); process.",[74,824,825],{"class":94},"exit",[74,827,673],{"class":84},[74,829,380],{"class":98},[74,831,832],{"class":84},"); }\n",[326,834,835,982],{},[329,836,337,841,337,844,337,847,337,850],{"viewBox":837,"role":332,"ariaLabelledBy":838,"xmlns":336},"0 0 760 280",[839,840],"lsv-bench-title","lsv-bench-desc",[339,842,843],{"id":839},"Total Blocking Time against runner benchmark index",[343,845,846],{"id":840},"A scatter plot of twenty jobs. Runners with a benchmark index around 1,100 to 1,300 produced TBT between 170 and 240 milliseconds; runners around 1,600 to 1,900 produced TBT between 30 and 90 milliseconds. A dashed line at 1,300 marks the floor below which runs are discarded.",[347,848],{"x":349,"y":349,"width":350,"height":849,"fill":352},"280",[354,851,357,852,357,855,357,860,357,862,357,867,357,871,357,875,357,881,357,885,357,889,357,892,357,899,357,906,357,910,357,914,357,918,357,922,357,928,357,931,357,933,357,937,357,941,357,945,357,948,357,951,357,955,357,959,357,963,357,967,357,971,357,975,357,978,337],{"style":356},[359,853,854],{"x":361,"y":362,"fill":363,"style":364},"Slower runners, longer blocking time",[76,856],{"x1":857,"y1":858,"x2":859,"y2":858,"stroke":421,"style":376},"80","230","720",[76,861],{"x1":857,"y1":379,"x2":857,"y2":858,"stroke":421,"style":376},[359,863,349],{"x":864,"y":865,"fill":421,"style":866},"72","234","font-size:11px;text-anchor:end",[359,868,870],{"x":864,"y":869,"fill":421,"style":866},"144","125",[359,872,874],{"x":864,"y":873,"fill":421,"style":866},"54","250 ms",[359,876,880],{"x":877,"y":878,"fill":421,"style":879},"100","248","font-size:11px;text-anchor:middle","1,000",[359,882,884],{"x":883,"y":878,"fill":421,"style":879},"400","1,500",[359,886,888],{"x":887,"y":878,"fill":421,"style":879},"700","2,000",[76,890],{"x1":849,"y1":379,"x2":849,"y2":858,"stroke":375,"style":891},"stroke-width:1.5px;stroke-dasharray:6 4",[359,893,898],{"x":894,"y":895,"fill":896,"style":897},"286","64","#b32b30","font-size:11px;font-weight:700","discard below 1,300",[900,901],"circle",{"cx":902,"cy":903,"r":904,"fill":373,"stroke":375,"style":905},"160","58","5","stroke-width:1px",[900,907],{"cx":908,"cy":909,"r":904,"fill":373,"stroke":375,"style":905},"190","82",[900,911],{"cx":912,"cy":913,"r":904,"fill":373,"stroke":375,"style":905},"215","70",[900,915],{"cx":916,"cy":917,"r":904,"fill":373,"stroke":375,"style":905},"240","96",[900,919],{"cx":920,"cy":921,"r":904,"fill":373,"stroke":375,"style":905},"265","108",[900,923],{"cx":924,"cy":925,"r":904,"fill":926,"stroke":927,"style":905},"330","150","#8ac926","#5a8a16",[900,929],{"cx":930,"cy":902,"r":904,"fill":926,"stroke":927,"style":905},"370",[900,932],{"cx":396,"cy":406,"r":904,"fill":926,"stroke":927,"style":905},[900,934],{"cx":935,"cy":936,"r":904,"fill":926,"stroke":927,"style":905},"440","176",[900,938],{"cx":939,"cy":940,"r":904,"fill":926,"stroke":927,"style":905},"470","168",[900,942],{"cx":943,"cy":944,"r":904,"fill":926,"stroke":927,"style":905},"500","184",[900,946],{"cx":947,"cy":908,"r":904,"fill":926,"stroke":927,"style":905},"530",[900,949],{"cx":950,"cy":412,"r":904,"fill":926,"stroke":927,"style":905},"560",[900,952],{"cx":953,"cy":954,"r":904,"fill":926,"stroke":927,"style":905},"590","188",[900,956],{"cx":957,"cy":958,"r":904,"fill":926,"stroke":927,"style":905},"610","200",[900,960],{"cx":961,"cy":962,"r":904,"fill":926,"stroke":927,"style":905},"630","204",[900,964],{"cx":965,"cy":966,"r":904,"fill":926,"stroke":927,"style":905},"650","198",[900,968],{"cx":969,"cy":970,"r":904,"fill":926,"stroke":927,"style":905},"670","210",[900,972],{"cx":973,"cy":974,"r":904,"fill":926,"stroke":927,"style":905},"690","206",[900,976],{"cx":887,"cy":977,"r":904,"fill":926,"stroke":927,"style":905},"214",[359,979,981],{"x":883,"y":980,"fill":421,"style":879},"270","x: Lighthouse benchmarkIndex · y: TBT · 20 jobs on GitHub-hosted ubuntu-latest",[438,983,984],{},"Five of twenty jobs landed on noticeably slower hardware and produced all of the high TBT readings.",[27,986,988],{"id":987},"fix-6-budget-bytes-alongside-timings","Fix 6: Budget Bytes Alongside Timings",[14,990,991,992,25],{},"Byte sizes do not vary at all between runs of the same build. For every timing budget, add the byte budget that usually drives it — script bytes for TBT, above-the-fold image bytes for LCP on image-led templates. Then the timing budget can stay a warning with a generous threshold while the byte budget is a hard error, and most real regressions are still caught deterministically. The pattern is laid out in ",[21,993,995],{"href":994},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fwriting-a-performance-budget-that-fails-builds\u002F","Writing a Performance Budget That Fails Builds",[27,997,999],{"id":998},"measured-impact","Measured Impact",[14,1001,1002],{},"The same twenty-job experiment after each cumulative change:",[224,1004,1005,1021],{},[227,1006,1007],{},[230,1008,1009,1012,1015,1018],{},[233,1010,1011],{},"Configuration",[233,1013,1014],{},"LCP spread",[233,1016,1017],{},"TBT spread",[233,1019,1020],{},"Score spread",[249,1022,1023,1035,1049,1062,1076,1089],{},[230,1024,1025,1028,1030,1032],{},[254,1026,1027],{},"Baseline: 1 run, shared runner",[254,1029,268],{},[254,1031,285],{},[254,1033,1034],{},"14 pts",[230,1036,1037,1040,1043,1046],{},[254,1038,1039],{},"+ median of 5",[254,1041,1042],{},"260 ms",[254,1044,1045],{},"110 ms",[254,1047,1048],{},"5 pts",[230,1050,1051,1054,1057,1060],{},[254,1052,1053],{},"+ CDN warm-up",[254,1055,1056],{},"190 ms",[254,1058,1059],{},"105 ms",[254,1061,1048],{},[230,1063,1064,1067,1070,1073],{},[254,1065,1066],{},"+ third parties blocked",[254,1068,1069],{},"150 ms",[254,1071,1072],{},"80 ms",[254,1074,1075],{},"4 pts",[230,1077,1078,1081,1084,1087],{},[254,1079,1080],{},"+ pinned Chrome and Lighthouse",[254,1082,1083],{},"140 ms",[254,1085,1086],{},"75 ms",[254,1088,1075],{},[230,1090,1091,1094,1096,1099],{},[254,1092,1093],{},"+ dedicated runner",[254,1095,279],{},[254,1097,1098],{},"35 ms",[254,1100,1101],{},"2 pts",[326,1103,1104,1191],{},[329,1105,337,1110,337,1113,337,1116,337,1119],{"viewBox":1106,"role":332,"ariaLabelledBy":1107,"xmlns":336},"0 0 760 290",[1108,1109],"lsv-step-title","lsv-step-desc",[339,1111,1112],{"id":1108},"LCP spread after each cumulative fix",[343,1114,1115],{"id":1109},"Descending bars of LCP spread across twenty identical jobs: 800 milliseconds at baseline, 260 with a median of five runs, 190 with CDN warm-up, 150 with third parties blocked, 140 with pinned versions, and 90 on a dedicated runner.",[347,1117],{"x":349,"y":349,"width":350,"height":1118,"fill":352},"290",[354,1120,357,1121,357,1124,357,1127,357,1130,357,1135,357,1138,357,1142,357,1146,357,1149,357,1152,357,1155,357,1159,357,1162,357,1165,357,1168,357,1172,357,1175,357,1178,357,1181,357,1184,357,1187,337],{"style":356},[359,1122,1123],{"x":361,"y":362,"fill":363,"style":364},"LCP spread across 20 identical jobs (ms)",[76,1125],{"x1":1126,"y1":916,"x2":859,"y2":916,"stroke":421,"style":376},"60",[347,1128],{"x":857,"y":857,"width":857,"height":902,"fill":373,"opacity":1129,"stroke":375,"style":905},"0.28",[359,1131,1134],{"x":1132,"y":864,"fill":363,"style":1133},"120","font-weight:700;text-anchor:middle","800",[347,1136],{"x":908,"y":954,"width":857,"height":369,"fill":407,"opacity":1137,"stroke":409,"style":905},"0.35",[359,1139,1141],{"x":858,"y":1140,"fill":363,"style":1133},"180","260",[347,1143],{"x":351,"y":1144,"width":857,"height":1145,"fill":407,"opacity":1137,"stroke":409,"style":905},"202","38",[359,1147,908],{"x":370,"y":1148,"fill":363,"style":1133},"194",[347,1150],{"x":396,"y":970,"width":857,"height":368,"fill":393,"opacity":1151,"stroke":393,"style":905},"0.25",[359,1153,925],{"x":1154,"y":1144,"fill":363,"style":1133},"450",[347,1156],{"x":1157,"y":1158,"width":857,"height":362,"fill":393,"opacity":1151,"stroke":393,"style":905},"520","212",[359,1160,1161],{"x":950,"y":962,"fill":363,"style":1133},"140",[347,1163],{"x":961,"y":416,"width":857,"height":1164,"fill":926,"opacity":1137,"stroke":927,"style":905},"18",[359,1166,1167],{"x":969,"y":977,"fill":363,"style":1133},"90",[359,1169,1171],{"x":1132,"y":1170,"fill":421,"style":879},"258","baseline",[359,1173,1174],{"x":858,"y":1170,"fill":421,"style":879},"median of 5",[359,1176,1177],{"x":370,"y":1170,"fill":421,"style":879},"CDN warm",[359,1179,1180],{"x":1154,"y":1170,"fill":421,"style":879},"3P blocked",[359,1182,1183],{"x":950,"y":1170,"fill":421,"style":879},"pinned",[359,1185,1186],{"x":969,"y":1170,"fill":421,"style":879},"dedicated",[359,1188,1190],{"x":361,"y":1189,"fill":421,"style":879},"282","Blog template, Lighthouse 12 mobile, preview on Cloudflare; each bar includes all fixes to its left",[438,1192,1193],{},"The median does most of the work; the dedicated runner matters mainly for CPU-bound metrics like TBT.",[14,1195,1196],{},"With a 90 ms LCP spread around a 1.9 s median, an error threshold at 2.2 s sits more than three spreads above the median. That is safe to enforce, and it would still catch the 300 ms regression a mis-sized hero image typically causes.",[27,1198,1200],{"id":1199},"keeping-variance-low-over-time","Keeping Variance Low Over Time",[14,1202,1203],{},"Variance creeps back. A new third-party script is added and nobody updates the block list; the runner image is upgraded and the benchmark floor no longer matches; a template gains an animation that makes LCP timing depend on when the animation frame lands. Re-run the twenty-job spread measurement once a quarter and after any Lighthouse, Chrome or runner change, and keep the result next to the budgets in the repository so the next person can see what \"normal\" looks like.",[14,1205,1206],{},"It also helps to separate the performance job from everything else. Running Lighthouse in the same job as the build, or in parallel with a heavy test suite on the same self-hosted machine, reintroduces CPU contention you removed by choosing a dedicated runner. A job that does nothing but warm the CDN, run Lighthouse and upload results is easier to reason about and measurably steadier.",[14,1208,1209],{},"Finally, make noise visible in reports. Lighthouse CI's output includes every run's values; surfacing the min–max range in the pull request comment next to the median lets reviewers see at a glance whether a result is clear-cut or borderline, and they stop treating a single number as more precise than it is.",[27,1211,1213],{"id":1212},"pitfalls-rollback","Pitfalls & Rollback",[32,1215,1216,1223,1229,1235,1241],{},[35,1217,1218,1222],{},[1219,1220,1221],"strong",{},"Blocking third parties and forgetting them."," Blocked scripts still affect readers. Measure them in a separate scheduled job so their cost is visible.",[35,1224,1225,1228],{},[1219,1226,1227],{},"Averaging instead of taking the median."," One outlier run drags a mean; the median ignores it.",[35,1230,1231,1234],{},[1219,1232,1233],{},"Re-running until green."," Automatic retries on failure hide real regressions. Retry only on a detected slow runner, not on a failed assertion.",[35,1236,1237,1240],{},[1219,1238,1239],{},"Comparing across Lighthouse versions."," Re-baseline after every upgrade instead of assuming continuity.",[35,1242,1243,1246],{},[1219,1244,1245],{},"Rollback:"," each fix is a config line or a workflow step. Revert any one of them and re-measure the spread to see what it was contributing.",[27,1248,1250],{"id":1249},"conclusion","Conclusion",[14,1252,1253],{},"Lighthouse variance in CI is not mysterious; it comes from a few identifiable sources, and each has a direct fix. Median of five runs, a CDN warm-up, blocked third parties, pinned versions, a quiet runner and byte budgets alongside timing budgets took LCP spread from 800 ms to 90 ms and TBT spread from 210 ms to 35 ms on the same unchanged page. At that level, timing budgets can fail builds without failing healthy ones.",[27,1255,1257],{"id":1256},"faq","FAQ",[1259,1260,1262],"h3",{"id":1261},"how-many-lighthouse-runs-per-url-are-enough","How many Lighthouse runs per URL are enough?",[14,1264,1265],{},"Three is the practical minimum and five is better for timing metrics. In our measurements, moving from one run to the median of three cut the LCP spread by about two thirds; going to five cut it by a further quarter.",[1259,1267,1269],{"id":1268},"does-simulated-or-applied-throttling-vary-less","Does simulated or applied throttling vary less?",[14,1271,1272],{},"Simulated throttling, the default, usually varies less because it models the network from an unthrottled trace. Applied throttling with DevTools is more realistic but more sensitive to runner load.",[1259,1274,1276],{"id":1275},"why-is-total-blocking-time-so-noisy","Why is Total Blocking Time so noisy?",[14,1278,1279],{},"TBT depends on how long main-thread tasks take, which depends directly on CPU speed. Shared CI runners vary in CPU availability from job to job, so TBT moves more than network-bound metrics. Lighthouse's benchmark index can be used to detect slow runners.",[1259,1281,1283],{"id":1282},"should-i-use-a-dedicated-runner","Should I use a dedicated runner?",[14,1285,1286],{},"If timing budgets must block merges, yes. A self-hosted or larger dedicated runner with nothing else scheduled on it cut TBT spread from 170 ms to 35 ms in our tests. Byte budgets do not need it because sizes do not vary.",[27,1288,1290],{"id":1289},"related","Related",[32,1292,1293,1302,1307,1314,1321],{},[35,1294,1295,1298,1299,1301],{},[1219,1296,1297],{},"Parent:"," ",[21,1300,24],{"href":23}," — why timing budgets need low variance.",[35,1303,1304,1306],{},[21,1305,995],{"href":994}," — when to promote a warning to an error.",[35,1308,1309,1313],{},[21,1310,1312],{"href":1311},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Frunning-webpagetest-scripts-against-preview-deploys\u002F","Running WebPageTest Scripts Against Preview Deploys"," — real devices when lab emulation is not enough.",[35,1315,1316,1320],{},[21,1317,1319],{"href":1318},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fmeasuring-build-time-regressions-in-ci\u002F","Measuring Build Time Regressions in CI"," — the same noise problem for build durations.",[35,1322,1323,1325],{},[21,1324,541],{"href":540}," — measuring what CI blocks.",[1327,1328,1329],"style",{},"html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}",{"title":70,"searchDepth":145,"depth":145,"links":1331},[1332,1333,1334,1335,1336,1337,1338,1339,1340,1341,1342,1343,1344,1345,1351],{"id":29,"depth":145,"text":30},{"id":59,"depth":145,"text":60},{"id":323,"depth":145,"text":324},{"id":443,"depth":145,"text":444},{"id":466,"depth":145,"text":467},{"id":529,"depth":145,"text":530},{"id":606,"depth":145,"text":607},{"id":621,"depth":145,"text":622},{"id":987,"depth":145,"text":988},{"id":998,"depth":145,"text":999},{"id":1199,"depth":145,"text":1200},{"id":1212,"depth":145,"text":1213},{"id":1249,"depth":145,"text":1250},{"id":1256,"depth":145,"text":1257,"children":1346},[1347,1348,1349,1350],{"id":1261,"depth":152,"text":1262},{"id":1268,"depth":152,"text":1269},{"id":1275,"depth":152,"text":1276},{"id":1282,"depth":152,"text":1283},{"id":1289,"depth":145,"text":1290},[1353,1356,1359,1360],{"name":1354,"item":1355},"Home","\u002F",{"name":1357,"item":1358},"Performance Optimization & Core Web Vitals for SSGs","\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002F",{"name":24,"item":23},{"name":5,"item":1361},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci\u002F","2026-09-18","Why 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.","md",[1366,1367,1368,1369],{"q":1262,"a":1265},{"q":1269,"a":1272},{"q":1276,"a":1279},{"q":1283,"a":1286},{},true,"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci",{"title":5,"description":1363},"performance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci\u002Findex","article","QFMm2Zi4MbTK7kmmi-hgpgNBCzc6UzkIYuVbUyaWfQ8",[1378,1381,1384,1387,1390,1393,1396,1399,1402,1405,1408,1411,1414,1417,1420,1423,1426,1429,1432,1435,1438,1441,1444,1447,1450,1453,1456,1459,1462,1465,1468,1471,1474,1477,1480,1483,1486,1489,1492,1495,1498,1501,1504,1507,1510,1513,1516,1519,1522,1525,1528,1531,1534,1537,1540,1543,1546,1549,1552,1555,1558,1561,1564,1567,1570,1573,1576,1579,1582,1585,1588,1591,1594,1597,1600,1603,1606,1609,1612,1615,1618,1621,1624,1627,1630,1633,1636,1639,1642,1645,1648,1651,1654,1657,1660,1663,1666,1669,1672,1675,1678,1681,1684,1687,1690,1693,1696,1699,1702,1705,1708,1711,1714,1717,1720,1723,1726,1729,1732,1735,1738,1741,1744,1747,1750,1753,1756,1759,1762,1765,1768,1771,1774,1777,1780,1783,1786,1789,1792,1795,1798,1801,1804,1807,1810,1813,1816,1819,1822,1825,1828,1831,1834,1837,1840,1843,1846,1849,1852,1855,1858,1861,1864,1867,1870,1873,1876,1879,1882,1885,1888,1891,1894,1897,1900,1903,1906,1909,1912,1915,1918,1921,1924,1927,1930,1933,1936,1939,1942,1945,1948,1951,1954,1957,1960,1963,1966,1969,1972,1975,1978,1981,1984,1987,1990,1993,1996,1999,2002,2005,2008,2011,2014,2017,2020,2023,2026,2028,2031,2034,2037,2040,2041,2043,2045,2048,2051,2053,2056,2059,2062,2065,2068,2071,2074,2077,2080,2083,2086,2089,2092,2095,2098,2101,2104,2107,2110,2113,2116,2119,2122,2125,2128,2131,2134,2137,2140,2143,2146,2149,2152,2155,2158,2161,2164,2167,2170,2173,2176,2179,2182,2185,2188,2191,2194,2197,2200,2203,2206,2209,2212,2215,2218,2221,2224,2227,2230,2233,2236,2239,2242,2245,2248,2251,2254,2257,2260,2263,2266,2269,2272,2275,2278,2281,2284,2287,2290,2293,2296,2299,2302,2305,2308,2311,2314,2317,2320,2323,2326,2329,2332,2335,2338,2341,2344,2347,2350,2353,2356,2359,2362,2365,2368,2371,2374,2377,2380,2383,2386,2389,2392,2395,2398,2401,2404,2407,2410,2413,2416,2419,2422,2425,2428,2431,2434,2437,2440,2443,2446,2449,2452,2455,2458,2461,2464,2467,2470,2473,2476,2479,2482,2485,2488,2491,2494,2497,2500,2503,2506,2509,2512,2515,2518],{"path":1379,"title":1380},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-code-blocks-in-documentation-sites","Accessible Code Blocks in Documentation Sites",{"path":1382,"title":1383},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-dark-mode-toggles-for-static-sites","Accessible Dark Mode Toggles for Static Sites",{"path":1385,"title":1386},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-svg-diagrams-on-static-sites","Accessible SVG Diagrams on Static Sites",{"path":1388,"title":1389},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fenforcing-alt-text-for-markdown-images-at-build-time","Enforcing Alt Text for Markdown Images at Build Time",{"path":1391,"title":1392},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content","Fixing Heading Order Problems in Markdown Content",{"path":1394,"title":1395},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-low-color-contrast-flagged-by-lighthouse","Fixing Low Color Contrast Flagged by Lighthouse",{"path":1397,"title":1398},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1400,"title":1401},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fkeyboard-navigation-and-focus-order-on-static-sites","Keyboard Navigation and Focus Order on Static Sites",{"path":1403,"title":1404},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fskip-links-and-landmarks-in-ssg-layouts","Skip Links and Landmarks in SSG Layouts",{"path":1406,"title":1407},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fastro-vs-eleventy-build-times-at-10000-pages","Astro vs Eleventy Build Times at 10,000 Pages",{"path":1409,"title":1410},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fchoosing-between-astro-and-eleventy-for-large-docs","Astro vs Eleventy for Large Docs (1000+ Pages)",{"path":1412,"title":1413},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fcontent-collections-vs-eleventy-data-cascade","Content Collections vs the Eleventy Data Cascade",{"path":1415,"title":1416},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fdev-server-performance-astro-vs-eleventy","Dev Server Performance: Astro vs Eleventy",{"path":1418,"title":1419},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-astro-build-errors-after-upgrading-to-astro-5","Fixing Astro Build Errors After Upgrading to Astro 5",{"path":1421,"title":1422},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-duplicate-permalink-errors-in-eleventy","Fixing Duplicate Permalink Errors in Eleventy",{"path":1424,"title":1425},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-eleventy-out-of-memory-errors-on-large-collections","Fixing Eleventy Out-of-Memory Errors on Large Collections",{"path":1427,"title":1428},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-slow-astro-builds-caused-by-large-mdx-collections","Fixing Slow Astro Builds Caused by Large MDX Collections",{"path":1430,"title":1431},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1433,"title":1434},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Floading-remote-content-with-astro-content-layer-loaders","Loading Remote Content With Astro Content Layer Loaders",{"path":1436,"title":1437},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fmarkdown-pipelines-remark-vs-markdown-it","Markdown Pipelines: remark vs markdown-it",{"path":1439,"title":1440},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors","Shortcodes vs Components for Docs Authors",{"path":1442,"title":1443},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fsidebar-navigation-in-astro-and-eleventy","Sidebar Navigation in Astro and Eleventy",{"path":1445,"title":1446},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fsyntax-highlighting-with-shiki-in-astro-and-eleventy","Syntax Highlighting with Shiki in Astro and Eleventy",{"path":1448,"title":1449},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fupgrading-eleventy-2-to-3-with-esm-configuration","Upgrading Eleventy 2 to 3 With ESM Configuration",{"path":1451,"title":1452},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fadding-local-search-to-a-vitepress-site","Adding Local Search to a VitePress Site",{"path":1454,"title":1455},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1457,"title":1458},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcustomizing-starlight-without-forking-the-theme","Customizing Starlight Without Forking the Theme",{"path":1460,"title":1461},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fdocusaurus-vs-starlight-for-product-documentation","Docusaurus vs Starlight for Product Documentation",{"path":1463,"title":1464},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Ffixing-broken-links-reported-by-docusaurus-builds","Fixing Broken Links Reported by Docusaurus Builds",{"path":1466,"title":1467},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fgenerating-api-reference-pages-in-starlight-from-openapi","Generating API Reference Pages in Starlight From OpenAPI",{"path":1469,"title":1470},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1472,"title":1473},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1475,"title":1476},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content","MDX vs Markdoc for Docs Content",{"path":1478,"title":1479},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1481,"title":1482},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1484,"title":1485},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fspeeding-up-docusaurus-builds-with-rspack","Speeding Up Docusaurus Builds With Rspack",{"path":1487,"title":1488},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1490,"title":1491},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioning-vitepress-documentation-without-a-plugin","Versioning VitePress Documentation Without a Plugin",{"path":1493,"title":1494},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1496,"title":1497},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-vs-starlight-for-vue-and-astro-teams","VitePress vs Starlight for Vue and Astro Teams",{"path":1499,"title":1500},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Ffixing-hugo-builds-that-fail-after-a-version-upgrade","Fixing Hugo Builds That Fail After a Version Upgrade",{"path":1502,"title":1503},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Ffixing-hugo-builds-that-slow-down-after-adding-taxonomies","Fixing Hugo Builds That Slow Down After Adding Taxonomies",{"path":1505,"title":1506},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhow-to-benchmark-hugo-vs-astro-build-speeds","How to Benchmark Hugo vs Astro Build Speeds",{"path":1508,"title":1509},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-image-processing-cache-in-ci","Hugo Image Processing Cache in CI",{"path":1511,"title":1512},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-modules-and-dependency-caching","Hugo Modules and Dependency Caching",{"path":1514,"title":1515},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds","Hugo partialCached for Faster Builds",{"path":1517,"title":1518},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1520,"title":1521},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fparallel-hugo-builds-across-ci-jobs","Parallel Hugo Builds Across CI Jobs",{"path":1523,"title":1524},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fprofiling-hugo-templates-with-template-metrics","Profiling Hugo Templates With Template Metrics",{"path":1526,"title":1527},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners","Reducing Hugo Memory Usage on CI Runners",{"path":1529,"title":1530},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fsharing-a-theme-across-hugo-sites-with-modules","Sharing a Theme Across Hugo Sites With Modules",{"path":1532,"title":1533},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fspeeding-up-hugo-builds-with-render-hooks-and-caching","Speeding Up Hugo Builds with Render Hooks & Caching",{"path":1535,"title":1536},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fsplitting-large-hugo-sites-with-segments","Splitting Large Hugo Sites with Segments",{"path":1538,"title":1539},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1541,"title":1542},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Ffixing-hreflang-errors-reported-in-search-console","Fixing Hreflang Errors Reported in Search Console",{"path":1544,"title":1545},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fhreflang-and-language-alternates-on-static-sites","hreflang and Language Alternates on Static Sites",{"path":1547,"title":1548},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1550,"title":1551},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1553,"title":1554},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Flanguage-detection-and-redirects-at-the-edge","Language Detection and Redirects at the Edge",{"path":1556,"title":1557},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-eleventy-sites-with-the-i18n-plugin","Multilingual Eleventy Sites With the i18n Plugin",{"path":1559,"title":1560},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1562,"title":1563},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fright-to-left-layouts-on-static-sites","Right-to-Left Layouts on Static Sites",{"path":1565,"title":1566},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fsubdirectories-vs-subdomains-for-translated-static-sites","Subdirectories vs Subdomains for Translated Static Sites",{"path":1568,"title":1569},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Ftranslation-workflows-with-git-and-crowdin","Translation Workflows with Git and Crowdin",{"path":1571,"title":1572},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fcustom-domains-and-https-for-jekyll-on-github-pages","Custom Domains and HTTPS for Jekyll on GitHub Pages",{"path":1574,"title":1575},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1577,"title":1578},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Feleventy-vs-jekyll-for-markdown-heavy-blogs","Eleventy vs Jekyll for Markdown-Heavy Blogs",{"path":1580,"title":1581},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Ffixing-jekyll-builds-that-break-after-a-ruby-upgrade","Fixing Jekyll Builds That Break After a Ruby Upgrade",{"path":1583,"title":1584},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1586,"title":1587},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Freplacing-jekyll-plugins-when-migrating-to-eleventy","Replacing Jekyll Plugins When Migrating to Eleventy",{"path":1589,"title":1590},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds","Running Jekyll in Docker for Reproducible Builds",{"path":1592,"title":1593},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-on-github-pages-without-plugins","Running Jekyll on GitHub Pages Without Plugins",{"path":1595,"title":1596},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1598,"title":1599},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1601,"title":1602},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fauditing-content-parity-after-a-migration","Auditing Content Parity After a Migration",{"path":1604,"title":1605},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fconverting-front-matter-at-scale-during-migration","Converting Front Matter at Scale During Migration",{"path":1607,"title":1608},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1610,"title":1611},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fkeeping-redirects-working-after-an-ssg-migration","Keeping Redirects Working After an SSG Migration",{"path":1613,"title":1614},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-a-docs-site-from-jekyll-to-hugo","Migrating a Docs Site From Jekyll to Hugo",{"path":1616,"title":1617},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-a-wordpress-export-to-eleventy","Migrating a WordPress Export to Eleventy",{"path":1619,"title":1620},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1622,"title":1623},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1625,"title":1626},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-hugo-to-astro-without-breaking-urls","Migrating From Hugo to Astro Without Breaking URLs",{"path":1628,"title":1629},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-nextjs-pages-router-to-astro","Migrating from Next.js Pages Router to Astro",{"path":1631,"title":1632},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-wordpress-to-a-static-site-generator","Migrating WordPress to a Static Site Generator",{"path":1634,"title":1635},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fporting-shortcodes-and-includes-between-generators","Porting Shortcodes and Includes Between Generators",{"path":1637,"title":1638},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Frecovering-search-traffic-lost-after-a-generator-migration","Recovering Search Traffic Lost After a Generator Migration",{"path":1640,"title":1641},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Freplacing-gatsby-graphql-queries-during-a-migration","Replacing Gatsby GraphQL Queries During a Migration",{"path":1643,"title":1644},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export","Fixing 404s on Refresh in Next.js Static Export",{"path":1646,"title":1647},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fgenerating-sitemaps-and-rss-in-nextjs-static-export","Generating Sitemaps and RSS in Next.js Static Export",{"path":1649,"title":1650},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fhandling-dynamic-routes-in-nextjs-static-export","Handling Dynamic Routes in Next.js Static Export",{"path":1652,"title":1653},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1655,"title":1656},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fmigrating-from-gatsby-to-nextjs-static-export","Migrating from Gatsby to Next.js Static Export",{"path":1658,"title":1659},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fnextjs-app-router-static-export-limitations","Next.js App Router Static Export Limitations",{"path":1661,"title":1662},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fnextjs-static-export-vs-astro-for-marketing-sites","Next.js Static Export vs Astro for Marketing",{"path":1664,"title":1665},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fnextjs-static-export-vs-gatsby-for-existing-react-sites","Next.js Static Export vs Gatsby for Existing React Sites",{"path":1667,"title":1668},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Foptimizing-images-in-nextjs-static-export","Optimizing Images in Next.js Static Export",{"path":1670,"title":1671},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ftrailing-slash-and-basepath-in-nextjs-static-export","Trailing Slash and basePath in Next.js Static Export",{"path":1673,"title":1674},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fusing-mdx-in-nextjs-static-export","Using MDX in Next.js Static Export",{"path":1676,"title":1677},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Faccessible-search-ui-for-static-sites","Accessible Search UI for Static Sites",{"path":1679,"title":1680},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fadding-pagefind-to-an-astro-site","Adding Pagefind to an Astro Site",{"path":1682,"title":1683},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fbuilding-a-lunr-index-at-build-time-in-eleventy","Building a Lunr Index at Build Time in Eleventy",{"path":1685,"title":1686},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1688,"title":1689},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ffixing-missing-results-in-pagefind-indexes","Fixing Missing Results in Pagefind Indexes",{"path":1691,"title":1692},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1694,"title":1695},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1697,"title":1698},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1700,"title":1701},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1703,"title":1704},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-lunr-for-small-documentation-sites","Pagefind vs Lunr for Small Documentation Sites",{"path":1706,"title":1707},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fsearch-index-size-budgets-for-large-docs","Search Index Size Budgets for Large Docs",{"path":1709,"title":1710},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fself-hosting-typesense-for-a-static-site","Self-Hosting Typesense for a Static Site",{"path":1712,"title":1713},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1715,"title":1716},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fbest-ssg-for-technical-writers-without-coding-experience","Best SSG for Non-Developer Technical Writers",{"path":1718,"title":1719},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fchoosing-an-ssg-for-a-marketing-site-with-non-technical-editors","Choosing an SSG for a Marketing Site with Non-Technical Editors",{"path":1721,"title":1722},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fchoosing-an-ssg-for-api-reference-documentation","Choosing an SSG for API Reference Documentation",{"path":1724,"title":1725},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1727,"title":1728},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fgatsby-vs-astro-for-content-sites-in-2026","Gatsby vs Astro for Content Sites in 2026",{"path":1730,"title":1731},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1733,"title":1734},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fpicking-an-ssg-for-a-multi-language-documentation-site","Picking an SSG for a Multi-Language Docs Site",{"path":1736,"title":1737},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fscoring-ssg-long-term-maintenance-risk","Scoring SSG Long-Term Maintenance Risk",{"path":1739,"title":1740},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fssg-selection-checklist-for-engineering-teams","SSG Selection Checklist for Engineering Teams",{"path":1742,"title":1743},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Ftotal-cost-of-ownership-for-static-site-generators","Total Cost of Ownership for Static Site Generators",{"path":1745,"title":1746},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fwhen-a-static-site-generator-is-the-wrong-choice","When a Static Site Generator Is the Wrong Choice",{"path":1748,"title":1749},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fadding-json-ld-structured-data-at-build-time","Adding JSON-LD Structured Data at Build Time",{"path":1751,"title":1752},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fcanonical-urls-and-duplicate-content-on-static-sites","Canonical URLs and Duplicate Content on Static Sites",{"path":1754,"title":1755},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Ffixing-pages-crawled-but-not-indexed-on-static-sites","Fixing Pages Crawled but Not Indexed on Static Sites",{"path":1757,"title":1758},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Ffixing-soft-404s-on-static-hosts","Fixing Soft 404s on Static Hosts",{"path":1760,"title":1761},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fgenerating-breadcrumb-structured-data-in-astro","Generating Breadcrumb Structured Data in Astro",{"path":1763,"title":1764},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fgenerating-sitemaps-for-large-static-sites","Generating Sitemaps for Large Static Sites",{"path":1766,"title":1767},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1769,"title":1770},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Frobots-txt-and-noindex-for-preview-and-staging","robots.txt and noindex for Preview and Staging",{"path":1772,"title":1773},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Frss-and-atom-feeds-for-static-blogs","RSS and Atom Feeds for Static Blogs",{"path":1775,"title":1776},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fseo-safe-pagination-and-tag-pages","SEO-Safe Pagination and Tag Pages",{"path":1778,"title":1779},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-busting-with-content-hashed-filenames","Cache Busting with Content-Hashed Filenames",{"path":1781,"title":1782},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-for-static-sites-in-nginx","Cache-Control Headers for Static Sites in Nginx",{"path":1784,"title":1785},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-on-s3-and-cloudfront","Cache-Control Headers on S3 and CloudFront",{"path":1787,"title":1788},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-on-vercel-for-static-sites","Cache-Control Headers on Vercel for Static Sites",{"path":1790,"title":1791},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-keys-and-query-strings-on-cdns","Cache Keys and Query Strings on CDNs",{"path":1793,"title":1794},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcaching-404s-and-redirects-at-the-edge","Caching 404s and Redirects at the Edge",{"path":1796,"title":1797},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcloudflare-vs-cloudfront-cache-hit-ratios-for-static-sites","Cloudflare vs CloudFront Cache Hit Ratios for Static Sites",{"path":1799,"title":1800},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ffixing-stale-html-after-deploys-on-cloudflare","Fixing Stale HTML After Deploys on Cloudflare",{"path":1802,"title":1803},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1805,"title":1806},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fpurging-the-cdn-cache-after-a-static-deploy","Purging the CDN Cache After a Static Deploy",{"path":1808,"title":1809},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fsetting-cache-control-headers-on-cloudflare-pages","Cache-Control Headers on Cloudflare Pages",{"path":1811,"title":1812},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fsetting-up-proper-cache-headers-on-netlify","Proper Cache Headers on Netlify for SSGs",{"path":1814,"title":1815},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fstale-while-revalidate-for-static-html","Stale-While-Revalidate for Static HTML",{"path":1817,"title":1818},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1820,"title":1821},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fcode-splitting-and-module-preload-in-vite-based-ssgs","Code Splitting and Module Preload in Vite-Based SSGs",{"path":1823,"title":1824},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ffixing-missing-tailwind-classes-in-production-builds","Fixing Missing Tailwind Classes in Production Builds",{"path":1826,"title":1827},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ffixing-unused-javascript-warnings-on-static-pages","Fixing Unused JavaScript Warnings on Static Pages",{"path":1829,"title":1830},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1832,"title":1833},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Finlining-critical-css-on-static-sites","Inlining Critical CSS on Static Sites",{"path":1835,"title":1836},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fkeeping-tailwind-css-output-small-on-static-sites","Keeping Tailwind CSS Output Small on Static Sites",{"path":1838,"title":1839},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fminifying-html-css-and-js-in-eleventy","Minifying HTML, CSS and JS in Eleventy",{"path":1841,"title":1842},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fprecompressing-assets-with-brotli-and-zstd","Precompressing Assets with Brotli and Zstd",{"path":1844,"title":1845},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fpurging-unused-css-with-tailwind-and-lightningcss","Purging Unused CSS with Tailwind and Lightning CSS",{"path":1847,"title":1848},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fsvg-icon-sprites-vs-inline-icons","SVG Icon Sprites vs Inline Icons",{"path":1850,"title":1851},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins","Tailwind v4 in Astro Without PostCSS Plugins",{"path":1853,"title":1854},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Fcls-from-client-side-rendered-components","CLS from Client-Side Rendered Components",{"path":1856,"title":1857},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Fdebugging-cls-with-the-layout-instability-api","Debugging CLS with the Layout Instability API",{"path":1859,"title":1860},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Feliminating-layout-shift-from-web-fonts","Eliminating Layout Shift From Web Fonts",{"path":1862,"title":1863},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-cookie-banners","Fixing CLS from Cookie Banners",{"path":1865,"title":1866},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-dynamic-table-of-contents-widgets","Fixing CLS From Dynamic Table of Contents Widgets",{"path":1868,"title":1869},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-images-without-dimensions-in-markdown","Fixing CLS From Images Without Dimensions in Markdown",{"path":1871,"title":1872},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-late-loading-embeds","Fixing CLS From Late-Loading Embeds",{"path":1874,"title":1875},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-sticky-headers-and-anchor-links","Fixing CLS from Sticky Headers and Anchor Links",{"path":1877,"title":1878},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1880,"title":1881},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Fmeasuring-cls-in-the-field-with-web-vitals-js","Measuring CLS in the Field With web-vitals.js",{"path":1883,"title":1884},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Freserving-space-for-ad-and-promo-slots","Reserving Space for Ad and Promo Slots",{"path":1886,"title":1887},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Freserving-space-for-images-and-embeds-to-stop-layout-shift","Reserving Space for Images and Embeds",{"path":1889,"title":1890},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":1892,"title":1893},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffixing-invisible-text-while-web-fonts-load","Fixing Invisible Text While Web Fonts Load",{"path":1895,"title":1896},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1898,"title":1899},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1901,"title":1902},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fmetric-matched-fallback-fonts-with-size-adjust","Metric-Matched Fallback Fonts with size-adjust",{"path":1904,"title":1905},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1907,"title":1908},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fself-hosted-fonts-vs-google-fonts-for-static-sites","Self-Hosted Fonts vs Google Fonts for Static Sites",{"path":1910,"title":1911},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fself-hosting-google-fonts-to-eliminate-layout-shift","Self-Host Google Fonts to Eliminate Layout Shift",{"path":1913,"title":1914},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fsubsetting-variable-fonts-for-faster-first-render","Subsetting Variable Fonts for Faster First Render",{"path":1916,"title":1917},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fusing-system-font-stacks-to-skip-webfonts","Using System Font Stacks to Skip Web Fonts",{"path":1919,"title":1920},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":1922,"title":1923},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fart-direction-with-the-picture-element","Art Direction with the Picture Element",{"path":1925,"title":1926},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":1928,"title":1929},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fbuilding-an-image-cdn-pipeline-for-static-sites","Building an Image CDN Pipeline for Static Sites",{"path":1931,"title":1932},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":1934,"title":1935},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Ffixing-blurry-images-from-astro-assets-resizing","Fixing Blurry Images From astro:assets Resizing",{"path":1937,"title":1938},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fgenerating-open-graph-images-at-build-time","Generating Open Graph Images at Build Time",{"path":1940,"title":1941},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1943,"title":1944},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Flazy-loading-images-without-hurting-lcp","Lazy-Loading Images Without Hurting LCP",{"path":1946,"title":1947},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Foptimizing-webp-images-in-hugo-without-plugins","Optimizing WebP Images in Hugo Without Plugins",{"path":1949,"title":1950},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fresponsive-images-with-srcset-in-eleventy","Responsive Images with srcset in Eleventy",{"path":1952,"title":1953},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fserving-astro-images-through-cloudflare-image-resizing","Serving Astro Images Through Cloudflare Image Resizing",{"path":1955,"title":1956},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fserving-avif-with-fallbacks-on-static-sites","Serving AVIF With Fallbacks on Static Sites",{"path":1958,"title":1959},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1961,"title":1962},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1964,"title":1965},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fbreaking-up-long-tasks-on-static-sites","Breaking Up Long Tasks on Static Sites",{"path":1967,"title":1968},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fdeferring-hydration-with-client-visible-in-astro","Deferring Hydration with client:visible in Astro",{"path":1970,"title":1971},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Ffixing-hydration-mismatch-errors-in-astro-islands","Fixing Hydration Mismatch Errors in Astro Islands",{"path":1973,"title":1974},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Ffixing-poor-inp-on-static-pages-with-heavy-widgets","Fixing Poor INP on Static Pages With Heavy Widgets",{"path":1976,"title":1977},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fhow-to-reduce-bundle-size-in-eleventy-builds","How to Reduce Bundle Size in Eleventy Builds",{"path":1979,"title":1980},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1982,"title":1983},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fmeasuring-inp-on-static-sites-with-real-user-monitoring","Measuring INP on Static Sites with RUM",{"path":1985,"title":1986},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":1988,"title":1989},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1991,"title":1992},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":1994,"title":1995},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Feliminating-render-blocking-css-on-static-sites","Eliminating Render-Blocking CSS on Static Sites",{"path":1997,"title":1998},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-on-text-heavy-documentation-pages","Fixing LCP on Text-Heavy Documentation Pages",{"path":2000,"title":2001},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-regressions-caused-by-cookie-consent-tools","Fixing LCP Regressions Caused by Cookie Consent Tools",{"path":2003,"title":2004},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-when-the-hero-is-a-background-image","Fixing LCP When the Hero Is a Background Image",{"path":2006,"title":2007},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-slow-lcp-on-pages-with-embedded-video","Fixing Slow LCP on Pages With Embedded Video",{"path":2009,"title":2010},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fimproving-ttfb-for-static-html","Improving TTFB for Static HTML",{"path":2012,"title":2013},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":2015,"title":2016},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fmeasuring-lcp-subparts-with-devtools","Measuring LCP Subparts with DevTools",{"path":2018,"title":2019},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Foptimizing-lcp-on-astro-with-priority-hints","Optimizing LCP on Astro with Priority Hints",{"path":2021,"title":2022},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Freducing-lcp-from-hero-images-on-static-sites","Reducing LCP from Hero Images on Static Sites",{"path":2024,"title":2025},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fcomparing-lab-and-field-data-with-crux","Comparing Lab and Field Data with CrUX",{"path":2027,"title":24},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci",{"path":2029,"title":2030},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Flighthouse-ci-vs-webpagetest-for-regression-gates","Lighthouse CI vs WebPageTest for Regression Gates",{"path":2032,"title":2033},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fmeasuring-web-vitals-in-playwright-tests","Measuring Web Vitals in Playwright Tests",{"path":2035,"title":2036},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2038,"title":2039},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fperformance-testing-on-throttled-mobile-profiles","Performance Testing on Throttled Mobile Profiles",{"path":1372,"title":5},{"path":2042,"title":1312},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Frunning-webpagetest-scripts-against-preview-deploys",{"path":2044,"title":41},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site",{"path":2046,"title":2047},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-bundle-size-per-pull-request","Tracking Bundle Size per Pull Request",{"path":2049,"title":2050},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2052,"title":995},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fwriting-a-performance-budget-that-fails-builds",{"path":2054,"title":2055},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2057,"title":2058},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2060,"title":2061},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2063,"title":2064},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffixing-wasted-preloads-flagged-by-chrome","Fixing Wasted Preloads Flagged by Chrome",{"path":2066,"title":2067},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2069,"title":2070},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2072,"title":2073},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fpreconnect-vs-dns-prefetch-on-static-sites","Preconnect vs DNS-Prefetch on Static Sites",{"path":2075,"title":2076},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2078,"title":2079},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fview-transitions-in-astro-without-hurting-vitals","View Transitions in Astro Without Hurting Vitals",{"path":2081,"title":2082},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fview-transitions-on-multi-page-static-sites","View Transitions on Multi-Page Static Sites",{"path":2084,"title":2085},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fauditing-third-party-scripts-with-lighthouse","Auditing Third-Party Scripts With Lighthouse",{"path":2087,"title":2088},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Ffacades-for-chat-widgets-and-maps","Facades for Chat Widgets and Maps",{"path":2090,"title":2091},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Ffixing-main-thread-blocking-from-chat-widgets","Fixing Main-Thread Blocking From Chat Widgets",{"path":2093,"title":2094},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2096,"title":2097},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Flazy-loading-youtube-embeds-on-static-sites","Lazy-Loading YouTube Embeds on Static Sites",{"path":2099,"title":2100},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Floading-google-tag-manager-without-hurting-inp","Loading Google Tag Manager Without Hurting INP",{"path":2102,"title":2103},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fmeasuring-third-party-cost-with-request-blocking","Measuring Third-Party Cost with Request Blocking",{"path":2105,"title":2106},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fprivacy-friendly-analytics-compared-by-page-weight","Privacy-Friendly Analytics Compared by Page Weight",{"path":2108,"title":2109},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Frunning-third-party-scripts-in-a-web-worker-with-partytown","Running Third-Party Scripts in a Web Worker with Partytown",{"path":2111,"title":2112},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fself-hosting-analytics-to-cut-third-party-requests","Self-Hosting Analytics to Cut Third-Party Requests",{"path":2114,"title":2115},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2117,"title":2118},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2120,"title":2121},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2123,"title":2124},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2126,"title":2127},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcustom-domains-and-tls-on-cloudflare-pages","Custom Domains and TLS on Cloudflare Pages",{"path":2129,"title":2130},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-astro-to-cloudflare-workers-static-assets","Deploying Astro to Cloudflare Workers Static Assets",{"path":2132,"title":2133},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-hugo-to-cloudflare-pages-and-workers","Deploying Hugo to Cloudflare Pages and Workers",{"path":2135,"title":2136},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-to-cloudflare-from-github-actions-with-wrangler","Deploying to Cloudflare From GitHub Actions With Wrangler",{"path":2138,"title":2139},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2141,"title":2142},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2144,"title":2145},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fmigrating-from-cloudflare-pages-to-workers-static-assets","Migrating from Cloudflare Pages to Workers Static Assets",{"path":2147,"title":2148},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2150,"title":2151},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2153,"title":2154},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fdocs-as-code-review-workflow-for-writers","Docs-as-Code Review Workflow for Writers",{"path":2156,"title":2157},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2159,"title":2160},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fgit-based-cms-options-for-static-sites-compared","Git-Based CMS Options for Static Sites Compared",{"path":2162,"title":2163},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2165,"title":2166},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fmanaging-images-in-docs-as-code-repos","Managing Images in Docs-as-Code Repos",{"path":2168,"title":2169},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2171,"title":2172},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2174,"title":2175},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduling-content-publication-with-cron-triggered-builds","Scheduling Content Publication With Cron-Triggered Builds",{"path":2177,"title":2178},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fwiring-a-headless-cms-to-a-static-build","Wiring a Headless CMS to a Static Build",{"path":2180,"title":2181},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2183,"title":2184},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fcaching-node-modules-in-github-actions-for-faster-ssg-builds","Caching node_modules in GitHub Actions",{"path":2186,"title":2187},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2189,"title":2190},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2192,"title":2193},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-multiple-environments-from-one-workflow","Deploying to Multiple Environments From One Workflow",{"path":2195,"title":2196},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Ffixing-flaky-static-site-builds-in-github-actions","Fixing Flaky Static Site Builds in GitHub Actions",{"path":2198,"title":2199},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fhow-to-set-up-github-actions-for-hugo-deployments","GitHub Actions for Hugo Deployments",{"path":2201,"title":2202},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2204,"title":2205},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2207,"title":2208},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2210,"title":2211},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpublishing-any-generator-to-github-pages-with-actions","Publishing Any Generator to GitHub Pages With Actions",{"path":2213,"title":2214},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2216,"title":2217},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fbuild-caching-on-netlify-and-vercel","Build Caching on Netlify and Vercel",{"path":2219,"title":2220},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions","Caching Hugo Builds in GitHub Actions",{"path":2222,"title":2223},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2225,"title":2226},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2228,"title":2229},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Ffixing-stale-pages-from-incremental-builds","Fixing Stale Pages From Incremental Builds",{"path":2231,"title":2232},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fincremental-builds-in-astro-with-the-content-layer","Incremental Builds in Astro with the Content Layer",{"path":2234,"title":2235},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fincremental-rebuild-times-across-astro-eleventy-and-hugo","Incremental Rebuild Times Across Astro, Eleventy and Hugo",{"path":2237,"title":2238},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2240,"title":2241},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fmeasuring-build-time-regressions-in-ci","Measuring Build-Time Regressions in CI",{"path":2243,"title":2244},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos","Remote Caching with Turborepo for SSG Monorepos",{"path":2246,"title":2247},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fsharing-build-cache-across-ci-runners","Sharing Build Cache Across CI Runners",{"path":2249,"title":2250},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2252,"title":2253},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2255,"title":2256},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fbuilding-a-core-web-vitals-dashboard-from-rum-data","Building a Core Web Vitals Dashboard from RUM Data",{"path":2258,"title":2259},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fcrawling-for-broken-links-on-a-schedule","Crawling for Broken Links on a Schedule",{"path":2261,"title":2262},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ffinding-the-cause-of-a-sudden-field-lcp-drop","Finding the Cause of a Sudden Field LCP Drop",{"path":2264,"title":2265},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2267,"title":2268},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2270,"title":2271},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2273,"title":2274},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Freal-user-error-tracking-on-static-sites","Real-User Error Tracking on Static Sites",{"path":2276,"title":2277},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2279,"title":2280},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2282,"title":2283},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fuptime-and-synthetic-checks-for-static-sites","Uptime and Synthetic Checks for Static Sites",{"path":2285,"title":2286},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fbandwidth-pricing-for-static-sites-across-netlify-vercel-and-cloudflare","Static Site Bandwidth Pricing: Netlify, Vercel, Cloudflare",{"path":2288,"title":2289},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-redirects-on-vercel-for-static-sites","Configuring Redirects on Vercel for Static Sites",{"path":2291,"title":2292},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2294,"title":2295},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fdeploying-astro-to-vercel-as-a-fully-static-site","Deploying Astro to Vercel as a Fully Static Site",{"path":2297,"title":2298},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Ffixing-netlify-builds-that-exceed-the-time-limit","Fixing Netlify Builds That Exceed the Time Limit",{"path":2300,"title":2301},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Ffixing-vercel-builds-that-run-out-of-memory","Fixing Vercel Builds That Run Out of Memory",{"path":2303,"title":2304},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2306,"title":2307},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2309,"title":2310},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2312,"title":2313},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites","Netlify Redirects and Rewrites for Static Sites",{"path":2315,"title":2316},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fsetting-up-deploy-previews-on-netlify-for-every-pull-request","Netlify Deploy Previews for Every Pull Request",{"path":2318,"title":2319},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs","Vercel Build Output API for Custom SSGs",{"path":2321,"title":2322},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-isr-vs-static-generation-for-ssgs","Vercel ISR vs Static Generation for SSGs",{"path":2324,"title":2325},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fautomating-preview-deploy-pipelines-with-github-actions","Automating Preview Deploy Pipelines with GitHub Actions",{"path":2327,"title":2328},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2330,"title":2331},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2333,"title":2334},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Ffixing-preview-deploys-leaking-into-search-results","Fixing Preview Deploys Leaking Into Search Results",{"path":2336,"title":2337},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2339,"title":2340},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2342,"title":2343},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2345,"title":2346},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2348,"title":2349},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpull-request-previews-for-github-pages-sites","Pull Request Previews for GitHub Pages Sites",{"path":2351,"title":2352},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2354,"title":2355},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2357,"title":2358},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fblue-green-deploys-for-static-sites","Blue-Green Deploys for Static Sites",{"path":2360,"title":2361},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2363,"title":2364},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2366,"title":2367},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2369,"title":2370},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fkeeping-old-assets-alive-after-deploy","Keeping Old Assets Alive After Deploy",{"path":2372,"title":2373},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2375,"title":2376},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frecovering-from-a-deploy-that-deleted-live-assets","Recovering From a Deploy That Deleted Live Assets",{"path":2378,"title":2379},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-a-bad-static-deploy-in-under-a-minute","Rolling Back a Bad Static Deploy in Under a Minute",{"path":2381,"title":2382},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-netlify-deploys-from-the-cli-and-api","Rolling Back Netlify Deploys From the CLI and API",{"path":2384,"title":2385},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-s3-and-cloudfront-deploys-with-versioned-prefixes","Rolling Back S3 and CloudFront Deploys With Versioned Prefixes",{"path":2387,"title":2388},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frunning-smoke-tests-against-a-preview-url","Running Smoke Tests Against a Preview URL",{"path":2390,"title":2391},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2393,"title":2394},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2396,"title":2397},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Ffixing-content-security-policy-violations-from-inline-scripts","Fixing Content Security Policy Violations From Inline Scripts",{"path":2399,"title":2400},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Ffixing-mixed-content-warnings-after-moving-to-https","Fixing Mixed Content Warnings After Moving to HTTPS",{"path":2402,"title":2403},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fhash-based-csp-for-inline-scripts-in-astro","Hash-Based CSP for Inline Scripts in Astro",{"path":2405,"title":2406},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2408,"title":2409},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2411,"title":2412},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2414,"title":2415},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecurity-headers-for-static-sites-served-by-caddy","Security Headers for Static Sites Served by Caddy",{"path":2417,"title":2418},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecurity-headers-on-vercel-for-static-sites","Security Headers on Vercel for Static Sites",{"path":2420,"title":2421},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecurity-txt-and-disclosure-for-static-sites","security.txt and Disclosure for Static Sites",{"path":2423,"title":2424},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2426,"title":2427},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fwriting-a-content-security-policy-for-a-static-site","Writing a Content Security Policy for a Static Site",{"path":2429,"title":2430},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2432,"title":2433},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2435,"title":2436},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2438,"title":2439},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fdeploying-a-static-site-to-s3-and-cloudfront","Deploying a Static Site to S3 and CloudFront",{"path":2441,"title":2442},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2444,"title":2445},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2447,"title":2448},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2450,"title":2451},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx","Serving a Static Site From a Docker Container With Nginx",{"path":2453,"title":2454},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy-and-automatic-https","Serving a Static Site With Caddy and Automatic HTTPS",{"path":2456,"title":2457},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2459,"title":2460},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2462,"title":2463},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2465,"title":2466},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2468,"title":2469},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fadding-a-contact-form-with-cloudflare-workers","Adding a Contact Form with Cloudflare Workers",{"path":2471,"title":2472},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Ffixing-cold-starts-in-netlify-functions-for-forms","Fixing Cold Starts in Netlify Functions for Forms",{"path":2474,"title":2475},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fhandling-form-submissions-on-a-static-site","Handling Form Submissions on a Static Site",{"path":2477,"title":2478},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2480,"title":2481},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2483,"title":2484},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2486,"title":2487},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2489,"title":2490},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fproxying-third-party-apis-from-an-edge-function","Proxying Third-Party APIs from an Edge Function",{"path":2492,"title":2493},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2495,"title":2496},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Faccessibility-testing-with-axe-and-pa11y-in-ci","Accessibility Testing with axe and pa11y in CI",{"path":2498,"title":2499},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fend-to-end-tests-for-static-sites-with-playwright","End-to-End Tests for Static Sites with Playwright",{"path":2501,"title":2502},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ffixing-flaky-playwright-tests-against-preview-deploys","Fixing Flaky Playwright Tests Against Preview Deploys",{"path":2504,"title":2505},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2507,"title":2508},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2510,"title":2511},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2513,"title":2514},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-search-and-navigation-flows-with-playwright","Testing Search and Navigation Flows With Playwright",{"path":2516,"title":2517},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2519,"title":2520},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2522,"tools":2526},{"label":2523,"plural":2524,"u":2525},"Fix","Fixes","\u002Fguides\u002Ffixes\u002F",[2527],{"label":2528,"u":2529},"Lighthouse","\u002Ftools\u002Flighthouse\u002F",1790943192064]