[{"data":1,"prerenderedAt":2090},["ShallowReactive",2],{"page:\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci":3,"all-docs-nav":1550},{"id":4,"title":5,"body":6,"breadcrumb":1528,"dateModified":1535,"datePublished":1535,"description":1536,"extension":1537,"faq":1538,"meta":1544,"navigation":1545,"path":1546,"seo":1547,"slug":12,"stem":1548,"type":832,"__hash__":1549},"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":1506},"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,1502],[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],{},[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.",[1503,1504,1505],"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":1507},[1508,1509,1510,1511,1512,1513,1514,1515,1516,1517,1518,1519,1520,1527],{"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":1521},[1522,1523,1524,1525,1526],{"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},[1529,1532,1533],{"name":1530,"item":1531},"Home","\u002F",{"name":29,"item":28},{"name":5,"item":1534},"\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",[1539,1540,1541,1542,1543],{"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":1536},"performance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Findex","GQ4QwCPrKancu3Cj1MjQ0K_6gIiYZ4eQ315zhENTmfM",[1551,1554,1557,1560,1563,1566,1569,1572,1575,1577,1580,1583,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,1679,1682,1685,1688,1691,1694,1697,1700,1703,1706,1709,1712,1715,1718,1721,1724,1727,1730,1733,1736,1739,1742,1745,1748,1751,1754,1757,1760,1763,1766,1769,1772,1775,1778,1781,1784,1787,1790,1793,1796,1798,1801,1804,1807,1810,1813,1816,1819,1822,1825,1828,1830,1831,1833,1835,1837,1839,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1904,1907,1910,1913,1916,1919,1922,1925,1928,1931,1934,1937,1940,1943,1946,1949,1952,1955,1958,1961,1964,1967,1970,1973,1976,1979,1982,1985,1988,1991,1994,1997,2000,2003,2006,2009,2012,2015,2018,2021,2024,2027,2030,2033,2036,2039,2042,2045,2048,2051,2054,2057,2060,2063,2066,2069,2072,2075,2078,2081,2084,2087],{"path":1552,"title":1553},"\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":1555,"title":1556},"\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":1558,"title":1559},"\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":1561,"title":1562},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1564,"title":1565},"\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":1567,"title":1568},"\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":1570,"title":1571},"\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":1573,"title":1574},"\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":1576,"title":1177},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress",{"path":1578,"title":1579},"\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":1581,"title":1582},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1584,"title":1585},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1587,"title":1588},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1590,"title":1591},"\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":1593,"title":1594},"\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":1596,"title":1597},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1599,"title":1600},"\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":1602,"title":1603},"\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":1605,"title":1606},"\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":1608,"title":1609},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1611,"title":1612},"\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":1614,"title":1615},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1617,"title":1618},"\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":1620,"title":1621},"\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":1623,"title":1624},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1626,"title":1627},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1629,"title":1630},"\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":1632,"title":1633},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1635,"title":1636},"\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":1638,"title":1639},"\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":1641,"title":1642},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1644,"title":1645},"\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":1647,"title":1648},"\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":1650,"title":1651},"\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":1653,"title":1654},"\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":1656,"title":1657},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1659,"title":1660},"\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":1662,"title":1663},"\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":1665,"title":1666},"\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":1668,"title":1669},"\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":1671,"title":1672},"\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":1674,"title":1675},"\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":1677,"title":1678},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1680,"title":1681},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1683,"title":1684},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1686,"title":1687},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1689,"title":1690},"\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":1692,"title":1693},"\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":1695,"title":1696},"\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":1698,"title":1699},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1701,"title":1702},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1704,"title":1705},"\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":1707,"title":1708},"\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":1710,"title":1711},"\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":1713,"title":1714},"\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":1716,"title":1717},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1719,"title":1720},"\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":1722,"title":1723},"\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":1725,"title":1726},"\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":1728,"title":1729},"\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":1731,"title":1732},"\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":1734,"title":1735},"\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":1737,"title":1738},"\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":1740,"title":1741},"\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":1743,"title":1744},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1746,"title":1747},"\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":1749,"title":1750},"\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":1752,"title":1753},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1755,"title":1756},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1758,"title":1759},"\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":1761,"title":1762},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1764,"title":1765},"\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":1767,"title":1768},"\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":1770,"title":1771},"\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":1773,"title":1774},"\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":1776,"title":1777},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1779,"title":1780},"\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":1782,"title":1783},"\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":1785,"title":1786},"\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":1788,"title":1789},"\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":1791,"title":1792},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1794,"title":1795},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1797,"title":1144},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fdeferring-hydration-with-client-visible-in-astro",{"path":1799,"title":1800},"\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":1802,"title":1803},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1805,"title":1806},"\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":1808,"title":1809},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1811,"title":1812},"\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":1814,"title":1815},"\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":1817,"title":1818},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1820,"title":1821},"\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":1823,"title":1824},"\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":1826,"title":1827},"\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":1829,"title":1119},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fcomparing-lab-and-field-data-with-crux",{"path":1546,"title":5},{"path":1832,"title":250},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci",{"path":1834,"title":1227},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Frunning-webpagetest-scripts-against-preview-deploys",{"path":1836,"title":781},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site",{"path":1838,"title":1077},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-bundle-size-per-pull-request",{"path":1840,"title":389},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fwriting-a-performance-budget-that-fails-builds",{"path":1842,"title":1843},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1845,"title":1846},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1848,"title":1849},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1851,"title":1852},"\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":1854,"title":1855},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1857,"title":1858},"\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":1860,"title":1861},"\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":1863,"title":1864},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1866,"title":1867},"\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":1869,"title":1870},"\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":1872,"title":1873},"\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":1875,"title":1876},"\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":1878,"title":1879},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1881,"title":1882},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1884,"title":1885},"\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":1887,"title":1888},"\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":1890,"title":1891},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1893,"title":1894},"\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":1896,"title":1897},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1899,"title":1900},"\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":1902,"title":1903},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1905,"title":1906},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1908,"title":1909},"\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":1911,"title":1912},"\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":1914,"title":1915},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1917,"title":1918},"\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":1920,"title":1921},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1923,"title":1924},"\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":1926,"title":1927},"\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":1929,"title":1930},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1932,"title":1933},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1935,"title":1936},"\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":1938,"title":1939},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1941,"title":1942},"\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":1944,"title":1945},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1947,"title":1948},"\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":1950,"title":1951},"\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":1953,"title":1954},"\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":1956,"title":1957},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1959,"title":1960},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1962,"title":1963},"\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":1965,"title":1966},"\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":1968,"title":1969},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1971,"title":1972},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1974,"title":1975},"\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":1977,"title":1978},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1980,"title":1981},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1983,"title":1984},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1986,"title":1987},"\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":1989,"title":1990},"\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":1992,"title":1993},"\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":1995,"title":1996},"\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":1998,"title":1999},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2001,"title":2002},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2004,"title":2005},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2007,"title":2008},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2010,"title":2011},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2013,"title":2014},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2016,"title":2017},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2019,"title":2020},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2022,"title":2023},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2025,"title":2026},"\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":2028,"title":2029},"\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":2031,"title":2032},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2034,"title":2035},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2037,"title":2038},"\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":2040,"title":2041},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2043,"title":2044},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2046,"title":2047},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2049,"title":2050},"\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":2052,"title":2053},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2055,"title":2056},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2058,"title":2059},"\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":2061,"title":2062},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2064,"title":2065},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2067,"title":2068},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2070,"title":2071},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2073,"title":2074},"\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":2076,"title":2077},"\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":2079,"title":2080},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2082,"title":2083},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2085,"title":2086},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2088,"title":2089},"\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",1789722846728]