[{"data":1,"prerenderedAt":1463},["ShallowReactive",2],{"page:\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components":3,"all-docs-nav":919},{"id":4,"title":5,"body":6,"breadcrumb":895,"dateModified":905,"datePublished":905,"description":906,"extension":907,"faq":908,"meta":913,"navigation":306,"path":914,"seo":915,"slug":12,"stem":916,"type":917,"__hash__":918},"content\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components\u002Findex.md","Replacing React Islands with Web Components",{"type":7,"value":8,"toc":877},"minimark",[9,13,17,26,31,48,52,55,201,204,208,211,219,467,477,481,488,591,598,602,609,689,693,696,730,733,736,740,743,747,790,794,797,801,806,809,813,816,820,823,827,830,834,873],[10,11,5],"h1",{"id":12},"replacing-react-islands-with-web-components",[14,15,16],"p",{},"Islands architecture was a big step forward for static sites: instead of hydrating the whole page, only the interactive parts ship JavaScript. But an island still carries its framework. A \"copy code\" button written as a React island on an otherwise static documentation page pulls in React and React DOM — around 45 KB compressed — to attach one click handler. Multiply that by tabs, a theme toggle and a feedback widget, and a page that is 95% text ends up with a 120 KB JavaScript budget and a noticeable INP cost on low-end phones.",[14,18,19,20,25],{},"For small, self-contained widgets, a custom element does the same job with no runtime. This guide shows how to decide which islands to replace, rewrites a tabs widget as a web component that enhances build-time HTML, and measures the difference. It is part of ",[21,22,24],"a",{"href":23},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002F","JavaScript Hydration & Partial Rendering",".",[27,28,30],"h2",{"id":29},"prerequisites","Prerequisites",[32,33,34,38,45],"ul",{},[35,36,37],"li",{},"A static site using Astro islands, or a framework-hydrated widget in another generator.",[35,39,40,41,25],{},"A bundle analysis showing which scripts each page loads — see ",[21,42,44],{"href":43},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-bundle-size-per-pull-request\u002F","Tracking Bundle Size Per Pull Request",[35,46,47],{},"Field INP data if you have it, to confirm the benefit afterwards.",[27,49,51],{"id":50},"which-islands-to-replace","Which Islands to Replace",[14,53,54],{},"Not every island is a candidate. A search interface with complex state, a data-heavy chart or a form with validation is where a framework earns its keep. The good candidates are the small widgets that make up most islands on content sites.",[56,57,58,197],"figure",{},[59,60,67,68,67,72,67,76,67,83],"svg",{"viewBox":61,"role":62,"ariaLabelledBy":63,"xmlns":66},"0 0 760 290","img",[64,65],"rwc-which-title","rwc-which-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[69,70,71],"title",{"id":64},"Which islands are worth replacing",[73,74,75],"desc",{"id":65},"A two by two grid by state complexity and whether other framework code is on the page. Simple widgets on pages with no other framework code are the best candidates: copy buttons, tabs, disclosure, theme toggle. Complex widgets such as search or charts should stay as islands. Simple widgets on pages that already load the framework give a smaller gain.",[77,78],"rect",{"x":79,"y":79,"width":80,"height":81,"fill":82},"0","760","290","#ffffff",[84,85,87,88,87,96,87,103,87,109,87,114,87,118,87,124,87,129,87,133,87,136,87,139,87,142,87,146,87,150,87,154,87,158,87,162,87,165,87,168,87,171,87,174,87,178,87,181,87,186,87,190,87,193,67],"g",{"style":86},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[89,90,95],"text",{"x":91,"y":92,"fill":93,"style":94},"380","26","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Replace simple islands first",[77,97],{"x":98,"y":99,"width":81,"height":100,"fill":101,"style":102,"stroke":101},"140","46","100","#3f6410","fill-opacity:0.15",[89,104,108],{"x":105,"y":106,"fill":101,"style":107},"285","72","font-weight:700;text-anchor:middle","Replace now",[89,110,113],{"x":105,"y":111,"fill":93,"style":112},"96","text-anchor:middle","copy button, tabs, disclosure,",[89,115,117],{"x":105,"y":116,"fill":93,"style":112},"114","theme toggle, reading progress",[89,119,123],{"x":105,"y":120,"fill":121,"style":122},"132","#556071","font-size:11px;text-anchor:middle","saves the whole runtime",[77,125],{"x":126,"y":99,"width":81,"height":100,"fill":127,"style":128,"stroke":127},"440","#166a9e","fill-opacity:0.1",[89,130,132],{"x":131,"y":106,"fill":127,"style":107},"585","Keep as island",[89,134,135],{"x":131,"y":111,"fill":93,"style":112},"search UI, charts,",[89,137,138],{"x":131,"y":116,"fill":93,"style":112},"multi-step forms",[89,140,141],{"x":131,"y":120,"fill":121,"style":122},"framework earns its cost",[77,143],{"x":98,"y":144,"width":81,"height":100,"fill":145,"style":128,"stroke":145},"156","#8a6d0f",[89,147,149],{"x":105,"y":148,"fill":145,"style":107},"182","Replace later",[89,151,153],{"x":105,"y":152,"fill":93,"style":112},"206","simple widget on a page",[89,155,157],{"x":105,"y":156,"fill":93,"style":112},"224","that already loads React",[89,159,161],{"x":105,"y":160,"fill":121,"style":122},"242","saves only the widget code",[77,163],{"x":126,"y":144,"width":81,"height":100,"fill":121,"style":164,"stroke":121},"fill-opacity:0.08",[89,166,167],{"x":131,"y":148,"fill":121,"style":107},"Leave alone",[89,169,170],{"x":131,"y":152,"fill":93,"style":112},"complex widget sharing",[89,172,173],{"x":131,"y":156,"fill":93,"style":112},"state with other islands",[89,175,177],{"x":105,"y":176,"fill":93,"style":112},"276","simple, local state",[89,179,180],{"x":131,"y":176,"fill":93,"style":112},"complex or shared state",[89,182,185],{"x":183,"y":100,"fill":93,"style":184},"130","text-anchor:end","no other",[89,187,189],{"x":183,"y":188,"fill":93,"style":184},"116","framework",[89,191,189],{"x":183,"y":192,"fill":93,"style":184},"210",[89,194,196],{"x":183,"y":195,"fill":93,"style":184},"226","already loaded",[198,199,200],"figcaption",{},"The biggest saving comes when the last React island on a page is removed, because the runtime goes with it.",[14,202,203],{},"List every island by page template, note its framework, and mark the templates where replacing the simple ones removes the framework entirely. Those are the pages where the saving is largest. On a typical documentation site that is the article template, which makes up most of the page views.",[27,205,207],{"id":206},"build-time-html-client-side-behaviour","Build-Time HTML, Client-Side Behaviour",[14,209,210],{},"The key design choice is to render the widget's markup at build time and let the custom element add behaviour. That keeps the content visible without JavaScript, avoids layout shift, and means the element needs no rendering code at all — just event handlers.",[14,212,213,214,218],{},"Here is a tabs component in Astro that renders ordinary HTML and wraps it in a ",[215,216,217],"code",{},"\u003Ctab-set>"," element:",[220,221,226],"pre",{"className":222,"code":223,"language":224,"meta":225,"style":225},"language-astro shiki shiki-themes github-light github-dark","---\nconst { labels } = Astro.props;\n---\n\u003Ctab-set>\n  \u003Cdiv role=\"tablist\">\n    {labels.map((label, i) => (\n      \u003Cbutton role=\"tab\" id={`tab-${i}`} aria-controls={`panel-${i}`}\n              aria-selected={i === 0 ? 'true' : 'false'} tabindex={i === 0 ? 0 : -1}>{label}\u003C\u002Fbutton>\n    ))}\n  \u003C\u002Fdiv>\n  \u003Cslot \u002F>\n\u003C\u002Ftab-set>\n\n\u003Cscript>\n  class TabSet extends HTMLElement {\n    connectedCallback() {\n      this.tabs = [...this.querySelectorAll('[role=\"tab\"]')];\n      this.panels = [...this.querySelectorAll('[role=\"tabpanel\"]')];\n      this.addEventListener('click', (e) => {\n        const tab = e.target.closest('[role=\"tab\"]');\n        if (tab) this.select(this.tabs.indexOf(tab));\n      });\n      this.addEventListener('keydown', (e) => {\n        const i = this.tabs.indexOf(document.activeElement);\n        if (i \u003C 0) return;\n        if (e.key === 'ArrowRight') this.select((i + 1) % this.tabs.length, true);\n        if (e.key === 'ArrowLeft') this.select((i - 1 + this.tabs.length) % this.tabs.length, true);\n      });\n    }\n    select(index, focus = false) {\n      this.tabs.forEach((t, i) => {\n        t.setAttribute('aria-selected', String(i === index));\n        t.tabIndex = i === index ? 0 : -1;\n        this.panels[i].hidden = i !== index;\n      });\n      if (focus) this.tabs[index].focus();\n    }\n  }\n  customElements.define('tab-set', TabSet);\n\u003C\u002Fscript>\n","astro","",[215,227,228,236,242,247,253,259,265,271,277,283,289,295,301,308,314,320,326,332,338,344,350,356,362,368,374,380,386,392,397,403,409,415,421,427,433,438,444,449,455,461],{"__ignoreMap":225},[229,230,233],"span",{"class":231,"line":232},"line",1,[229,234,235],{},"---\n",[229,237,239],{"class":231,"line":238},2,[229,240,241],{},"const { labels } = Astro.props;\n",[229,243,245],{"class":231,"line":244},3,[229,246,235],{},[229,248,250],{"class":231,"line":249},4,[229,251,252],{},"\u003Ctab-set>\n",[229,254,256],{"class":231,"line":255},5,[229,257,258],{},"  \u003Cdiv role=\"tablist\">\n",[229,260,262],{"class":231,"line":261},6,[229,263,264],{},"    {labels.map((label, i) => (\n",[229,266,268],{"class":231,"line":267},7,[229,269,270],{},"      \u003Cbutton role=\"tab\" id={`tab-${i}`} aria-controls={`panel-${i}`}\n",[229,272,274],{"class":231,"line":273},8,[229,275,276],{},"              aria-selected={i === 0 ? 'true' : 'false'} tabindex={i === 0 ? 0 : -1}>{label}\u003C\u002Fbutton>\n",[229,278,280],{"class":231,"line":279},9,[229,281,282],{},"    ))}\n",[229,284,286],{"class":231,"line":285},10,[229,287,288],{},"  \u003C\u002Fdiv>\n",[229,290,292],{"class":231,"line":291},11,[229,293,294],{},"  \u003Cslot \u002F>\n",[229,296,298],{"class":231,"line":297},12,[229,299,300],{},"\u003C\u002Ftab-set>\n",[229,302,304],{"class":231,"line":303},13,[229,305,307],{"emptyLinePlaceholder":306},true,"\n",[229,309,311],{"class":231,"line":310},14,[229,312,313],{},"\u003Cscript>\n",[229,315,317],{"class":231,"line":316},15,[229,318,319],{},"  class TabSet extends HTMLElement {\n",[229,321,323],{"class":231,"line":322},16,[229,324,325],{},"    connectedCallback() {\n",[229,327,329],{"class":231,"line":328},17,[229,330,331],{},"      this.tabs = [...this.querySelectorAll('[role=\"tab\"]')];\n",[229,333,335],{"class":231,"line":334},18,[229,336,337],{},"      this.panels = [...this.querySelectorAll('[role=\"tabpanel\"]')];\n",[229,339,341],{"class":231,"line":340},19,[229,342,343],{},"      this.addEventListener('click', (e) => {\n",[229,345,347],{"class":231,"line":346},20,[229,348,349],{},"        const tab = e.target.closest('[role=\"tab\"]');\n",[229,351,353],{"class":231,"line":352},21,[229,354,355],{},"        if (tab) this.select(this.tabs.indexOf(tab));\n",[229,357,359],{"class":231,"line":358},22,[229,360,361],{},"      });\n",[229,363,365],{"class":231,"line":364},23,[229,366,367],{},"      this.addEventListener('keydown', (e) => {\n",[229,369,371],{"class":231,"line":370},24,[229,372,373],{},"        const i = this.tabs.indexOf(document.activeElement);\n",[229,375,377],{"class":231,"line":376},25,[229,378,379],{},"        if (i \u003C 0) return;\n",[229,381,383],{"class":231,"line":382},26,[229,384,385],{},"        if (e.key === 'ArrowRight') this.select((i + 1) % this.tabs.length, true);\n",[229,387,389],{"class":231,"line":388},27,[229,390,391],{},"        if (e.key === 'ArrowLeft') this.select((i - 1 + this.tabs.length) % this.tabs.length, true);\n",[229,393,395],{"class":231,"line":394},28,[229,396,361],{},[229,398,400],{"class":231,"line":399},29,[229,401,402],{},"    }\n",[229,404,406],{"class":231,"line":405},30,[229,407,408],{},"    select(index, focus = false) {\n",[229,410,412],{"class":231,"line":411},31,[229,413,414],{},"      this.tabs.forEach((t, i) => {\n",[229,416,418],{"class":231,"line":417},32,[229,419,420],{},"        t.setAttribute('aria-selected', String(i === index));\n",[229,422,424],{"class":231,"line":423},33,[229,425,426],{},"        t.tabIndex = i === index ? 0 : -1;\n",[229,428,430],{"class":231,"line":429},34,[229,431,432],{},"        this.panels[i].hidden = i !== index;\n",[229,434,436],{"class":231,"line":435},35,[229,437,361],{},[229,439,441],{"class":231,"line":440},36,[229,442,443],{},"      if (focus) this.tabs[index].focus();\n",[229,445,447],{"class":231,"line":446},37,[229,448,402],{},[229,450,452],{"class":231,"line":451},38,[229,453,454],{},"  }\n",[229,456,458],{"class":231,"line":457},39,[229,459,460],{},"  customElements.define('tab-set', TabSet);\n",[229,462,464],{"class":231,"line":463},40,[229,465,466],{},"\u003C\u002Fscript>\n",[14,468,469,470,473,474,476],{},"Astro bundles the ",[215,471,472],{},"\u003Cscript>"," once per page, however many ",[215,475,217],{}," elements there are, and loads it as a module, which is deferred by default. The same pattern works in Hugo or Eleventy: render the markup in a partial or shortcode and include the script once in the layout.",[27,478,480],{"id":479},"light-dom-or-shadow-dom","Light DOM or Shadow DOM",[14,482,483,484,487],{},"Custom elements can render into a shadow root, which encapsulates styles and markup. For content-site widgets that is usually unnecessary and sometimes harmful: shadow DOM hides the markup from your site's global styles, and ARIA attributes such as ",[215,485,486],{},"aria-labelledby"," cannot reference IDs across the shadow boundary. Enhancing light DOM children, as above, keeps styling in your normal CSS and keeps accessibility relationships intact. Reach for shadow DOM when you are building a widget to be embedded on other people's sites, where isolation is the point.",[56,489,490,588],{},[59,491,67,496,67,499,67,502,67,505],{"viewBox":492,"role":62,"ariaLabelledBy":493,"xmlns":66},"0 0 760 250",[494,495],"rwc-dom-title","rwc-dom-desc",[69,497,498],{"id":494},"Light DOM enhancement compared with shadow DOM rendering",[73,500,501],{"id":495},"Left: a light DOM element wraps build-time buttons and panels; site CSS applies and aria-controls references work. Right: a shadow DOM element holds its markup inside a shadow root; site CSS does not reach it and ID references from outside cannot cross the boundary.",[77,503],{"x":79,"y":79,"width":80,"height":504,"fill":82},"250",[84,506,87,507,87,510,87,517,87,522,87,527,87,531,87,536,87,540,87,544,87,547,87,551,87,554,87,557,87,562,87,566,87,571,87,574,87,578,87,582,87,585,67],{"style":86},[89,508,509],{"x":91,"y":92,"fill":93,"style":94},"Where the widget's markup lives",[77,511],{"x":512,"y":513,"width":514,"height":515,"rx":516,"fill":101,"style":164,"stroke":101},"30","44","330","150","8",[89,518,521],{"x":519,"y":520,"fill":101,"style":107},"195","68","Light DOM (recommended)",[77,523],{"x":524,"y":525,"width":81,"height":111,"rx":526,"fill":82,"stroke":121},"50","82","6",[89,528,217],{"x":529,"y":530,"fill":93},"64","104",[89,532,535],{"x":533,"y":534,"fill":93},"80","126","button role=tab (build-time HTML)",[89,537,539],{"x":533,"y":538,"fill":93},"146","div role=tabpanel",[89,541,543],{"x":529,"y":542,"fill":93},"168","\u003C\u002Ftab-set>",[77,545],{"x":546,"y":513,"width":514,"height":515,"rx":516,"fill":145,"style":164,"stroke":145},"400",[89,548,550],{"x":549,"y":520,"fill":145,"style":107},"565","Shadow DOM",[77,552],{"x":553,"y":525,"width":81,"height":111,"rx":526,"fill":82,"stroke":121},"420",[89,555,217],{"x":556,"y":530,"fill":93},"434",[77,558],{"x":559,"y":560,"width":504,"height":513,"fill":145,"stroke":145,"style":561},"446","112","fill-opacity:0.1;stroke-dasharray:4 3",[89,563,565],{"x":564,"y":183,"fill":93},"456","#shadow-root: tabs, panels",[89,567,570],{"x":564,"y":568,"fill":121,"style":569},"148","font-size:11px","rendered by JavaScript",[89,572,543],{"x":556,"y":573,"fill":93},"172",[89,575,577],{"x":519,"y":576,"fill":101,"style":112},"216","site CSS applies, ARIA IDs resolve,",[89,579,581],{"x":519,"y":580,"fill":101,"style":112},"234","content visible before JavaScript",[89,583,584],{"x":549,"y":576,"fill":145,"style":112},"styles isolated, ID references blocked,",[89,586,587],{"x":549,"y":580,"fill":145,"style":112},"content appears when script runs",[198,589,590],{},"For content-site widgets, enhancing build-time light DOM keeps styling and accessibility simple.",[14,592,593,594,597],{},"Declarative shadow DOM, where the shadow root is written into the HTML with ",[215,595,596],{},"\u003Ctemplate shadowrootmode=\"open\">",", removes the \"content appears when the script runs\" problem and is supported in all current browsers. It still isolates styles, though, so it suits design-system components more than one-off enhancements on a documentation page.",[27,599,601],{"id":600},"what-the-browser-does-differently","What the Browser Does Differently",[14,603,604,605,608],{},"A React island has to download the runtime and the component, execute them, and hydrate — re-render the component in memory and reconcile it with the server HTML — before it responds to clicks. A custom element's script runs once, defines the class, and the browser calls ",[215,606,607],{},"connectedCallback"," for each instance. There is no reconciliation step and far less main-thread work.",[56,610,611,686],{},[59,612,67,616,67,619,67,622,67,624],{"viewBox":492,"role":62,"ariaLabelledBy":613,"xmlns":66},[614,615],"rwc-main-title","rwc-main-desc",[69,617,618],{"id":614},"Main-thread work to make three widgets interactive",[73,620,621],{"id":615},"On a mid-range phone, React islands for tabs, copy buttons and a theme toggle need 46 kilobytes of compressed JavaScript and 190 milliseconds of main-thread work including hydration. The same three widgets as custom elements need 2.1 kilobytes and 9 milliseconds.",[77,623],{"x":79,"y":79,"width":80,"height":504,"fill":82},[84,625,87,626,87,630,87,635,87,642,87,647,87,650,87,655,87,660,87,664,87,667,87,671,87,675,87,678,87,683,67],{"style":86},[89,627,629],{"x":91,"y":628,"fill":93,"style":94},"28","Three widgets, mid-range Android phone",[89,631,634],{"x":632,"y":633,"fill":93,"style":184},"200","74","React islands: bytes",[77,636],{"x":192,"y":637,"width":638,"height":639,"fill":640,"style":641},"62","460","18","#d83b41","fill-opacity:0.45",[89,643,646],{"x":644,"y":645,"fill":93,"style":184},"662","75","46 KB",[89,648,649],{"x":632,"y":530,"fill":93,"style":184},"custom elements: bytes",[77,651],{"x":192,"y":652,"width":653,"height":639,"fill":101,"style":654},"92","21","fill-opacity:0.6",[89,656,659],{"x":657,"y":658,"fill":93},"239","105","2.1 KB",[89,661,663],{"x":632,"y":662,"fill":93,"style":184},"154","React islands: main thread",[77,665],{"x":192,"y":666,"width":638,"height":639,"fill":640,"style":641},"142",[89,668,670],{"x":644,"y":669,"fill":93,"style":184},"155","190 ms",[89,672,674],{"x":632,"y":673,"fill":93,"style":184},"184","custom elements: main thread",[77,676],{"x":192,"y":573,"width":677,"height":639,"fill":101,"style":654},"22",[89,679,682],{"x":680,"y":681,"fill":93},"240","185","9 ms",[89,684,685],{"x":91,"y":195,"fill":121,"style":122},"compressed transfer size; script evaluation plus hydration, 4× CPU slowdown profile",[198,687,688],{},"Most of the saving is the framework runtime and hydration, not the widget code itself.",[27,690,692],{"id":691},"migrating-one-widget-at-a-time","Migrating One Widget at a Time",[14,694,695],{},"Replace islands incrementally so each change is small and measurable:",[697,698,699,706,712,718,724],"ol",{},[35,700,701,705],{},[702,703,704],"strong",{},"Pick the widget with the most instances"," on the highest-traffic template. Copy buttons on code blocks are often first.",[35,707,708,711],{},[702,709,710],{},"Move rendering to build time."," The markup that React rendered on the server becomes a plain component or partial.",[35,713,714,717],{},[702,715,716],{},"Write the element"," with only the event handling and state the widget needs.",[35,719,720,723],{},[702,721,722],{},"Match behaviour exactly",", including keyboard support and focus handling, and run the same accessibility checks as before.",[35,725,726,729],{},[702,727,728],{},"Remove the island"," and confirm in the bundle report that the framework chunk is gone from that template.",[14,731,732],{},"Test each replacement on the slowest device you support, not only on a developer laptop. The difference between a framework island and a custom element is small on a fast machine and large on a budget phone, and the budget phone is where your INP p75 comes from. A Lighthouse run with the default mobile throttling, or a WebPageTest run on a Moto G-class device, shows the change in Total Blocking Time within minutes.",[14,734,735],{},"Keep the old component until the new one has been live for a release. If a regression appears, switching the import back is a one-line change.",[27,737,739],{"id":738},"measured-impact","Measured Impact",[14,741,742],{},"On a 2,300-page documentation site built with Astro, the article template had three React islands: code-copy buttons, language tabs and a theme toggle. Replacing all three with custom elements removed React from the template. JavaScript on article pages fell from 118 KB to 6 KB compressed, Total Blocking Time in lab tests on a throttled phone dropped from 310 to 20 milliseconds, and field INP p75 on mobile improved from 240 to 110 milliseconds over the following month. The search page kept its React island, and the framework still loads there.",[27,744,746],{"id":745},"pitfalls-rollback","Pitfalls & Rollback",[32,748,749,758,772,778,784],{},[35,750,751,754,755,757],{},[702,752,753],{},"Rendering in JavaScript."," If the element builds its markup in ",[215,756,607],{},", content appears late and shifts layout; render at build time.",[35,759,760,763,764,767,768,771],{},[702,761,762],{},"Defining the element twice."," Calling ",[215,765,766],{},"customElements.define"," for an existing name throws; guard with ",[215,769,770],{},"customElements.get"," if scripts may load twice.",[35,773,774,777],{},[702,775,776],{},"Forgetting keyboard behaviour."," Frameworks' component libraries often handled it for you; test arrow keys, Home, End and focus order.",[35,779,780,783],{},[702,781,782],{},"Shared state between widgets."," If two widgets must stay in sync, use DOM events or a tiny store; if that gets complex, the island may be the better choice.",[35,785,786,789],{},[702,787,788],{},"Rollback:"," restore the island import; the build-time markup is compatible with both.",[27,791,793],{"id":792},"conclusion","Conclusion",[14,795,796],{},"Most interactive widgets on static content sites are small and self-contained, and for those a framework island is a heavy vehicle. Rendering the markup at build time and enhancing it with a custom element keeps the progressive-enhancement benefits of islands while dropping the runtime and hydration cost. Replace the simple widgets on your busiest template first, confirm the framework chunk disappears, and measure INP — the results are usually large for a small amount of code.",[27,798,800],{"id":799},"faq","FAQ",[802,803,805],"h3",{"id":804},"when-is-a-web-component-better-than-a-react-island","When is a web component better than a React island?",[14,807,808],{},"When the widget is small and self-contained — a copy button, tabs, a theme toggle, a disclosure — and the page has no other React. The component then ships a few hundred bytes of JavaScript instead of the 45 KB or so of compressed React and React DOM runtime plus the island's own code.",[802,810,812],{"id":811},"do-web-components-work-with-astro-and-other-static-site-generators","Do web components work with Astro and other static site generators?",[14,814,815],{},"Yes. A custom element is plain HTML plus a script, so it works in Astro, Hugo, Eleventy, Jekyll or any generator. In Astro, a script tag in a component is bundled and deduplicated automatically, so the element's class is defined once per page however many instances there are.",[802,817,819],{"id":818},"are-web-components-accessible","Are web components accessible?",[14,821,822],{},"They are as accessible as the HTML you put in them. Enhancing server-rendered buttons, links and headings keeps native semantics and keyboard behaviour; shadow DOM does not block screen readers, but labels and ARIA references cannot cross the shadow boundary, so light DOM is simpler for most widgets.",[802,824,826],{"id":825},"do-i-lose-server-side-rendering-with-custom-elements","Do I lose server-side rendering with custom elements?",[14,828,829],{},"No, if you render the markup at build time and have the element enhance it. The HTML is visible before any JavaScript runs, which is the same progressive-enhancement model as an island, without a framework hydration step.",[27,831,833],{"id":832},"related","Related",[32,835,836,845,852,859,866],{},[35,837,838,841,842,844],{},[702,839,840],{},"Parent:"," ",[21,843,24],{"href":23}," — the full hydration strategy.",[35,846,847,851],{},[21,848,850],{"href":849},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance\u002F","Astro Islands vs Full Hydration Performance"," — why islands beat full hydration.",[35,853,854,858],{},[21,855,857],{"href":856},"\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"," — for islands you keep.",[35,860,861,865],{},[21,862,864],{"href":863},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fmeasuring-inp-on-static-sites-with-real-user-monitoring\u002F","Measuring INP on Static Sites with Real User Monitoring"," — confirming the gain.",[35,867,868,872],{},[21,869,871],{"href":870},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors\u002F","Shortcodes vs Components for Docs Authors"," — how authors insert the widgets.",[874,875,876],"style",{},"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":225,"searchDepth":238,"depth":238,"links":878},[879,880,881,882,883,884,885,886,887,888,894],{"id":29,"depth":238,"text":30},{"id":50,"depth":238,"text":51},{"id":206,"depth":238,"text":207},{"id":479,"depth":238,"text":480},{"id":600,"depth":238,"text":601},{"id":691,"depth":238,"text":692},{"id":738,"depth":238,"text":739},{"id":745,"depth":238,"text":746},{"id":792,"depth":238,"text":793},{"id":799,"depth":238,"text":800,"children":889},[890,891,892,893],{"id":804,"depth":244,"text":805},{"id":811,"depth":244,"text":812},{"id":818,"depth":244,"text":819},{"id":825,"depth":244,"text":826},{"id":832,"depth":238,"text":833},[896,899,902,903],{"name":897,"item":898},"Home","\u002F",{"name":900,"item":901},"Performance Optimization & Core Web Vitals for SSGs","\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002F",{"name":24,"item":23},{"name":5,"item":904},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components\u002F","2026-09-18","Small interactive widgets rarely need React. Rewriting islands as custom elements removes the framework runtime, cuts JavaScript and improves INP.","md",[909,910,911,912],{"q":805,"a":808},{"q":812,"a":815},{"q":819,"a":822},{"q":826,"a":829},{},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components",{"title":5,"description":906},"performance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components\u002Findex","article","MxzUwa_itZPTjR8ratXX_kaMoCcIBPh7snRtfETmfoE",[920,923,926,929,932,934,937,940,943,946,949,952,955,958,961,964,967,970,973,976,979,982,985,988,991,994,997,1000,1003,1006,1009,1012,1015,1018,1021,1024,1027,1030,1033,1036,1039,1042,1045,1048,1051,1054,1057,1060,1063,1066,1069,1072,1075,1078,1081,1084,1087,1090,1093,1096,1099,1102,1105,1108,1111,1114,1117,1120,1123,1126,1129,1132,1135,1138,1141,1144,1147,1150,1153,1156,1159,1162,1164,1166,1169,1171,1174,1175,1178,1181,1184,1187,1190,1193,1196,1199,1202,1205,1208,1211,1214,1217,1220,1223,1226,1229,1232,1235,1238,1241,1244,1247,1250,1253,1256,1259,1262,1265,1268,1271,1274,1277,1280,1283,1286,1289,1292,1295,1298,1301,1304,1307,1310,1313,1316,1319,1322,1325,1328,1331,1334,1337,1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415,1418,1421,1424,1427,1430,1433,1436,1439,1442,1445,1448,1451,1454,1457,1460],{"path":921,"title":922},"\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":924,"title":925},"\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":927,"title":928},"\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":930,"title":931},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":933,"title":871},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors",{"path":935,"title":936},"\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":938,"title":939},"\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":941,"title":942},"\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":944,"title":945},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":947,"title":948},"\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":950,"title":951},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":953,"title":954},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":956,"title":957},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":959,"title":960},"\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":962,"title":963},"\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":965,"title":966},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":968,"title":969},"\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":971,"title":972},"\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":974,"title":975},"\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":977,"title":978},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":980,"title":981},"\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":983,"title":984},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":986,"title":987},"\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":989,"title":990},"\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":992,"title":993},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":995,"title":996},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":998,"title":999},"\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":1001,"title":1002},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1004,"title":1005},"\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":1007,"title":1008},"\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":1010,"title":1011},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1013,"title":1014},"\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":1016,"title":1017},"\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":1019,"title":1020},"\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":1022,"title":1023},"\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":1025,"title":1026},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1028,"title":1029},"\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":1031,"title":1032},"\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":1034,"title":1035},"\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":1037,"title":1038},"\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":1040,"title":1041},"\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":1043,"title":1044},"\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":1046,"title":1047},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1049,"title":1050},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1052,"title":1053},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1055,"title":1056},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1058,"title":1059},"\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":1061,"title":1062},"\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":1064,"title":1065},"\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":1067,"title":1068},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1070,"title":1071},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1073,"title":1074},"\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":1076,"title":1077},"\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":1079,"title":1080},"\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":1082,"title":1083},"\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":1085,"title":1086},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1088,"title":1089},"\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":1091,"title":1092},"\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":1094,"title":1095},"\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":1097,"title":1098},"\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":1100,"title":1101},"\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":1103,"title":1104},"\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":1106,"title":1107},"\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":1109,"title":1110},"\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":1112,"title":1113},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1115,"title":1116},"\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":1118,"title":1119},"\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":1121,"title":1122},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1124,"title":1125},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1127,"title":1128},"\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":1130,"title":1131},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1133,"title":1134},"\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":1136,"title":1137},"\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":1139,"title":1140},"\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":1142,"title":1143},"\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":1145,"title":1146},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1148,"title":1149},"\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":1151,"title":1152},"\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":1154,"title":1155},"\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":1157,"title":1158},"\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":1160,"title":1161},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1163,"title":850},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance",{"path":1165,"title":857},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fdeferring-hydration-with-client-visible-in-astro",{"path":1167,"title":1168},"\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":1170,"title":24},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering",{"path":1172,"title":1173},"\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":914,"title":5},{"path":1176,"title":1177},"\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":1179,"title":1180},"\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":1182,"title":1183},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1185,"title":1186},"\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":1188,"title":1189},"\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":1191,"title":1192},"\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":1194,"title":1195},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fcomparing-lab-and-field-data-with-crux","Comparing Lab and Field Data with CrUX",{"path":1197,"title":1198},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1200,"title":1201},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci","Reducing Lighthouse Score Variance in CI",{"path":1203,"title":1204},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Frunning-webpagetest-scripts-against-preview-deploys","Running WebPageTest Scripts Against Preview Deploys",{"path":1206,"title":1207},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site","Setting Up Lighthouse CI for a Static Site",{"path":1209,"title":1210},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-bundle-size-per-pull-request","Tracking Bundle Size per Pull Request",{"path":1212,"title":1213},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fwriting-a-performance-budget-that-fails-builds","Writing a Performance Budget That Fails Builds",{"path":1215,"title":1216},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1218,"title":1219},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1221,"title":1222},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1224,"title":1225},"\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":1227,"title":1228},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1230,"title":1231},"\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":1233,"title":1234},"\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":1236,"title":1237},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1239,"title":1240},"\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":1242,"title":1243},"\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":1245,"title":1246},"\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":1248,"title":1249},"\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":1251,"title":1252},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1254,"title":1255},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1257,"title":1258},"\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":1260,"title":1261},"\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":1263,"title":1264},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1266,"title":1267},"\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":1269,"title":1270},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1272,"title":1273},"\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":1275,"title":1276},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1278,"title":1279},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1281,"title":1282},"\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":1284,"title":1285},"\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":1287,"title":1288},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1290,"title":1291},"\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":1293,"title":1294},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1296,"title":1297},"\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":1299,"title":1300},"\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":1302,"title":1303},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1305,"title":1306},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1308,"title":1309},"\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":1311,"title":1312},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1314,"title":1315},"\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":1317,"title":1318},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1320,"title":1321},"\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":1323,"title":1324},"\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":1326,"title":1327},"\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":1329,"title":1330},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1332,"title":1333},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1335,"title":1336},"\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":1338,"title":1339},"\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":1341,"title":1342},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1344,"title":1345},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1347,"title":1348},"\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":1350,"title":1351},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1353,"title":1354},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1356,"title":1357},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1359,"title":1360},"\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":1362,"title":1363},"\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":1365,"title":1366},"\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":1368,"title":1369},"\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":1371,"title":1372},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1374,"title":1375},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1377,"title":1378},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1380,"title":1381},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1383,"title":1384},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1386,"title":1387},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1389,"title":1390},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1392,"title":1393},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1395,"title":1396},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1398,"title":1399},"\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":1401,"title":1402},"\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":1404,"title":1405},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1407,"title":1408},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1410,"title":1411},"\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":1413,"title":1414},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1416,"title":1417},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1419,"title":1420},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1422,"title":1423},"\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":1425,"title":1426},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1428,"title":1429},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1431,"title":1432},"\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":1434,"title":1435},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1437,"title":1438},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1440,"title":1441},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1443,"title":1444},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1446,"title":1447},"\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":1449,"title":1450},"\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":1452,"title":1453},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1455,"title":1456},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1458,"title":1459},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1461,"title":1462},"\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",1789722848168]