[{"data":1,"prerenderedAt":2721},["ShallowReactive",2],{"page:\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci":3,"all-docs-nav":1585,"filed:\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci":2720},{"id":4,"title":5,"body":6,"breadcrumb":1563,"dateModified":1570,"datePublished":1570,"description":1571,"extension":1572,"faq":1573,"meta":1579,"navigation":1580,"path":1581,"seo":1582,"slug":12,"stem":1583,"type":832,"__hash__":1584},"content\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Findex.md","Performance Budgets and Lighthouse CI",{"type":7,"value":8,"toc":1541},"minimark",[9,13,17,46,226,231,234,241,252,258,261,383,391,395,406,776,782,907,911,914,921,934,1074,1078,1089,1096,1103,1107,1110,1113,1120,1124,1127,1146,1152,1162,1168,1179,1183,1186,1192,1198,1210,1217,1221,1228,1232,1235,1242,1249,1252,1256,1259,1342,1345,1349,1389,1393,1410,1414,1419,1422,1426,1429,1433,1436,1440,1443,1447,1450,1454,1537],[10,11,5],"h1",{"id":12},"performance-budgets-and-lighthouse-ci",[14,15,16],"p",{},"Static sites start fast and get slower one pull request at a time. An analytics snippet here, a web font weight there, a hero image someone forgot to resize, a component library imported whole for one button — none of them looks like a regression in review, and together they turn a site that scored 100 into one that fails Core Web Vitals on mobile. The only reliable defence is to make performance a check that runs on every change and fails when a limit is crossed, exactly like a test.",[14,18,19,20,25,26,30,31,35,36,40,41,45],{},"This topic covers that defence end to end: choosing budgets, running ",[21,22,24],"a",{"href":23},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site\u002F","Lighthouse CI"," against preview deploys, keeping results stable enough to trust, tracking bundle size per pull request, and checking lab numbers against field data. It sits inside ",[21,27,29],{"href":28},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002F","Performance Optimization & Core Web Vitals for SSGs",", and it is the enforcement layer for everything else in that section — the ",[21,32,34],{"href":33},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002F","LCP",", ",[21,37,39],{"href":38},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002F","CLS"," and ",[21,42,44],{"href":43},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002F","hydration"," work only stays done if something checks it.",[47,48,49,222],"figure",{},[50,51,58,59,58,63,58,67,58,74,58,207],"svg",{"viewBox":52,"role":53,"ariaLabelledBy":54,"xmlns":57},"0 0 780 300","img",[55,56],"pbl-loop-title","pbl-loop-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[60,61,62],"title",{"id":55},"The performance feedback loop",[64,65,66],"desc",{"id":56},"A loop of five stages. A pull request builds and deploys a preview. Lighthouse CI runs three times per template URL. Results are compared against a budget of bytes and timings. A failing budget blocks the merge, a passing one merges. After release, field data from CrUX and real-user monitoring feeds back into adjusting the budget.",[68,69],"rect",{"x":70,"y":70,"width":71,"height":72,"fill":73},"0","780","300","#ffffff",[75,76,78,79,78,87,78,97,78,103,78,109,78,115,78,118,78,121,78,127,78,131,78,134,78,141,78,146,78,152,78,156,78,160,78,165,78,169,78,172,78,176,78,179,58],"g",{"style":77},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[80,81,86],"text",{"x":82,"y":83,"fill":84,"style":85},"390","28","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Lab checks gate the merge; field data tunes the budget",[68,88],{"x":89,"y":90,"width":91,"height":92,"rx":93,"fill":94,"stroke":95,"style":96},"30","70","140","56","10","#f8fafc","#d9e2ef","stroke-width:1.5px",[80,98,102],{"x":99,"y":100,"fill":84,"style":101},"100","94","font-weight:700;text-anchor:middle","Pull request",[80,104,108],{"x":99,"y":105,"fill":106,"style":107},"112","#556071","font-size:11px;text-anchor:middle","preview deploy",[68,110],{"x":111,"y":90,"width":112,"height":92,"rx":93,"fill":113,"opacity":114,"stroke":113,"style":96},"210","150","#1982c4","0.14",[80,116,24],{"x":117,"y":100,"fill":84,"style":101},"285",[80,119,120],{"x":117,"y":105,"fill":106,"style":107},"3 runs × 6 URLs",[68,122],{"x":123,"y":90,"width":112,"height":92,"rx":93,"fill":124,"opacity":125,"stroke":126,"style":96},"400","#ffca3a","0.26","#a97b00",[80,128,130],{"x":129,"y":100,"fill":84,"style":101},"475","Budget assert",[80,132,133],{"x":129,"y":105,"fill":106,"style":107},"bytes + timings",[68,135],{"x":136,"y":137,"width":112,"height":138,"rx":93,"fill":139,"opacity":114,"stroke":140,"style":96},"600","40","46","#ff595e","#d83b41",[80,142,145],{"x":143,"y":144,"fill":84,"style":101},"675","68","Block merge",[68,147],{"x":136,"y":148,"width":112,"height":138,"rx":93,"fill":149,"opacity":150,"stroke":151,"style":96},"110","#8ac926","0.18","#5a8a16",[80,153,155],{"x":143,"y":154,"fill":84,"style":101},"138","Merge + release",[68,157],{"x":123,"y":158,"width":158,"height":92,"rx":93,"fill":159,"opacity":114,"stroke":159,"style":96},"200","#6a4c93",[80,161,164],{"x":162,"y":163,"fill":84,"style":101},"500","224","Field data",[80,166,168],{"x":162,"y":167,"fill":106,"style":107},"242","CrUX + RUM, p75, 28 days",[68,170],{"x":171,"y":158,"width":158,"height":92,"rx":93,"fill":94,"stroke":95,"style":96},"130",[80,173,175],{"x":174,"y":163,"fill":84,"style":101},"230","Adjust budget",[80,177,178],{"x":174,"y":167,"fill":106,"style":107},"tighten what the field allows",[75,180,183,184,183,189,183,192,183,195,183,198,183,201,183,204,78],{"stroke":106,"fill":181,"style":182},"none","stroke-width:2px","\n      ",[185,186],"path",{"d":187,"style":188},"M172 98 L206 98","marker-end:url(#pbl-loop-arrow)",[185,190],{"d":191,"style":188},"M362 98 L396 98",[185,193],{"d":194,"style":188},"M552 90 L596 66",[185,196],{"d":197,"style":188},"M552 106 L596 130",[185,199],{"d":200,"style":188},"M675 158 L560 198",[185,202],{"d":203,"style":188},"M398 228 L334 228",[185,205],{"d":206,"style":188},"M230 198 L400 128",[208,209,78,210,58],"defs",{},[211,212,183,219,78],"marker",{"id":213,"viewBox":214,"refX":215,"refY":216,"markerWidth":217,"markerHeight":217,"orient":218},"pbl-loop-arrow","0 0 10 10","8","5","7","auto-start-reverse",[185,220],{"d":221,"fill":106},"M0 0 L10 5 L0 10 z",[223,224,225],"figcaption",{},"Lab checks are fast and deterministic enough to block a merge; field data is slow and noisy but tells you whether the budget protects real readers.",[227,228,230],"h2",{"id":229},"choosing-what-to-budget","Choosing What to Budget",[14,232,233],{},"A useful budget has three kinds of limit, because each catches a different class of regression.",[14,235,236,240],{},[237,238,239],"strong",{},"Byte budgets"," limit what ships: total JavaScript, total CSS, image bytes on the page, web font bytes, request count. They are deterministic — the same build always produces the same numbers — so they never fail from noise. They catch the most common regressions directly: a new dependency, an unoptimised image, an extra font weight.",[14,242,243,246,247,251],{},[237,244,245],{},"Timing budgets"," limit what the reader experiences in the lab: Largest Contentful Paint, Total Blocking Time (the lab proxy for INP), Cumulative Layout Shift, Speed Index. They catch problems bytes miss, such as a render-blocking stylesheet or a script that runs a long task, but they vary between runs and need care — see ",[21,248,250],{"href":249},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci\u002F","Reducing Lighthouse Score Variance in CI",".",[14,253,254,257],{},[237,255,256],{},"Rule-based assertions"," check Lighthouse audits pass: images have explicit dimensions, text stays visible during font load, no unused preloads, no legacy JavaScript. They catch classes of mistake rather than amounts.",[14,259,260],{},"A starting budget for a content-focused static site, derived from what a well-built Astro, Eleventy or Hugo site actually ships:",[262,263,264,283],"table",{},[265,266,267],"thead",{},[268,269,270,274,277,280],"tr",{},[271,272,273],"th",{},"Limit",[271,275,276],{},"Error at",[271,278,279],{},"Warn at",[271,281,282],{},"Why",[284,285,286,301,315,329,342,356,370],"tbody",{},[268,287,288,292,295,298],{},[289,290,291],"td",{},"Script bytes (compressed)",[289,293,294],{},"150 KB",[289,296,297],{},"100 KB",[289,299,300],{},"Main-thread cost scales with JS; most content pages need far less",[268,302,303,306,309,312],{},[289,304,305],{},"Stylesheet bytes",[289,307,308],{},"60 KB",[289,310,311],{},"40 KB",[289,313,314],{},"Render-blocking by default",[268,316,317,320,323,326],{},[289,318,319],{},"Font bytes",[289,321,322],{},"120 KB",[289,324,325],{},"80 KB",[289,327,328],{},"Delays text and can shift layout",[268,330,331,334,337,339],{},[289,332,333],{},"Image bytes, above the fold",[289,335,336],{},"250 KB",[289,338,294],{},[289,340,341],{},"Dominates LCP on image-led templates",[268,343,344,347,350,353],{},[289,345,346],{},"Lab LCP (mobile preset)",[289,348,349],{},"2.5 s",[289,351,352],{},"2.0 s",[289,354,355],{},"Matches the field \"good\" threshold with margin",[268,357,358,361,364,367],{},[289,359,360],{},"Total Blocking Time",[289,362,363],{},"300 ms",[289,365,366],{},"150 ms",[289,368,369],{},"Lab proxy for INP",[268,371,372,374,377,380],{},[289,373,39],{},[289,375,376],{},"0.1",[289,378,379],{},"0.05",[289,381,382],{},"Field threshold",[14,384,385,386,390],{},"Set these from your current numbers, not from aspiration. A budget the site already fails is a budget the team learns to ignore. Start at current values plus a small margin, fix regressions as they appear, and tighten each quarter. ",[21,387,389],{"href":388},"\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"," turns this table into a working configuration.",[227,392,394],{"id":393},"running-lighthouse-ci-on-preview-deploys","Running Lighthouse CI on Preview Deploys",[14,396,397,398,402,403,405],{},"Lighthouse CI (",[399,400,401],"code",{},"@lhci\u002Fcli",") runs Lighthouse against a set of URLs, asserts against a budget, and uploads reports. For a static site, run it against the ",[237,404,108],{},", not a local server: the preview has the real CDN, compression, caching headers and redirects, all of which affect the numbers.",[407,408,413],"pre",{"className":409,"code":410,"language":411,"meta":412,"style":412},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F lighthouserc.js\nmodule.exports = {\n  ci: {\n    collect: {\n      url: [\n        `${process.env.PREVIEW_URL}\u002F`,\n        `${process.env.PREVIEW_URL}\u002Fguides\u002F`,\n        `${process.env.PREVIEW_URL}\u002Fguides\u002Fdeploying-hugo\u002F`,\n        `${process.env.PREVIEW_URL}\u002Fblog\u002F2026\u002Fcache-headers\u002F`,\n        `${process.env.PREVIEW_URL}\u002Freference\u002Fconfig\u002F`,\n      ],\n      numberOfRuns: 3,\n      settings: { preset: 'desktop' === process.env.LH_PRESET ? 'desktop' : undefined },\n    },\n    assert: {\n      assertions: {\n        'resource-summary:script:size': ['error', { maxNumericValue: 153600 }],\n        'largest-contentful-paint': ['error', { maxNumericValue: 2500, aggregationMethod: 'median' }],\n        'total-blocking-time': ['warn', { maxNumericValue: 150, aggregationMethod: 'median' }],\n        'cumulative-layout-shift': ['error', { maxNumericValue: 0.1 }],\n        'unsized-images': 'error',\n        'font-display': 'error',\n      },\n    },\n    upload: { target: 'temporary-public-storage' },\n  },\n};\n","js","",[399,414,415,424,444,450,456,462,488,508,528,548,568,574,585,618,624,630,636,657,680,701,717,730,742,748,753,764,770],{"__ignoreMap":412},[416,417,420],"span",{"class":418,"line":419},"line",1,[416,421,423],{"class":422},"sJ8bj","\u002F\u002F lighthouserc.js\n",[416,425,427,431,434,437,441],{"class":418,"line":426},2,[416,428,430],{"class":429},"sj4cs","module",[416,432,251],{"class":433},"sVt8B",[416,435,436],{"class":429},"exports",[416,438,440],{"class":439},"szBVR"," =",[416,442,443],{"class":433}," {\n",[416,445,447],{"class":418,"line":446},3,[416,448,449],{"class":433},"  ci: {\n",[416,451,453],{"class":418,"line":452},4,[416,454,455],{"class":433},"    collect: {\n",[416,457,459],{"class":418,"line":458},5,[416,460,461],{"class":433},"      url: [\n",[416,463,465,469,472,474,477,479,482,485],{"class":418,"line":464},6,[416,466,468],{"class":467},"sZZnC","        `${",[416,470,471],{"class":433},"process",[416,473,251],{"class":467},[416,475,476],{"class":433},"env",[416,478,251],{"class":467},[416,480,481],{"class":429},"PREVIEW_URL",[416,483,484],{"class":467},"}\u002F`",[416,486,487],{"class":433},",\n",[416,489,491,493,495,497,499,501,503,506],{"class":418,"line":490},7,[416,492,468],{"class":467},[416,494,471],{"class":433},[416,496,251],{"class":467},[416,498,476],{"class":433},[416,500,251],{"class":467},[416,502,481],{"class":429},[416,504,505],{"class":467},"}\u002Fguides\u002F`",[416,507,487],{"class":433},[416,509,511,513,515,517,519,521,523,526],{"class":418,"line":510},8,[416,512,468],{"class":467},[416,514,471],{"class":433},[416,516,251],{"class":467},[416,518,476],{"class":433},[416,520,251],{"class":467},[416,522,481],{"class":429},[416,524,525],{"class":467},"}\u002Fguides\u002Fdeploying-hugo\u002F`",[416,527,487],{"class":433},[416,529,531,533,535,537,539,541,543,546],{"class":418,"line":530},9,[416,532,468],{"class":467},[416,534,471],{"class":433},[416,536,251],{"class":467},[416,538,476],{"class":433},[416,540,251],{"class":467},[416,542,481],{"class":429},[416,544,545],{"class":467},"}\u002Fblog\u002F2026\u002Fcache-headers\u002F`",[416,547,487],{"class":433},[416,549,551,553,555,557,559,561,563,566],{"class":418,"line":550},10,[416,552,468],{"class":467},[416,554,471],{"class":433},[416,556,251],{"class":467},[416,558,476],{"class":433},[416,560,251],{"class":467},[416,562,481],{"class":429},[416,564,565],{"class":467},"}\u002Freference\u002Fconfig\u002F`",[416,567,487],{"class":433},[416,569,571],{"class":418,"line":570},11,[416,572,573],{"class":433},"      ],\n",[416,575,577,580,583],{"class":418,"line":576},12,[416,578,579],{"class":433},"      numberOfRuns: ",[416,581,582],{"class":429},"3",[416,584,487],{"class":433},[416,586,588,591,594,597,600,603,606,609,612,615],{"class":418,"line":587},13,[416,589,590],{"class":433},"      settings: { preset: ",[416,592,593],{"class":467},"'desktop'",[416,595,596],{"class":439}," ===",[416,598,599],{"class":433}," process.env.",[416,601,602],{"class":429},"LH_PRESET",[416,604,605],{"class":439}," ?",[416,607,608],{"class":467}," 'desktop'",[416,610,611],{"class":439}," :",[416,613,614],{"class":429}," undefined",[416,616,617],{"class":433}," },\n",[416,619,621],{"class":418,"line":620},14,[416,622,623],{"class":433},"    },\n",[416,625,627],{"class":418,"line":626},15,[416,628,629],{"class":433},"    assert: {\n",[416,631,633],{"class":418,"line":632},16,[416,634,635],{"class":433},"      assertions: {\n",[416,637,639,642,645,648,651,654],{"class":418,"line":638},17,[416,640,641],{"class":467},"        'resource-summary:script:size'",[416,643,644],{"class":433},": [",[416,646,647],{"class":467},"'error'",[416,649,650],{"class":433},", { maxNumericValue: ",[416,652,653],{"class":429},"153600",[416,655,656],{"class":433}," }],\n",[416,658,660,663,665,667,669,672,675,678],{"class":418,"line":659},18,[416,661,662],{"class":467},"        'largest-contentful-paint'",[416,664,644],{"class":433},[416,666,647],{"class":467},[416,668,650],{"class":433},[416,670,671],{"class":429},"2500",[416,673,674],{"class":433},", aggregationMethod: ",[416,676,677],{"class":467},"'median'",[416,679,656],{"class":433},[416,681,683,686,688,691,693,695,697,699],{"class":418,"line":682},19,[416,684,685],{"class":467},"        'total-blocking-time'",[416,687,644],{"class":433},[416,689,690],{"class":467},"'warn'",[416,692,650],{"class":433},[416,694,112],{"class":429},[416,696,674],{"class":433},[416,698,677],{"class":467},[416,700,656],{"class":433},[416,702,704,707,709,711,713,715],{"class":418,"line":703},20,[416,705,706],{"class":467},"        'cumulative-layout-shift'",[416,708,644],{"class":433},[416,710,647],{"class":467},[416,712,650],{"class":433},[416,714,376],{"class":429},[416,716,656],{"class":433},[416,718,720,723,726,728],{"class":418,"line":719},21,[416,721,722],{"class":467},"        'unsized-images'",[416,724,725],{"class":433},": ",[416,727,647],{"class":467},[416,729,487],{"class":433},[416,731,733,736,738,740],{"class":418,"line":732},22,[416,734,735],{"class":467},"        'font-display'",[416,737,725],{"class":433},[416,739,647],{"class":467},[416,741,487],{"class":433},[416,743,745],{"class":418,"line":744},23,[416,746,747],{"class":433},"      },\n",[416,749,751],{"class":418,"line":750},24,[416,752,623],{"class":433},[416,754,756,759,762],{"class":418,"line":755},25,[416,757,758],{"class":433},"    upload: { target: ",[416,760,761],{"class":467},"'temporary-public-storage'",[416,763,617],{"class":433},[416,765,767],{"class":418,"line":766},26,[416,768,769],{"class":433},"  },\n",[416,771,773],{"class":418,"line":772},27,[416,774,775],{"class":433},"};\n",[14,777,778,779,251],{},"One URL per template is enough. Pages built from the same layout share the same assets and structure, so testing twenty blog posts tells you nothing that one does not. The step-by-step setup, including the GitHub Actions wiring and status checks, is in ",[21,780,781],{"href":23},"Setting Up Lighthouse CI for a Static Site",[47,783,784,904],{},[50,785,58,790,58,793,58,796,58,799,58,897],{"viewBox":786,"role":53,"ariaLabelledBy":787,"xmlns":57},"0 0 780 290",[788,789],"pbl-tpl-title","pbl-tpl-desc",[60,791,792],{"id":788},"Testing one URL per template instead of every page",[64,794,795],{"id":789},"A site of 1,400 pages is built from five templates: home, section index, guide, blog post and reference. Lighthouse CI tests one representative URL from each, three runs apiece, 15 runs in total taking about four minutes, instead of 4,200 runs for every page.",[68,797],{"x":70,"y":70,"width":71,"height":798,"fill":73},"290",[75,800,78,801,78,804,78,808,78,813,78,816,78,819,78,823,78,826,78,829,78,833,78,836,78,839,78,843,78,846,78,849,78,853,78,856,78,874,78,879,78,882,78,886,78,892,58],{"style":77},[80,802,803],{"x":82,"y":83,"fill":84,"style":85},"1,400 pages, five templates, fifteen Lighthouse runs",[68,805],{"x":89,"y":806,"width":171,"height":807,"rx":215,"fill":113,"opacity":114,"stroke":113,"style":96},"60","50",[80,809,812],{"x":810,"y":811,"fill":84,"style":101},"95","82","home",[80,814,815],{"x":810,"y":99,"fill":106,"style":107},"1 page",[68,817],{"x":818,"y":806,"width":171,"height":807,"rx":215,"fill":113,"opacity":114,"stroke":113,"style":96},"178",[80,820,822],{"x":821,"y":811,"fill":84,"style":101},"243","section index",[80,824,825],{"x":821,"y":99,"fill":106,"style":107},"14 pages",[68,827],{"x":828,"y":806,"width":171,"height":807,"rx":215,"fill":113,"opacity":114,"stroke":113,"style":96},"326",[80,830,832],{"x":831,"y":811,"fill":84,"style":101},"391","guide",[80,834,835],{"x":831,"y":99,"fill":106,"style":107},"610 pages",[68,837],{"x":838,"y":806,"width":171,"height":807,"rx":215,"fill":113,"opacity":114,"stroke":113,"style":96},"474",[80,840,842],{"x":841,"y":811,"fill":84,"style":101},"539","blog post",[80,844,845],{"x":841,"y":99,"fill":106,"style":107},"480 pages",[68,847],{"x":848,"y":806,"width":171,"height":807,"rx":215,"fill":113,"opacity":114,"stroke":113,"style":96},"622",[80,850,852],{"x":851,"y":811,"fill":84,"style":101},"687","reference",[80,854,855],{"x":851,"y":99,"fill":106,"style":107},"295 pages",[75,857,183,858,183,862,183,865,183,868,183,871,78],{"stroke":106,"fill":181,"style":182},[185,859],{"d":860,"style":861},"M95 112 L95 150","marker-end:url(#pbl-tpl-arrow)",[185,863],{"d":864,"style":861},"M243 112 L243 150",[185,866],{"d":867,"style":861},"M391 112 L391 150",[185,869],{"d":870,"style":861},"M539 112 L539 150",[185,872],{"d":873,"style":861},"M687 112 L687 150",[68,875],{"x":89,"y":876,"width":877,"height":807,"rx":93,"fill":149,"opacity":878,"stroke":151,"style":96},"154","722","0.16",[80,880,881],{"x":831,"y":818,"fill":84,"style":101},"1 representative URL each × 3 runs = 15 runs",[80,883,885],{"x":831,"y":884,"fill":106,"style":107},"196","about 4 minutes on a GitHub Actions runner",[68,887],{"x":158,"y":888,"width":889,"height":890,"rx":215,"fill":139,"opacity":376,"stroke":140,"style":891},"226","380","36","stroke-width:1px",[80,893,896],{"x":82,"y":894,"fill":84,"style":895},"249","text-anchor:middle","every page × 3 runs = 4,200 runs, about 18 hours",[208,898,78,899,58],{},[211,900,183,902,78],{"id":901,"viewBox":214,"refX":215,"refY":216,"markerWidth":217,"markerHeight":217,"orient":218},"pbl-tpl-arrow",[185,903],{"d":221,"fill":106},[223,905,906],{},"Performance is a property of templates and their assets. Pick the heaviest real page of each template as its representative.",[227,908,910],{"id":909},"making-results-trustworthy","Making Results Trustworthy",[14,912,913],{},"A performance check that fails at random gets muted within a week. Three sources of noise matter on CI runners: CPU contention from other jobs on the same host, network variation between the runner and the preview host, and Lighthouse's own simulated throttling, which extrapolates from an unthrottled trace.",[14,915,916,917,920],{},"On a GitHub Actions ",[399,918,919],{},"ubuntu-latest"," runner, ten consecutive single runs of the same page produced LCP values from 1.6 to 2.4 seconds and TBT from 40 to 210 ms. With three runs and the median, the spread across ten repetitions narrowed to 1.8–2.0 seconds and 60–110 ms — tight enough to set a threshold on.",[14,922,923,924,927,928,931,932,251],{},"The practical rules: median of three to five runs; byte budgets as ",[399,925,926],{},"error",", timing budgets as ",[399,929,930],{},"warn"," until you have a month of data showing their spread; and assertions on the specific metrics rather than the composite score. The deeper treatment, including running on a dedicated runner and pinning Chrome versions, is in ",[21,933,250],{"href":249},[47,935,936,1071],{},[50,937,58,942,58,945,58,948,58,951],{"viewBox":938,"role":53,"ariaLabelledBy":939,"xmlns":57},"0 0 780 280",[940,941],"pbl-var-title","pbl-var-desc",[60,943,944],{"id":940},"Spread of LCP with single runs versus median of three",[64,946,947],{"id":941},"Ten single Lighthouse runs of the same page produced LCP values scattered between 1.6 and 2.4 seconds, several crossing a 2.2 second threshold. Ten medians of three runs stayed between 1.8 and 2.0 seconds, all below the threshold.",[68,949],{"x":70,"y":70,"width":71,"height":950,"fill":73},"280",[75,952,78,953,78,956,78,960,78,962,78,966,78,973,78,979,78,983,78,987,78,992,78,996,78,999,78,1003,78,1006,78,1009,78,1012,78,1014,78,1017,78,1021,78,1023,78,1027,78,1030,78,1034,78,1038,78,1041,78,1045,78,1048,78,1052,78,1056,78,1060,78,1064,78,1067,58],{"style":77},[80,954,955],{"x":82,"y":83,"fill":84,"style":85},"Same page, same build, ten repetitions (LCP, seconds)",[418,957],{"x1":958,"y1":174,"x2":959,"y2":174,"stroke":106,"style":96},"80","740",[418,961],{"x1":958,"y1":807,"x2":958,"y2":174,"stroke":106,"style":96},[418,963],{"x1":958,"y1":964,"x2":959,"y2":964,"stroke":140,"style":965},"98","stroke-width:1.5px;stroke-dasharray:6 4",[80,967,972],{"x":968,"y":969,"fill":970,"style":971},"736","92","#b32b30","font-size:11px;font-weight:700;text-anchor:end","2.2 s threshold",[80,974,978],{"x":975,"y":976,"fill":106,"style":977},"72","234","font-size:11px;text-anchor:end","1.4",[80,980,982],{"x":975,"y":981,"fill":106,"style":977},"142","2.0",[80,984,986],{"x":975,"y":985,"fill":106,"style":977},"54","2.6",[80,988,991],{"x":989,"y":990,"fill":84,"style":101},"250","252","single runs",[993,994],"circle",{"cx":995,"cy":158,"r":216,"fill":139,"stroke":140,"style":891},"120",[993,997],{"cx":112,"cy":998,"r":216,"fill":139,"stroke":140,"style":891},"128",[993,1000],{"cx":1001,"cy":1002,"r":216,"fill":139,"stroke":140,"style":891},"180","84",[993,1004],{"cx":111,"cy":1005,"r":216,"fill":139,"stroke":140,"style":891},"170",[993,1007],{"cx":1008,"cy":148,"r":216,"fill":139,"stroke":140,"style":891},"240",[993,1010],{"cx":1011,"cy":90,"r":216,"fill":139,"stroke":140,"style":891},"270",[993,1013],{"cx":72,"cy":112,"r":216,"fill":139,"stroke":140,"style":891},[993,1015],{"cx":1016,"cy":969,"r":216,"fill":139,"stroke":140,"style":891},"330",[993,1018],{"cx":1019,"cy":1020,"r":216,"fill":139,"stroke":140,"style":891},"360","185",[993,1022],{"cx":82,"cy":995,"r":216,"fill":139,"stroke":140,"style":891},[80,1024,1026],{"x":1025,"y":990,"fill":84,"style":101},"590","median of 3",[993,1028],{"cx":1029,"cy":91,"r":216,"fill":149,"stroke":151,"style":891},"460",[993,1031],{"cx":1032,"cy":1033,"r":216,"fill":149,"stroke":151,"style":891},"490","134",[993,1035],{"cx":1036,"cy":1037,"r":216,"fill":149,"stroke":151,"style":891},"520","146",[993,1039],{"cx":1040,"cy":998,"r":216,"fill":149,"stroke":151,"style":891},"550",[993,1042],{"cx":1043,"cy":1044,"r":216,"fill":149,"stroke":151,"style":891},"580","152",[993,1046],{"cx":1047,"cy":154,"r":216,"fill":149,"stroke":151,"style":891},"610",[993,1049],{"cx":1050,"cy":1051,"r":216,"fill":149,"stroke":151,"style":891},"640","144",[993,1053],{"cx":1054,"cy":1055,"r":216,"fill":149,"stroke":151,"style":891},"670","132",[993,1057],{"cx":1058,"cy":1059,"r":216,"fill":149,"stroke":151,"style":891},"700","148",[993,1061],{"cx":1062,"cy":1063,"r":216,"fill":149,"stroke":151,"style":891},"730","136",[418,1065],{"x1":1066,"y1":807,"x2":1066,"y2":174,"stroke":95,"style":96},"425",[80,1068,1070],{"x":82,"y":1069,"fill":106,"style":107},"272","GitHub Actions ubuntu-latest, Lighthouse 12 mobile preset, preview deploy on Cloudflare",[223,1072,1073],{},"Four of ten single runs would have failed a 2.2 s threshold on an unchanged page; none of the medians did.",[227,1075,1077],{"id":1076},"tracking-bundle-size-per-pull-request","Tracking Bundle Size per Pull Request",[14,1079,1080,1081,1084,1085,1088],{},"Lighthouse measures pages; bundle-size tracking measures the build output directly and is faster, cheaper and completely deterministic. Tools such as ",[399,1082,1083],{},"size-limit"," or a twenty-line script comparing the ",[399,1086,1087],{},"dist\u002F"," asset sizes against the base branch post a comment on each pull request showing exactly what grew and by how much:",[407,1090,1094],{"className":1091,"code":1093,"language":80,"meta":412},[1092],"language-text","Asset changes vs main\n  _astro\u002FSearch.3f9a.js     +18.4 KB  (new)       ⚠\n  _astro\u002Findex.c21e.css      +0.6 KB\n  Total JS (gzip)            41.2 KB → 59.6 KB    ⚠ over 50 KB warn\n",[399,1095,1093],{"__ignoreMap":412},[14,1097,1098,1099,1102],{},"This catches the dependency-added-for-one-function regression within seconds of the build finishing, long before Lighthouse runs. ",[21,1100,1077],{"href":1101},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-bundle-size-per-pull-request\u002F"," has the full setup.",[227,1104,1106],{"id":1105},"lab-versus-field","Lab Versus Field",[14,1108,1109],{},"Lab tests answer \"did this change make the page slower under fixed conditions?\" Field data answers \"are real readers having a good experience?\" Both questions matter, and they disagree more often than teams expect.",[14,1111,1112],{},"The Chrome User Experience Report (CrUX) publishes 28-day rolling 75th-percentile values for LCP, INP and CLS for origins and popular URLs, and it is what Google's page experience signals use. Your own real-user monitoring gives the same metrics for every page with shorter lag. Comparing the two with lab numbers per template reveals where the lab profile is unrepresentative — for example, a documentation site whose readers mostly use fast desktops will see field LCP well below lab LCP, while a consumer blog read on older phones will see the reverse.",[14,1114,1115,1116,251],{},"Use the comparison to calibrate: if field LCP p75 is 1.4 s while lab LCP is 2.1 s, your lab budget of 2.5 s has a lot of headroom and can tighten. The method is in ",[21,1117,1119],{"href":1118},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fcomparing-lab-and-field-data-with-crux\u002F","Comparing Lab and Field Data with CrUX",[227,1121,1123],{"id":1122},"budgets-and-your-generator","Budgets and Your Generator",[14,1125,1126],{},"The budget table above is generator-neutral, but each generator has a characteristic way of blowing through it, and knowing yours tells you which limit to set tightest.",[14,1128,1129,1132,1133,1136,1137,1140,1141,1145],{},[237,1130,1131],{},"Astro"," ships zero JavaScript by default, so its script budget is really a budget on islands. The regression to watch is a ",[399,1134,1135],{},"client:load"," directive added to a large component — a date picker, a carousel, a React design-system import — which can add 40–80 KB at once. Set the script-bytes error low (60 KB is realistic for a content site) and add a rule in review that any new ",[399,1138,1139],{},"client:"," directive needs a reason. ",[21,1142,1144],{"href":1143},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fdeferring-hydration-with-client-visible-in-astro\u002F","Deferring Hydration with client:visible in Astro"," covers the cheaper directives.",[14,1147,1148,1151],{},[237,1149,1150],{},"Eleventy"," ships only what you add, which makes it the easiest to keep lean and the easiest to regress silently, because there is no framework convention for where scripts go. Budget request count as well as bytes: Eleventy sites tend to accumulate small separate script and stylesheet files from plugins and partials, each one a request and often render-blocking.",[14,1153,1154,1157,1158,1161],{},[237,1155,1156],{},"Hugo"," sites regress most often through images and CSS. Hugo Pipes makes resizing easy but does nothing unless templates call it, so an unprocessed 2 MB PNG in a new post sails through. Budget above-the-fold image bytes on the post template and assert the ",[399,1159,1160],{},"uses-responsive-images"," audit.",[14,1163,1164,1167],{},[237,1165,1166],{},"Next.js static export"," starts with the React runtime and router — typically 85–100 KB compressed before any page code — so a script budget below that is unachievable. Budget the per-route chunk instead, and watch for shared chunks growing as components are imported on more pages.",[14,1169,1170,1173,1174,1178],{},[237,1171,1172],{},"Docs frameworks"," carry their own baselines: measured on a 1,200-page corpus, Starlight pages shipped about 12 KB of JavaScript, VitePress about 58 KB and Docusaurus about 190 KB, as covered in ",[21,1175,1177],{"href":1176},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002F","Docs Frameworks: Docusaurus, Starlight and VitePress",". Set budgets relative to your framework's floor, not to another framework's.",[227,1180,1182],{"id":1181},"handling-a-failing-budget-in-review","Handling a Failing Budget in Review",[14,1184,1185],{},"A budget is only as good as what happens when it fails. Three responses cover nearly every case, and writing them down in the repository's contributing guide saves a debate on every pull request.",[14,1187,1188,1191],{},[237,1189,1190],{},"Fix it in the same pull request."," Most failures have an obvious cause visible in the Lighthouse report or the bundle-size comment: an image not run through the pipeline, a library imported whole, a font weight added. The author fixes it before merge. This should be the outcome for at least four failures in five.",[14,1193,1194,1197],{},[237,1195,1196],{},"Accept it with a raised budget."," Sometimes the regression is the feature — a new interactive tool genuinely needs 30 KB of JavaScript. Raise the budget for that template in the same pull request, with the reason in the commit message, and have the budget owner approve it. The change is visible in history and can be revisited.",[14,1199,1200,1203,1204,1206,1207,1209],{},[237,1201,1202],{},"Defer it with a ticket."," Rarely, a regression must ship for business reasons before it can be fixed. Mark the assertion ",[399,1205,930],{}," for that template with a comment linking a ticket and a date, and have the budget owner restore ",[399,1208,926],{}," by that date. Without the date, deferrals become permanent.",[14,1211,1212,1213,1216],{},"What must never happen is the fourth response: disabling the check, or adding ",[399,1214,1215],{},"continue-on-error",", to get a pull request through. A performance check that can be bypassed quietly stops being a check. Branch protection that makes the Lighthouse status required, with administrators included, removes the temptation.",[227,1218,1220],{"id":1219},"when-lighthouse-is-not-enough","When Lighthouse Is Not Enough",[14,1222,1223,1224,251],{},"Lighthouse loads one page, cold, with one device profile. Some regressions only show up in multi-step journeys (a search dialog that blocks input, a slow client-side navigation) or on specific networks and locations. For those, scripted WebPageTest runs against the preview — logging in, opening search, navigating between pages — catch what a single cold load misses, and its filmstrips make a regression easy to explain in review. See ",[21,1225,1227],{"href":1226},"\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",[227,1229,1231],{"id":1230},"reporting-that-people-read","Reporting That People Read",[14,1233,1234],{},"Checks block merges; reports change habits. Two lightweight reports keep performance visible without a dashboard nobody opens.",[14,1236,1237,1238,1241],{},"The first is the ",[237,1239,1240],{},"pull request comment",". Lighthouse CI's GitHub App or a small script posts a table of each template's LCP, TBT, CLS and script bytes against the base branch, with arrows for direction. Authors see the effect of their change without opening a report, and reviewers can ask about a 20 KB increase before it becomes a failure.",[14,1243,1244,1245,1248],{},"The second is a ",[237,1246,1247],{},"weekly trend note"," posted to the team channel: the median of each budgeted metric across the week's merged pull requests, the headroom left against each budget, and the field p75 values from the previous 28 days. It takes five minutes to automate from stored Lighthouse CI results and gives the budget owner the evidence to tighten a limit or to schedule clean-up work before a limit is hit. Teams that adopted the note in this study raised their median headroom on script bytes from 12% to 31% over a quarter, simply because slow creep became visible.",[14,1250,1251],{},"Store raw results somewhere queryable — a Lighthouse CI server, or JSON artefacts pushed to object storage — rather than relying on temporary public storage, which expires. Six months of history is what lets you tell a real trend from a noisy week.",[227,1253,1255],{"id":1254},"measured-impact","Measured Impact",[14,1257,1258],{},"A documentation and blog site on Eleventy (1,400 pages, six templates) added byte budgets, Lighthouse CI on previews and bundle-size comments, then tracked every performance-related pull request for six months:",[262,1260,1261,1274],{},[265,1262,1263],{},[268,1264,1265,1268,1271],{},[271,1266,1267],{},"Measure",[271,1269,1270],{},"Six months before",[271,1272,1273],{},"Six months after",[284,1275,1276,1287,1298,1309,1320,1331],{},[268,1277,1278,1281,1284],{},[289,1279,1280],{},"Regressions reaching production",[289,1282,1283],{},"11",[289,1285,1286],{},"1",[268,1288,1289,1292,1295],{},[289,1290,1291],{},"Median time to detect a regression",[289,1293,1294],{},"23 days (from CrUX)",[289,1296,1297],{},"at review (same day)",[268,1299,1300,1303,1306],{},[289,1301,1302],{},"Script bytes, guide template",[289,1304,1305],{},"38 → 97 KB (drifted up)",[289,1307,1308],{},"41 → 44 KB",[268,1310,1311,1314,1317],{},[289,1312,1313],{},"Field LCP p75, mobile",[289,1315,1316],{},"2.1 → 2.7 s",[289,1318,1319],{},"2.0 → 1.8 s",[268,1321,1322,1325,1328],{},[289,1323,1324],{},"Field INP p75, mobile",[289,1326,1327],{},"140 → 230 ms",[289,1329,1330],{},"150 → 120 ms",[268,1332,1333,1336,1339],{},[289,1334,1335],{},"CI time added per pull request",[289,1337,1338],{},"—",[289,1340,1341],{},"4 min 10 s",[14,1343,1344],{},"The one regression that escaped was a third-party chat widget loaded only for logged-in users, which Lighthouse never saw because it tested anonymous pages — a reminder to test the states your readers actually encounter.",[227,1346,1348],{"id":1347},"common-pitfalls","Common Pitfalls",[1350,1351,1352,1359,1365,1371,1377,1383],"ul",{},[1353,1354,1355,1358],"li",{},[237,1356,1357],{},"Budgeting the score."," The composite score changes weighting between Lighthouse versions and masks which metric moved. Budget metrics and bytes.",[1353,1360,1361,1364],{},[237,1362,1363],{},"Testing localhost."," A local static server has no compression, CDN or cache headers. Test the preview URL.",[1353,1366,1367,1370],{},[237,1368,1369],{},"Single runs."," One run is a sample, not a measurement. Use the median of three or more.",[1353,1372,1373,1376],{},[237,1374,1375],{},"Aspirational budgets."," A budget that fails on day one gets disabled on day two. Start from current values and ratchet down.",[1353,1378,1379,1382],{},[237,1380,1381],{},"Testing only anonymous, cold pages."," Consent banners, logged-in widgets and repeat visits each have their own performance profile.",[1353,1384,1385,1388],{},[237,1386,1387],{},"Nobody owns the budget."," Assign an owner who reviews warnings weekly and tightens limits quarterly; otherwise warnings accumulate unread.",[227,1390,1392],{"id":1391},"key-takeaways","Key Takeaways",[1350,1394,1395,1398,1401,1404,1407],{},[1353,1396,1397],{},"Budget bytes as hard errors and timings as warnings until you know their spread; both beat budgeting the composite score.",[1353,1399,1400],{},"Run Lighthouse CI against preview deploys, one URL per template, median of three runs.",[1353,1402,1403],{},"Median-of-three kept LCP within 1.8–2.0 s on an unchanged page where single runs ranged from 1.6 to 2.4 s.",[1353,1405,1406],{},"Bundle-size comments on pull requests catch dependency regressions in seconds, before any browser runs.",[1353,1408,1409],{},"Field data from CrUX and RUM calibrates lab budgets; on one site, budgets cut production regressions from 11 to 1 in six months.",[227,1411,1413],{"id":1412},"faq","FAQ",[1415,1416,1418],"h3",{"id":1417},"what-is-a-performance-budget","What is a performance budget?",[14,1420,1421],{},"A set of limits a page must stay within, such as total JavaScript under 100 KB, LCP under 2.5 seconds in the lab, or no more than 20 requests. The budget is enforced in CI so a change that breaks it fails before it merges.",[1415,1423,1425],{"id":1424},"should-the-budget-be-on-scores-or-on-metrics","Should the budget be on scores or on metrics?",[14,1427,1428],{},"On metrics and bytes. The Lighthouse performance score is a weighted blend that shifts between versions and hides which metric moved. Budget LCP, TBT, CLS and resource sizes directly, and treat the score as a summary only.",[1415,1430,1432],{"id":1431},"why-do-lighthouse-results-vary-between-runs","Why do Lighthouse results vary between runs?",[14,1434,1435],{},"CPU contention on shared CI runners, network jitter, and timing-sensitive metrics all add noise. Run three to five times per URL, use the median, and budget byte sizes, which do not vary, alongside timing metrics, which do.",[1415,1437,1439],{"id":1438},"do-lab-budgets-guarantee-good-core-web-vitals","Do lab budgets guarantee good Core Web Vitals?",[14,1441,1442],{},"No. Lab tests use one device and network profile, while field data reflects real users. Lab budgets catch regressions early; field data from CrUX or your own RUM confirms whether real readers are affected.",[1415,1444,1446],{"id":1445},"which-pages-should-lighthouse-ci-test","Which pages should Lighthouse CI test?",[14,1448,1449],{},"One representative URL per template, plus the homepage. A static site with six templates needs six to eight URLs, not every page, because pages built from the same template share the same performance characteristics.",[227,1451,1453],{"id":1452},"related","Related",[1350,1455,1456,1465,1470,1475,1480,1485,1490,1495,1502,1509,1516,1523,1530],{},[1353,1457,1458,1461,1462,1464],{},[237,1459,1460],{},"Up:"," ",[21,1463,29],{"href":28}," — the optimisations these budgets protect.",[1353,1466,1467,1469],{},[21,1468,781],{"href":23}," — the step-by-step wiring.",[1353,1471,1472,1474],{},[21,1473,389],{"href":388}," — turning the table above into config.",[1353,1476,1477,1479],{},[21,1478,250],{"href":249}," — making timing budgets trustworthy.",[1353,1481,1482,1484],{},[21,1483,1077],{"href":1101}," — the fastest, cheapest check.",[1353,1486,1487,1489],{},[21,1488,1119],{"href":1118}," — calibrating budgets against real readers.",[1353,1491,1492,1494],{},[21,1493,1227],{"href":1226}," — multi-step journeys Lighthouse misses.",[1353,1496,1497,1501],{},[21,1498,1500],{"href":1499},"\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 discipline applied to build speed.",[1353,1503,1504,1508],{},[21,1505,1507],{"href":1506},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets\u002F","Per-Template Performance Budgets"," — set a performance budget for each page template of a static site, pick representative URLs automatically, and enforce them with Lighthouse CI and size checks.",[1353,1510,1511,1515],{},[21,1512,1514],{"href":1513},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fperformance-testing-on-throttled-mobile-profiles\u002F","Performance Testing on Throttled Mobile Profiles"," — choose throttling that matches your real readers, calibrate Lighthouse and WebPageTest against field data, and test static sites on real mid-range phones.",[1353,1517,1518,1522],{},[21,1519,1521],{"href":1520},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time\u002F","Tracking Page Weight Over Time"," — record page weight per template on every deploy of a static site, chart the trend, attribute each jump to a commit, and catch slow growth that budgets miss.",[1353,1524,1525,1529],{},[21,1526,1528],{"href":1527},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fmeasuring-web-vitals-in-playwright-tests\u002F","Measuring Web Vitals in Playwright Tests"," — measure LCP, CLS and interaction latency inside existing Playwright tests on a static site, with throttling, stable thresholds and per-PR results.",[1353,1531,1532,1536],{},[21,1533,1535],{"href":1534},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Flighthouse-ci-vs-webpagetest-for-regression-gates\u002F","Lighthouse CI vs WebPageTest for Regression Gates"," — lighthouse CI and WebPageTest compared as pull request performance gates on a static site: variance, regressions caught, false alarms, speed and cost.",[1538,1539,1540],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}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);}",{"title":412,"searchDepth":426,"depth":426,"links":1542},[1543,1544,1545,1546,1547,1548,1549,1550,1551,1552,1553,1554,1555,1562],{"id":229,"depth":426,"text":230},{"id":393,"depth":426,"text":394},{"id":909,"depth":426,"text":910},{"id":1076,"depth":426,"text":1077},{"id":1105,"depth":426,"text":1106},{"id":1122,"depth":426,"text":1123},{"id":1181,"depth":426,"text":1182},{"id":1219,"depth":426,"text":1220},{"id":1230,"depth":426,"text":1231},{"id":1254,"depth":426,"text":1255},{"id":1347,"depth":426,"text":1348},{"id":1391,"depth":426,"text":1392},{"id":1412,"depth":426,"text":1413,"children":1556},[1557,1558,1559,1560,1561],{"id":1417,"depth":446,"text":1418},{"id":1424,"depth":446,"text":1425},{"id":1431,"depth":446,"text":1432},{"id":1438,"depth":446,"text":1439},{"id":1445,"depth":446,"text":1446},{"id":1452,"depth":426,"text":1453},[1564,1567,1568],{"name":1565,"item":1566},"Home","\u002F",{"name":29,"item":28},{"name":5,"item":1569},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002F","2026-09-18","Stop performance regressions before they merge: Lighthouse CI on preview deploys, byte and timing budgets, variance control and field-data checks.","md",[1574,1575,1576,1577,1578],{"q":1418,"a":1421},{"q":1425,"a":1428},{"q":1432,"a":1435},{"q":1439,"a":1442},{"q":1446,"a":1449},{},true,"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci",{"title":5,"description":1571},"performance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Findex","o05b3JlJ3fNjPbCOe2jHSYN0rPe00VOQtnQQpR3fFhM",[1586,1589,1592,1595,1598,1601,1604,1607,1610,1613,1616,1619,1622,1625,1628,1631,1634,1637,1640,1643,1646,1649,1652,1655,1658,1661,1664,1667,1670,1673,1676,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,2029,2032,2035,2038,2041,2044,2047,2050,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,2175,2178,2181,2184,2187,2190,2193,2196,2199,2202,2205,2208,2211,2214,2217,2220,2223,2226,2229,2231,2232,2234,2236,2238,2240,2242,2244,2246,2248,2250,2252,2255,2258,2261,2264,2267,2270,2273,2276,2279,2282,2285,2288,2291,2294,2297,2300,2303,2306,2309,2312,2315,2318,2321,2324,2327,2330,2333,2336,2339,2342,2345,2348,2351,2354,2357,2360,2363,2366,2369,2372,2375,2378,2381,2384,2387,2390,2393,2396,2399,2402,2405,2408,2411,2414,2417,2420,2423,2426,2429,2432,2435,2438,2441,2444,2447,2450,2453,2456,2459,2462,2465,2468,2471,2474,2477,2480,2483,2486,2489,2492,2495,2498,2501,2504,2507,2510,2513,2516,2519,2522,2525,2528,2531,2534,2537,2540,2543,2546,2549,2552,2555,2558,2561,2564,2567,2570,2573,2576,2579,2582,2585,2588,2591,2594,2597,2600,2603,2606,2609,2612,2615,2618,2621,2624,2627,2630,2633,2636,2639,2642,2645,2648,2651,2654,2657,2660,2663,2666,2669,2672,2675,2678,2681,2684,2687,2690,2693,2696,2699,2702,2705,2708,2711,2714,2717],{"path":1587,"title":1588},"\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":1590,"title":1591},"\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":1593,"title":1594},"\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":1596,"title":1597},"\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":1599,"title":1600},"\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":1602,"title":1603},"\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":1605,"title":1606},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1608,"title":1609},"\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":1611,"title":1612},"\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":1614,"title":1615},"\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":1617,"title":1618},"\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":1620,"title":1621},"\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":1623,"title":1624},"\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":1626,"title":1627},"\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":1629,"title":1630},"\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":1632,"title":1633},"\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":1635,"title":1636},"\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":1638,"title":1639},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1641,"title":1642},"\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":1644,"title":1645},"\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":1647,"title":1648},"\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":1650,"title":1651},"\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":1653,"title":1654},"\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":1656,"title":1657},"\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":1659,"title":1660},"\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":1662,"title":1663},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1665,"title":1666},"\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":1668,"title":1669},"\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":1671,"title":1672},"\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":1674,"title":1675},"\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":1677,"title":1177},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress",{"path":1679,"title":1680},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1682,"title":1683},"\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":1685,"title":1686},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1688,"title":1689},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1691,"title":1692},"\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":1694,"title":1695},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1697,"title":1698},"\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":1700,"title":1701},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1703,"title":1704},"\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":1706,"title":1707},"\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":1709,"title":1710},"\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":1712,"title":1713},"\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":1715,"title":1716},"\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":1718,"title":1719},"\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":1721,"title":1722},"\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":1724,"title":1725},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1727,"title":1728},"\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":1730,"title":1731},"\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":1733,"title":1734},"\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":1736,"title":1737},"\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":1739,"title":1740},"\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":1742,"title":1743},"\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":1745,"title":1746},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1748,"title":1749},"\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":1751,"title":1752},"\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":1754,"title":1755},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1757,"title":1758},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1760,"title":1761},"\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":1763,"title":1764},"\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":1766,"title":1767},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1769,"title":1770},"\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":1772,"title":1773},"\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":1775,"title":1776},"\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":1778,"title":1779},"\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":1781,"title":1782},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1784,"title":1785},"\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":1787,"title":1788},"\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":1790,"title":1791},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1793,"title":1794},"\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":1796,"title":1797},"\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":1799,"title":1800},"\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":1802,"title":1803},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1805,"title":1806},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1808,"title":1809},"\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":1811,"title":1812},"\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":1814,"title":1815},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1817,"title":1818},"\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":1820,"title":1821},"\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":1823,"title":1824},"\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":1826,"title":1827},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1829,"title":1830},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1832,"title":1833},"\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":1835,"title":1836},"\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":1838,"title":1839},"\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":1841,"title":1842},"\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":1844,"title":1845},"\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":1847,"title":1848},"\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":1850,"title":1851},"\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":1853,"title":1854},"\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":1856,"title":1857},"\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":1859,"title":1860},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1862,"title":1863},"\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":1865,"title":1866},"\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":1868,"title":1869},"\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":1871,"title":1872},"\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":1874,"title":1875},"\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":1877,"title":1878},"\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":1880,"title":1881},"\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":1883,"title":1884},"\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":1886,"title":1887},"\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":1889,"title":1890},"\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":1892,"title":1893},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1895,"title":1896},"\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":1898,"title":1899},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1901,"title":1902},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1904,"title":1905},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1907,"title":1908},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1910,"title":1911},"\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":1913,"title":1914},"\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":1916,"title":1917},"\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":1919,"title":1920},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1922,"title":1923},"\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":1925,"title":1926},"\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":1928,"title":1929},"\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":1931,"title":1932},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1934,"title":1935},"\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":1937,"title":1938},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1940,"title":1941},"\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":1943,"title":1944},"\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":1946,"title":1947},"\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":1949,"title":1950},"\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":1952,"title":1953},"\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":1955,"title":1956},"\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":1958,"title":1959},"\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":1961,"title":1962},"\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":1964,"title":1965},"\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":1967,"title":1968},"\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":1970,"title":1971},"\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":1973,"title":1974},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1976,"title":1977},"\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":1979,"title":1980},"\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":1982,"title":1983},"\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":1985,"title":1986},"\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":1988,"title":1989},"\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":1991,"title":1992},"\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":1994,"title":1995},"\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":1997,"title":1998},"\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":2000,"title":2001},"\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":2003,"title":2004},"\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":2006,"title":2007},"\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":2009,"title":2010},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":2012,"title":2013},"\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":2015,"title":2016},"\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":2018,"title":2019},"\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":2021,"title":2022},"\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":2024,"title":2025},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":2027,"title":2028},"\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":2030,"title":2031},"\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":2033,"title":2034},"\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":2036,"title":2037},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":2039,"title":2040},"\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":2042,"title":2043},"\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":2045,"title":2046},"\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":2048,"title":2049},"\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":2051,"title":2052},"\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":2054,"title":2055},"\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":2057,"title":2058},"\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":2060,"title":2061},"\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":2063,"title":2064},"\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":2066,"title":2067},"\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":2069,"title":2070},"\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":2072,"title":2073},"\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":2075,"title":2076},"\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":2078,"title":2079},"\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":2081,"title":2082},"\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":2084,"title":2085},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":2087,"title":2088},"\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":2090,"title":2091},"\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":2093,"title":2094},"\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":2096,"title":2097},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":2099,"title":2100},"\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":2102,"title":2103},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":2105,"title":2106},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":2108,"title":2109},"\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":2111,"title":2112},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":2114,"title":2115},"\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":2117,"title":2118},"\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":2120,"title":2121},"\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":2123,"title":2124},"\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":2126,"title":2127},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":2129,"title":2130},"\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":2132,"title":2133},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":2135,"title":2136},"\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":2138,"title":2139},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":2141,"title":2142},"\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":2144,"title":2145},"\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":2147,"title":2148},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":2150,"title":2151},"\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":2153,"title":2154},"\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":2156,"title":2157},"\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":2159,"title":2160},"\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":2162,"title":2163},"\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":2165,"title":2166},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":2168,"title":2169},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":2171,"title":2172},"\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":2174,"title":1144},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fdeferring-hydration-with-client-visible-in-astro",{"path":2176,"title":2177},"\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":2179,"title":2180},"\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":2182,"title":2183},"\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":2185,"title":2186},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":2188,"title":2189},"\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":2191,"title":2192},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":2194,"title":2195},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":2197,"title":2198},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":2200,"title":2201},"\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":2203,"title":2204},"\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":2206,"title":2207},"\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":2209,"title":2210},"\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":2212,"title":2213},"\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":2215,"title":2216},"\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":2218,"title":2219},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":2221,"title":2222},"\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":2224,"title":2225},"\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":2227,"title":2228},"\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":2230,"title":1119},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fcomparing-lab-and-field-data-with-crux",{"path":1581,"title":5},{"path":2233,"title":1535},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Flighthouse-ci-vs-webpagetest-for-regression-gates",{"path":2235,"title":1528},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fmeasuring-web-vitals-in-playwright-tests",{"path":2237,"title":1507},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets",{"path":2239,"title":1514},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fperformance-testing-on-throttled-mobile-profiles",{"path":2241,"title":250},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci",{"path":2243,"title":1227},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Frunning-webpagetest-scripts-against-preview-deploys",{"path":2245,"title":781},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site",{"path":2247,"title":1077},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-bundle-size-per-pull-request",{"path":2249,"title":1521},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time",{"path":2251,"title":389},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fwriting-a-performance-budget-that-fails-builds",{"path":2253,"title":2254},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2256,"title":2257},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2259,"title":2260},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2262,"title":2263},"\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":2265,"title":2266},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2268,"title":2269},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2271,"title":2272},"\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":2274,"title":2275},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2277,"title":2278},"\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":2280,"title":2281},"\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":2283,"title":2284},"\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":2286,"title":2287},"\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":2289,"title":2290},"\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":2292,"title":2293},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2295,"title":2296},"\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":2298,"title":2299},"\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":2301,"title":2302},"\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":2304,"title":2305},"\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":2307,"title":2308},"\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":2310,"title":2311},"\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":2313,"title":2314},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2316,"title":2317},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2319,"title":2320},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2322,"title":2323},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2325,"title":2326},"\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":2328,"title":2329},"\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":2331,"title":2332},"\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":2334,"title":2335},"\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":2337,"title":2338},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2340,"title":2341},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2343,"title":2344},"\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":2346,"title":2347},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2349,"title":2350},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2352,"title":2353},"\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":2355,"title":2356},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2358,"title":2359},"\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":2361,"title":2362},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2364,"title":2365},"\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":2367,"title":2368},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2370,"title":2371},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2373,"title":2374},"\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":2376,"title":2377},"\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":2379,"title":2380},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2382,"title":2383},"\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":2385,"title":2386},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2388,"title":2389},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2391,"title":2392},"\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":2394,"title":2395},"\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":2397,"title":2398},"\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":2400,"title":2401},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2403,"title":2404},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2406,"title":2407},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2409,"title":2410},"\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":2412,"title":2413},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2415,"title":2416},"\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":2418,"title":2419},"\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":2421,"title":2422},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2424,"title":2425},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2427,"title":2428},"\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":2430,"title":2431},"\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":2433,"title":2434},"\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":2436,"title":2437},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2439,"title":2440},"\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":2442,"title":2443},"\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":2445,"title":2446},"\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":2448,"title":2449},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2451,"title":2452},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2454,"title":2455},"\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":2457,"title":2458},"\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":2460,"title":2461},"\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":2463,"title":2464},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2466,"title":2467},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2469,"title":2470},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2472,"title":2473},"\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":2475,"title":2476},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2478,"title":2479},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2481,"title":2482},"\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":2484,"title":2485},"\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":2487,"title":2488},"\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":2490,"title":2491},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2493,"title":2494},"\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":2496,"title":2497},"\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":2499,"title":2500},"\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":2502,"title":2503},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2505,"title":2506},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2508,"title":2509},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2511,"title":2512},"\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":2514,"title":2515},"\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":2517,"title":2518},"\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":2520,"title":2521},"\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":2523,"title":2524},"\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":2526,"title":2527},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2529,"title":2530},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2532,"title":2533},"\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":2535,"title":2536},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2538,"title":2539},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2541,"title":2542},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2544,"title":2545},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2547,"title":2548},"\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":2550,"title":2551},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2553,"title":2554},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2556,"title":2557},"\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":2559,"title":2560},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2562,"title":2563},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2565,"title":2566},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2568,"title":2569},"\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":2571,"title":2572},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2574,"title":2575},"\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":2577,"title":2578},"\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":2580,"title":2581},"\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":2583,"title":2584},"\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":2586,"title":2587},"\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":2589,"title":2590},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2592,"title":2593},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2595,"title":2596},"\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":2598,"title":2599},"\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":2601,"title":2602},"\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":2604,"title":2605},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2607,"title":2608},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2610,"title":2611},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2613,"title":2614},"\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":2616,"title":2617},"\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":2619,"title":2620},"\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":2622,"title":2623},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2625,"title":2626},"\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":2628,"title":2629},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2631,"title":2632},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2634,"title":2635},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2637,"title":2638},"\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":2640,"title":2641},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2643,"title":2644},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2646,"title":2647},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2649,"title":2650},"\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":2652,"title":2653},"\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":2655,"title":2656},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2658,"title":2659},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2661,"title":2662},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2664,"title":2665},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2667,"title":2668},"\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":2670,"title":2671},"\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":2673,"title":2674},"\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":2676,"title":2677},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2679,"title":2680},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2682,"title":2683},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2685,"title":2686},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2688,"title":2689},"\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":2691,"title":2692},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2694,"title":2695},"\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":2697,"title":2698},"\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":2700,"title":2701},"\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":2703,"title":2704},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2706,"title":2707},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2709,"title":2710},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2712,"title":2713},"\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":2715,"title":2716},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2718,"title":2719},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",null,1790943190978]