[{"data":1,"prerenderedAt":1390},["ShallowReactive",2],{"page:\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fmeasuring-lcp-subparts-with-devtools":3,"all-docs-nav":851},{"id":4,"title":5,"body":6,"breadcrumb":827,"dateModified":837,"datePublished":837,"description":838,"extension":839,"faq":840,"meta":845,"navigation":452,"path":846,"seo":847,"slug":12,"stem":848,"type":849,"__hash__":850},"content\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fmeasuring-lcp-subparts-with-devtools\u002Findex.md","Measuring LCP Subparts with DevTools",{"type":7,"value":8,"toc":810},"minimark",[9,13,17,26,31,44,48,51,179,207,210,214,221,224,235,239,242,340,362,388,394,404,408,415,578,585,589,595,604,681,684,687,691,727,731,734,738,743,746,750,753,757,760,764,767,771,806],[10,11,5],"h1",{"id":12},"measuring-lcp-subparts-with-devtools",[14,15,16],"p",{},"Largest Contentful Paint is one number, but it is made of four very different parts. A 3-second LCP might be a slow server, an image that was discovered late, a large image that took long to download, or an image that downloaded quickly but waited for a script before it could paint. Each needs a different fix, and optimising the wrong one wastes a sprint. Splitting LCP into its subparts turns \"LCP is slow\" into \"the hero waited 900 milliseconds to start downloading\", which has an obvious remedy.",[14,18,19,20,25],{},"This guide shows where to read the subparts in Chrome DevTools and Lighthouse, how to collect them from real users, and what each pattern usually means on a static site. It is part of ",[21,22,24],"a",{"href":23},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002F","Largest Contentful Paint Optimization for Static Sites",".",[27,28,30],"h2",{"id":29},"prerequisites","Prerequisites",[32,33,34,38,41],"ul",{},[35,36,37],"li",{},"Chrome 129 or later for the LCP breakdown in the Performance panel.",[35,39,40],{},"A page whose LCP you want to improve, ideally with field data showing it is slow.",[35,42,43],{},"Optional: the web-vitals library installed for field measurement.",[27,45,47],{"id":46},"the-four-subparts","The Four Subparts",[14,49,50],{},"LCP is measured from navigation start to the moment the largest element in the viewport is painted. That span divides cleanly into four consecutive phases:",[52,53,54,175],"figure",{},[55,56,63,64,63,68,63,72,63,79],"svg",{"viewBox":57,"role":58,"ariaLabelledBy":59,"xmlns":62},"0 0 760 250","img",[60,61],"lcs-parts-title","lcs-parts-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[65,66,67],"title",{"id":60},"The four subparts of Largest Contentful Paint",[69,70,71],"desc",{"id":61},"A horizontal bar from navigation start to LCP split into four segments: time to first byte until the HTML's first byte arrives, resource load delay until the LCP image request starts, resource load duration until the image finishes downloading, and element render delay until it is painted.",[73,74],"rect",{"x":75,"y":75,"width":76,"height":77,"fill":78},"0","760","250","#ffffff",[80,81,83,84,83,92,83,99,83,104,83,109,83,114,83,120,83,124,83,128,83,132,83,138,83,142,83,145,83,148,83,151,83,154,83,157,83,160,83,165,83,170,63],"g",{"style":82},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[85,86,91],"text",{"x":87,"y":88,"fill":89,"style":90},"380","28","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","LCP = TTFB + load delay + load duration + render delay",[73,93],{"x":94,"y":95,"width":96,"height":94,"fill":97,"style":98},"40","70","190","#166a9e","fill-opacity:0.35",[73,100],{"x":101,"y":95,"width":102,"height":94,"fill":103,"style":98},"230","90","#d83b41",[73,105],{"x":106,"y":95,"width":107,"height":94,"fill":108,"style":98},"320","260","#3f6410",[73,110],{"x":111,"y":95,"width":112,"height":94,"fill":113,"style":98},"580","140","#6a4c93",[85,115,119],{"x":116,"y":117,"fill":89,"style":118},"135","95","font-weight:700;text-anchor:middle","TTFB",[85,121,123],{"x":122,"y":117,"fill":89,"style":118},"275","load delay",[85,125,127],{"x":126,"y":117,"fill":89,"style":118},"450","load duration",[85,129,131],{"x":130,"y":117,"fill":89,"style":118},"650","render delay",[85,133,137],{"x":116,"y":134,"fill":135,"style":136},"136","#556071","text-anchor:middle","server, CDN,",[85,139,141],{"x":116,"y":140,"fill":135,"style":136},"152","redirects",[85,143,144],{"x":122,"y":134,"fill":135,"style":136},"late discovery,",[85,146,147],{"x":122,"y":140,"fill":135,"style":136},"lazy, low priority",[85,149,150],{"x":126,"y":134,"fill":135,"style":136},"file size, format,",[85,152,153],{"x":126,"y":140,"fill":135,"style":136},"bandwidth contention",[85,155,156],{"x":130,"y":134,"fill":135,"style":136},"blocking CSS\u002FJS,",[85,158,159],{"x":130,"y":140,"fill":135,"style":136},"fonts, animations",[85,161,164],{"x":94,"y":162,"fill":135,"style":163},"186","font-size:11px","navigation start",[85,166,169],{"x":167,"y":162,"fill":135,"style":168},"720","font-size:11px;text-anchor:end","LCP painted",[85,171,174],{"x":87,"y":172,"fill":135,"style":173},"222","font-size:11px;text-anchor:middle","healthy target: TTFB ≈ 40%, load duration ≈ 40%, each delay under 10%",[176,177,178],"figcaption",{},"The two delays are waste; the other two are real work that can only be made smaller.",[180,181,182,189,195,201],"ol",{},[35,183,184,188],{},[185,186,187],"strong",{},"Time to first byte (TTFB)."," From navigation start until the first byte of HTML arrives. Includes redirects, DNS, connection setup and server or CDN response time.",[35,190,191,194],{},[185,192,193],{},"Resource load delay."," From TTFB until the browser starts requesting the LCP resource. Zero for text elements.",[35,196,197,200],{},[185,198,199],{},"Resource load duration."," How long the LCP image or video poster takes to download. Zero for text elements.",[35,202,203,206],{},[185,204,205],{},"Element render delay."," From the end of the download (or TTFB, for text) until the element is painted.",[14,208,209],{},"The two delays are waiting time: nothing useful happens for the LCP element during them. TTFB and load duration are real work that can be made faster but never removed.",[27,211,213],{"id":212},"reading-the-breakdown-in-devtools","Reading the Breakdown in DevTools",[14,215,216,217,220],{},"Open the Performance panel. The live metrics view shows LCP for the current page along with the element; interact with nothing and reload. Then click record, reload, and stop once the page settles. In the Insights sidebar, open ",[185,218,219],{},"LCP breakdown",". It lists the four phases with durations and highlights the LCP element in the trace.",[14,222,223],{},"Emulate a realistic device first. The default desktop profile hides most problems, so choose a mobile device, set CPU throttling to 4× and network to \"Fast 4G\", or use the field data calibration that the live metrics view suggests when CrUX data is available for your origin.",[14,225,226,227,230,231,25],{},"Lighthouse reports the same breakdown under the ",[185,228,229],{},"Largest Contentful Paint element"," audit, with a table of the four phases. It is useful in CI, where you can track each phase over time rather than only the total; see ",[21,232,234],{"href":233},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site\u002F","Setting Up Lighthouse CI for a Static Site",[27,236,238],{"id":237},"common-patterns-on-static-sites","Common Patterns on Static Sites",[14,240,241],{},"Once you have the four numbers, the dominant phase usually points straight at the cause.",[52,243,244,337],{},[55,245,63,250,63,253,63,256,63,259],{"viewBox":246,"role":58,"ariaLabelledBy":247,"xmlns":62},"0 0 760 290",[248,249],"lcs-pat-title","lcs-pat-desc",[65,251,252],{"id":248},"Four LCP breakdowns and what they indicate",[69,254,255],{"id":249},"Four stacked bars. A slow TTFB bar with a large first segment indicates a CDN miss or redirects. A large load delay bar indicates a lazy or CSS background hero. A large load duration bar indicates an oversized image. A large render delay bar indicates render-blocking CSS, a font or a client-rendered hero.",[73,257],{"x":75,"y":75,"width":76,"height":258,"fill":78},"290",[80,260,83,261,83,265,83,270,83,276,83,279,83,283,83,285,83,290,83,293,83,298,83,301,83,304,83,308,83,311,83,313,83,315,83,318,83,323,83,326,83,328,83,330,83,334,63],{"style":82},[85,262,264],{"x":87,"y":263,"fill":89,"style":90},"26","Which subpart dominates, and the usual cause",[85,266,269],{"x":267,"y":268,"fill":89},"60","66","CDN miss, redirect chain",[73,271],{"x":272,"y":273,"width":107,"height":274,"fill":97,"style":275},"200","54","20","fill-opacity:0.45",[73,277],{"x":278,"y":273,"width":274,"height":274,"fill":103,"style":98},"460",[73,280],{"x":281,"y":273,"width":282,"height":274,"fill":108,"style":98},"480","100",[73,284],{"x":111,"y":273,"width":274,"height":274,"fill":113,"style":98},[85,286,289],{"x":287,"y":288,"fill":89},"30","126","lazy or background-image hero",[73,291],{"x":272,"y":292,"width":282,"height":274,"fill":97,"style":98},"114",[73,294],{"x":295,"y":292,"width":296,"height":274,"fill":103,"style":297},"300","240","fill-opacity:0.5",[73,299],{"x":300,"y":292,"width":282,"height":274,"fill":108,"style":98},"540",[73,302],{"x":303,"y":292,"width":274,"height":274,"fill":113,"style":98},"640",[85,305,307],{"x":306,"y":162,"fill":89},"105","oversized image",[73,309],{"x":272,"y":310,"width":282,"height":274,"fill":97,"style":98},"174",[73,312],{"x":295,"y":310,"width":274,"height":274,"fill":103,"style":98},[73,314],{"x":106,"y":310,"width":295,"height":274,"fill":108,"style":297},[73,316],{"x":317,"y":310,"width":274,"height":274,"fill":113,"style":98},"620",[85,319,322],{"x":320,"y":321,"fill":89},"37","246","blocking CSS, font, JS render",[73,324],{"x":272,"y":325,"width":282,"height":274,"fill":97,"style":98},"234",[73,327],{"x":295,"y":325,"width":274,"height":274,"fill":103,"style":98},[73,329],{"x":106,"y":325,"width":282,"height":274,"fill":108,"style":98},[73,331],{"x":332,"y":325,"width":333,"height":274,"fill":113,"style":297},"420","280",[85,335,336],{"x":87,"y":333,"fill":135,"style":173},"segment order: TTFB, load delay, load duration, render delay",[176,338,339],{},"Each shape has a different fix; the breakdown tells you which one to reach for.",[14,341,342,345,346,350,351,350,354,357,358,25],{},[185,343,344],{},"Long TTFB."," On a static site, the HTML should come from a CDN edge in well under 200 milliseconds. Long TTFB usually means the HTML is not cached at the edge, there are redirects (such as ",[347,348,349],"code",{},"http"," to ",[347,352,353],{},"https",[347,355,356],{},"www"," to a trailing slash), or the cache is being bypassed by query strings. See ",[21,359,361],{"href":360},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002F","CDN Caching Rules for SSGs",[14,363,364,367,368,371,372,375,376,379,380,383,384,25],{},[185,365,366],{},"Long resource load delay."," The browser found the image late. Causes: ",[347,369,370],{},"loading=\"lazy\""," on the hero, the hero set as a CSS ",[347,373,374],{},"background-image",", the image inserted by JavaScript, or a low fetch priority behind other images. Fixes: an eager ",[347,377,378],{},"\u003Cimg>"," in the HTML with ",[347,381,382],{},"fetchpriority=\"high\"",", or a preload for background images. See ",[21,385,387],{"href":386},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Flazy-loading-images-without-hurting-lcp\u002F","Lazy-Loading Images Without Hurting LCP",[14,389,390,393],{},[185,391,392],{},"Long resource load duration."," The file is too big for the connection, or it shares bandwidth with many other early requests. Fixes: responsive widths, AVIF or WebP, and fewer competing requests early in the load.",[14,395,396,399,400,25],{},[185,397,398],{},"Long render delay."," The image arrived but could not paint. Causes: render-blocking stylesheets still downloading, a web font blocking text for text LCP elements, a hero that fades in from zero opacity, or client-side rendering that inserts the element after hydration. See ",[21,401,403],{"href":402},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Feliminating-render-blocking-css-on-static-sites\u002F","Eliminating Render-Blocking CSS on Static Sites",[27,405,407],{"id":406},"collecting-subparts-from-real-users","Collecting Subparts From Real Users",[14,409,410,411,414],{},"Lab traces show one device on one connection. Field data shows which subpart dominates for your actual readers, and it can differ. The attribution build of ",[347,412,413],{},"web-vitals"," reports all four values:",[416,417,422],"pre",{"className":418,"code":419,"language":420,"meta":421,"style":421},"language-js shiki shiki-themes github-light github-dark","import { onLCP } from 'web-vitals\u002Fattribution';\n\nonLCP(({ value, attribution }) => {\n  navigator.sendBeacon('\u002Frum', JSON.stringify({\n    metric: 'LCP',\n    value,\n    page: location.pathname,\n    element: attribution.target,\n    ttfb: attribution.timeToFirstByte,\n    loadDelay: attribution.resourceLoadDelay,\n    loadDuration: attribution.resourceLoadDuration,\n    renderDelay: attribution.elementRenderDelay,\n  }));\n});\n","js","",[347,423,424,447,454,483,512,524,530,536,542,548,554,560,566,572],{"__ignoreMap":421},[425,426,429,433,437,440,444],"span",{"class":427,"line":428},"line",1,[425,430,432],{"class":431},"szBVR","import",[425,434,436],{"class":435},"sVt8B"," { onLCP } ",[425,438,439],{"class":431},"from",[425,441,443],{"class":442},"sZZnC"," 'web-vitals\u002Fattribution'",[425,445,446],{"class":435},";\n",[425,448,450],{"class":427,"line":449},2,[425,451,453],{"emptyLinePlaceholder":452},true,"\n",[425,455,457,461,464,468,471,474,477,480],{"class":427,"line":456},3,[425,458,460],{"class":459},"sScJk","onLCP",[425,462,463],{"class":435},"(({ ",[425,465,467],{"class":466},"s4XuR","value",[425,469,470],{"class":435},", ",[425,472,473],{"class":466},"attribution",[425,475,476],{"class":435}," }) ",[425,478,479],{"class":431},"=>",[425,481,482],{"class":435}," {\n",[425,484,486,489,492,495,498,500,504,506,509],{"class":427,"line":485},4,[425,487,488],{"class":435},"  navigator.",[425,490,491],{"class":459},"sendBeacon",[425,493,494],{"class":435},"(",[425,496,497],{"class":442},"'\u002Frum'",[425,499,470],{"class":435},[425,501,503],{"class":502},"sj4cs","JSON",[425,505,25],{"class":435},[425,507,508],{"class":459},"stringify",[425,510,511],{"class":435},"({\n",[425,513,515,518,521],{"class":427,"line":514},5,[425,516,517],{"class":435},"    metric: ",[425,519,520],{"class":442},"'LCP'",[425,522,523],{"class":435},",\n",[425,525,527],{"class":427,"line":526},6,[425,528,529],{"class":435},"    value,\n",[425,531,533],{"class":427,"line":532},7,[425,534,535],{"class":435},"    page: location.pathname,\n",[425,537,539],{"class":427,"line":538},8,[425,540,541],{"class":435},"    element: attribution.target,\n",[425,543,545],{"class":427,"line":544},9,[425,546,547],{"class":435},"    ttfb: attribution.timeToFirstByte,\n",[425,549,551],{"class":427,"line":550},10,[425,552,553],{"class":435},"    loadDelay: attribution.resourceLoadDelay,\n",[425,555,557],{"class":427,"line":556},11,[425,558,559],{"class":435},"    loadDuration: attribution.resourceLoadDuration,\n",[425,561,563],{"class":427,"line":562},12,[425,564,565],{"class":435},"    renderDelay: attribution.elementRenderDelay,\n",[425,567,569],{"class":427,"line":568},13,[425,570,571],{"class":435},"  }));\n",[425,573,575],{"class":427,"line":574},14,[425,576,577],{"class":435},"});\n",[14,579,580,581,25],{},"Aggregate by template and look at the 75th percentile of each subpart for pages whose LCP is poor. That tells you which fix will move the needle for the pages that matter. The dashboard side is covered in ",[21,582,584],{"href":583},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fbuilding-a-core-web-vitals-dashboard-from-rum-data\u002F","Building a Core Web Vitals Dashboard from RUM Data",[27,586,588],{"id":587},"worked-example","Worked Example",[14,590,591,592,594],{},"A product documentation site had a mobile LCP p75 of 3.2 seconds on its landing pages. The lab breakdown on a throttled phone showed TTFB 310 ms, load delay 1,080 ms, load duration 620 ms and render delay 140 ms. Load delay dominated, so the team looked for late discovery and found the hero set as a CSS ",[347,593,374],{}," on a section element. The browser could only find it after downloading and parsing the stylesheet.",[14,596,597,598,600,601,603],{},"Replacing the background with an ",[347,599,378],{}," carrying ",[347,602,382],{}," cut the load delay to 60 ms. Nothing else on the page changed, which is what made the breakdown useful: the total improved by almost exactly the amount the one subpart shrank, confirming the diagnosis.",[52,605,606,678],{},[55,607,63,612,63,615,63,618,63,621],{"viewBox":608,"role":58,"ariaLabelledBy":609,"xmlns":62},"0 0 760 220",[610,611],"lcs-ex-title","lcs-ex-desc",[65,613,614],{"id":610},"Lab LCP breakdown before and after moving the hero out of CSS",[69,616,617],{"id":611},"Before: TTFB 310 milliseconds, load delay 1080, load duration 620, render delay 140, total 2150. After: TTFB 310, load delay 60, load duration 620, render delay 140, total 1130.",[73,619],{"x":75,"y":75,"width":76,"height":620,"fill":78},"220",[80,622,83,623,83,626,83,631,83,637,83,641,83,645,83,648,83,652,83,655,83,659,83,661,83,664,83,667,83,670,83,675,63],{"style":82},[85,624,625],{"x":87,"y":88,"fill":89,"style":90},"Lab breakdown, throttled phone (ms)",[85,627,630],{"x":628,"y":629,"fill":89},"77","76","before",[73,632],{"x":633,"y":267,"width":634,"height":635,"fill":97,"style":636},"120","62","24","fill-opacity:0.4",[73,638],{"x":639,"y":267,"width":640,"height":635,"fill":103,"style":297},"182","216",[73,642],{"x":643,"y":267,"width":644,"height":635,"fill":108,"style":636},"398","124",[73,646],{"x":647,"y":267,"width":88,"height":635,"fill":113,"style":636},"522",[85,649,651],{"x":650,"y":628,"fill":89},"560","2,150",[85,653,654],{"x":258,"y":628,"fill":89,"style":136},"load delay 1,080",[85,656,658],{"x":657,"y":134,"fill":89},"86","after",[73,660],{"x":633,"y":633,"width":634,"height":635,"fill":97,"style":636},[73,662],{"x":639,"y":633,"width":663,"height":635,"fill":103,"style":297},"12",[73,665],{"x":666,"y":633,"width":644,"height":635,"fill":108,"style":636},"194",[73,668],{"x":669,"y":633,"width":88,"height":635,"fill":113,"style":636},"318",[85,671,674],{"x":672,"y":673,"fill":89},"356","137","1,130",[85,676,677],{"x":87,"y":96,"fill":135,"style":173},"TTFB 310 · load duration 620 · render delay 140 unchanged in both runs",[176,679,680],{},"Only one subpart moved, and the total moved with it.",[14,682,683],{},"The lab result was a prediction; the field was the test. Because field LCP includes slower phones, worse networks and CDN misses, the team expected a smaller gain in the field than in the lab, and tracked the load delay subpart in their RUM data to confirm the change reached real readers.",[14,685,686],{},"Field data four weeks later showed LCP p75 of 2.1 seconds, with the remaining time split roughly evenly between TTFB and load duration — the healthy shape. A second round of work on image sizes then took it to 1.8 seconds.",[27,688,690],{"id":689},"pitfalls-rollback","Pitfalls & Rollback",[32,692,693,699,705,715,721],{},[35,694,695,698],{},[185,696,697],{},"Measuring on desktop only."," Subparts shift dramatically under throttling; always check a mobile profile.",[35,700,701,704],{},[185,702,703],{},"Changing LCP elements."," If a fix changes which element is largest, the breakdown now describes a different element; re-check which one it is.",[35,706,707,710,711,25],{},[185,708,709],{},"Ignoring text LCP."," On text-heavy pages, all time after TTFB is render delay; fonts and CSS are the levers, not images. See ",[21,712,714],{"href":713},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-on-text-heavy-documentation-pages\u002F","Fixing LCP on Text-Heavy Documentation Pages",[35,716,717,720],{},[185,718,719],{},"Cached repeat views."," Test cold loads; warm caches hide load delay and duration.",[35,722,723,726],{},[185,724,725],{},"Rollback:"," measurement changes nothing on the page; remove the RUM snippet if it is no longer needed.",[27,728,730],{"id":729},"conclusion","Conclusion",[14,732,733],{},"LCP subparts turn a single slow number into a diagnosis. Read them in the DevTools Performance panel or Lighthouse for a quick lab view, collect them with the web-vitals attribution build for the real picture, and fix the phase that dominates: caching and redirects for TTFB, discovery and priority for load delay, file size for load duration, and blocking resources for render delay. The goal is a breakdown with almost no waiting time in it.",[27,735,737],{"id":736},"faq","FAQ",[739,740,742],"h3",{"id":741},"what-are-the-four-lcp-subparts","What are the four LCP subparts?",[14,744,745],{},"Time to first byte, resource load delay, resource load duration and element render delay. They add up to the full LCP time. For text LCP elements with no resource to load, the two resource phases are zero and the time after TTFB is all render delay.",[739,747,749],{"id":748},"where-do-i-see-lcp-subparts-in-chrome-devtools","Where do I see LCP subparts in Chrome DevTools?",[14,751,752],{},"In the Performance panel, the live metrics view and a recorded trace both show an LCP breakdown insight with the four phases for the current LCP element. The same breakdown appears in Lighthouse under the Largest Contentful Paint element audit.",[739,754,756],{"id":755},"what-is-a-good-split-between-the-subparts","What is a good split between the subparts?",[14,758,759],{},"As a rough guide, TTFB and load duration should each take about 40 percent of LCP, and load delay and render delay should each be under 10 percent. Large load delay or render delay usually point to fixable problems in the page rather than the network.",[739,761,763],{"id":762},"how-do-i-collect-lcp-subparts-from-real-users","How do I collect LCP subparts from real users?",[14,765,766],{},"Use the attribution build of the web-vitals library. Its onLCP callback reports timeToFirstByte, resourceLoadDelay, resourceLoadDuration and elementRenderDelay along with the LCP element selector, which you can send to your analytics endpoint.",[27,768,770],{"id":769},"related","Related",[32,772,773,782,789,794,799],{},[35,774,775,778,779,781],{},[185,776,777],{},"Parent:"," ",[21,780,24],{"href":23}," — every LCP fix in one place.",[35,783,784,788],{},[21,785,787],{"href":786},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Freducing-lcp-from-hero-images-on-static-sites\u002F","Reducing LCP from Hero Images on Static Sites"," — fixing load delay and duration.",[35,790,791,793],{},[21,792,403],{"href":402}," — fixing render delay.",[35,795,796,798],{},[21,797,714],{"href":713}," — when the LCP element is text.",[35,800,801,805],{},[21,802,804],{"href":803},"\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"," — why the two disagree.",[807,808,809],"style",{},"html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}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":421,"searchDepth":449,"depth":449,"links":811},[812,813,814,815,816,817,818,819,820,826],{"id":29,"depth":449,"text":30},{"id":46,"depth":449,"text":47},{"id":212,"depth":449,"text":213},{"id":237,"depth":449,"text":238},{"id":406,"depth":449,"text":407},{"id":587,"depth":449,"text":588},{"id":689,"depth":449,"text":690},{"id":729,"depth":449,"text":730},{"id":736,"depth":449,"text":737,"children":821},[822,823,824,825],{"id":741,"depth":456,"text":742},{"id":748,"depth":456,"text":749},{"id":755,"depth":456,"text":756},{"id":762,"depth":456,"text":763},{"id":769,"depth":449,"text":770},[828,831,834,835],{"name":829,"item":830},"Home","\u002F",{"name":832,"item":833},"Performance Optimization & Core Web Vitals for SSGs","\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002F",{"name":24,"item":23},{"name":5,"item":836},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fmeasuring-lcp-subparts-with-devtools\u002F","2026-09-18","Split Largest Contentful Paint into TTFB, load delay, load duration and render delay in DevTools and field data, so you fix the part that is actually slow.","md",[841,842,843,844],{"q":742,"a":745},{"q":749,"a":752},{"q":756,"a":759},{"q":763,"a":766},{},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fmeasuring-lcp-subparts-with-devtools",{"title":5,"description":838},"performance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fmeasuring-lcp-subparts-with-devtools\u002Findex","article","ygeSnjUQserp_IDyOZ6RxoBVRAz29iAG6ZGSMqRRRbI",[852,855,858,861,864,867,870,873,876,879,882,885,888,891,894,897,900,903,906,909,912,915,918,921,924,927,930,933,936,939,942,945,948,951,954,957,960,963,966,969,972,975,978,981,984,987,990,993,996,999,1002,1005,1008,1011,1014,1017,1019,1022,1025,1028,1031,1034,1037,1040,1043,1046,1049,1052,1055,1058,1061,1064,1067,1070,1073,1076,1079,1081,1084,1087,1090,1093,1096,1099,1102,1105,1108,1111,1113,1115,1117,1118,1121,1123,1125,1128,1131,1134,1136,1139,1142,1145,1148,1151,1154,1157,1160,1163,1166,1169,1172,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,1264,1267,1270,1273,1276,1279,1282,1285,1288,1291,1294,1297,1300,1303,1306,1309,1312,1315,1318,1321,1324,1327,1330,1333,1336,1339,1342,1345,1348,1351,1354,1357,1360,1363,1366,1369,1372,1375,1378,1381,1384,1387],{"path":853,"title":854},"\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":856,"title":857},"\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":859,"title":860},"\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":862,"title":863},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":865,"title":866},"\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":868,"title":869},"\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":871,"title":872},"\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":874,"title":875},"\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":877,"title":878},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":880,"title":881},"\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":883,"title":884},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":886,"title":887},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":889,"title":890},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":892,"title":893},"\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":895,"title":896},"\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":898,"title":899},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":901,"title":902},"\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":904,"title":905},"\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":907,"title":908},"\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":910,"title":911},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":913,"title":914},"\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":916,"title":917},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":919,"title":920},"\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":922,"title":923},"\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":925,"title":926},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":928,"title":929},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":931,"title":932},"\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":934,"title":935},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":937,"title":938},"\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":940,"title":941},"\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":943,"title":944},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":946,"title":947},"\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":949,"title":950},"\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":952,"title":953},"\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":955,"title":956},"\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":958,"title":959},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":961,"title":962},"\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":964,"title":965},"\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":967,"title":968},"\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":970,"title":971},"\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":973,"title":974},"\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":976,"title":977},"\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":979,"title":980},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":982,"title":983},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":985,"title":986},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":988,"title":989},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":991,"title":992},"\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":994,"title":995},"\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":997,"title":998},"\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":1000,"title":1001},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1003,"title":1004},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1006,"title":1007},"\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":1009,"title":1010},"\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":1012,"title":1013},"\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":1015,"title":1016},"\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":1018,"title":361},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs",{"path":1020,"title":1021},"\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":1023,"title":1024},"\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":1026,"title":1027},"\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":1029,"title":1030},"\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":1032,"title":1033},"\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":1035,"title":1036},"\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":1038,"title":1039},"\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":1041,"title":1042},"\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":1044,"title":1045},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1047,"title":1048},"\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":1050,"title":1051},"\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":1053,"title":1054},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1056,"title":1057},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1059,"title":1060},"\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":1062,"title":1063},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1065,"title":1066},"\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":1068,"title":1069},"\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":1071,"title":1072},"\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":1074,"title":1075},"\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":1077,"title":1078},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1080,"title":387},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Flazy-loading-images-without-hurting-lcp",{"path":1082,"title":1083},"\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":1085,"title":1086},"\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":1088,"title":1089},"\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":1091,"title":1092},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1094,"title":1095},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1097,"title":1098},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fdeferring-hydration-with-client-visible-in-astro","Deferring Hydration with client:visible in Astro",{"path":1100,"title":1101},"\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":1103,"title":1104},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1106,"title":1107},"\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":1109,"title":1110},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1112,"title":403},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Feliminating-render-blocking-css-on-static-sites",{"path":1114,"title":714},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-on-text-heavy-documentation-pages",{"path":1116,"title":24},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites",{"path":846,"title":5},{"path":1119,"title":1120},"\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":1122,"title":787},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Freducing-lcp-from-hero-images-on-static-sites",{"path":1124,"title":804},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fcomparing-lab-and-field-data-with-crux",{"path":1126,"title":1127},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1129,"title":1130},"\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":1132,"title":1133},"\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":1135,"title":234},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site",{"path":1137,"title":1138},"\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":1140,"title":1141},"\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":1143,"title":1144},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1146,"title":1147},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1149,"title":1150},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1152,"title":1153},"\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":1155,"title":1156},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1158,"title":1159},"\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":1161,"title":1162},"\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":1164,"title":1165},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1167,"title":1168},"\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":1170,"title":1171},"\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":1173,"title":1174},"\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":1176,"title":1177},"\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":1179,"title":1180},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1182,"title":1183},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1185,"title":1186},"\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":1188,"title":1189},"\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":1191,"title":1192},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1194,"title":1195},"\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":1197,"title":1198},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1200,"title":1201},"\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":1203,"title":1204},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1206,"title":1207},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1209,"title":1210},"\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":1212,"title":1213},"\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":1215,"title":1216},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1218,"title":1219},"\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":1221,"title":1222},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1224,"title":1225},"\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":1227,"title":1228},"\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":1230,"title":1231},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1233,"title":1234},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1236,"title":1237},"\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":1239,"title":1240},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1242,"title":1243},"\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":1245,"title":1246},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1248,"title":1249},"\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":1251,"title":1252},"\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":1254,"title":1255},"\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":1257,"title":1258},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1260,"title":1261},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1263,"title":584},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fbuilding-a-core-web-vitals-dashboard-from-rum-data",{"path":1265,"title":1266},"\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":1268,"title":1269},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1271,"title":1272},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1274,"title":1275},"\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":1277,"title":1278},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1280,"title":1281},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1283,"title":1284},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1286,"title":1287},"\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":1289,"title":1290},"\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":1292,"title":1293},"\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":1295,"title":1296},"\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":1298,"title":1299},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1301,"title":1302},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1304,"title":1305},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1307,"title":1308},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1310,"title":1311},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1313,"title":1314},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1316,"title":1317},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1319,"title":1320},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1322,"title":1323},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1325,"title":1326},"\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":1328,"title":1329},"\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":1331,"title":1332},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1334,"title":1335},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1337,"title":1338},"\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":1340,"title":1341},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1343,"title":1344},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1346,"title":1347},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1349,"title":1350},"\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":1352,"title":1353},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1355,"title":1356},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1358,"title":1359},"\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":1361,"title":1362},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1364,"title":1365},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1367,"title":1368},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1370,"title":1371},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1373,"title":1374},"\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":1376,"title":1377},"\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":1379,"title":1380},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1382,"title":1383},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1385,"title":1386},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1388,"title":1389},"\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",1789722847974]