[{"data":1,"prerenderedAt":972},["ShallowReactive",2],{"blog-post-/blogs/storefront-requests-531-to-101":3,"blog-list":676},{"id":4,"title":5,"body":6,"description":657,"extension":658,"meta":659,"navigation":481,"ogImage":671,"path":672,"seo":673,"stem":674,"__hash__":675},"content/blogs/30. storefront-requests-531-to-101.md","531 Requests on a Homepage — Cutting a Headless Storefront Down to 101",{"type":7,"value":8,"toc":643},"minimark",[9,22,33,38,41,69,72,76,81,94,97,264,268,275,339,346,350,353,356,376,379,383,403,407,410,413,417,420,434,437,441,444,501,512,516,519,563,566,570,620,639],[10,11,12,13,17,18,21],"p",{},"The homepage of a headless storefront I work on loaded ",[14,15,16],"strong",{},"531 network requests"," on a mobile device and scored ",[14,19,20],{},"56"," in Lighthouse. The storefront is Shopware 6 with a Nuxt frontend, serving two brands from one backend. Nothing was broken. Pages rendered, orders came in. It was just slow, and it got a little slower with every feature.",[10,23,24,25,28,29,32],{},"After one batch of changes, deployed to production at the end of October, the same homepage loaded ",[14,26,27],{},"101 requests"," and scored ",[14,30,31],{},"88",". This post covers how I measured it, where the 430 extra requests came from, what I tried and reverted, and what to check in your own storefront. Client details are anonymized; the numbers are real.",[34,35,37],"h2",{"id":36},"measure-first-and-measure-where-it-counts","Measure First, and Measure Where It Counts",[10,39,40],{},"Before changing a line, I set up a benchmark I could re-run:",[42,43,44,51,57,63],"ul",{},[45,46,47,50],"li",{},[14,48,49],{},"Lighthouse mobile, three runs per page, median."," Single Lighthouse runs scatter too much to compare.",[45,52,53,56],{},[14,54,55],{},"The same seven pages every time:"," homepage, category pages, product pages of different types, a CMS page with videos.",[45,58,59,62],{},[14,60,61],{},"Against stage and production, never locally."," On an earlier project, a slow local backend made Lighthouse report an LCP of about 76 seconds while stage measured 3.1–4.1 seconds. A local benchmark measures your laptop's backend, not your shop.",[45,64,65,68],{},[14,66,67],{},"One script with the host as a variable",", so \"before\" and \"after\" run the exact same steps.",[10,70,71],{},"That baseline also gave the conversation with the client a different footing. \"It feels faster\" isn't something you can bill. \"Homepage from 56 to 88, requests from 531 to 101\" is.",[34,73,75],{"id":74},"where-531-requests-came-from","Where 531 Requests Came From",[77,78,80],"h3",{"id":79},"_1-every-component-was-global","1. Every Component Was Global",[10,82,83,84,88,89,93],{},"The Nuxt config had ",[85,86,87],"code",{},"components: { global: true }",". That registers ",[90,91,92],"em",{},"every"," component globally, so each one becomes its own chunk that the app has to know about up front, whether or not the page uses it.",[10,95,96],{},"The fix: only components resolved by a name built at runtime stay global. In a Shopware frontend those are the CMS elements, which are looked up by their CMS type name. Everything else is bundled with the component that imports it:",[98,99,104],"pre",{"className":100,"code":101,"language":102,"meta":103,"style":103},"language-ts shiki shiki-themes github-dark","// nuxt.config.ts\ncomponents: { global: false },\nhooks: {\n  'components:extend'(components) {\n    for (const component of components) {\n      // CMS elements are resolved by name at runtime and must stay global\n      if (/\\/components\\/(?:cms\\/|public\\/|errors\\/)/.test(component.filePath)) component.global = true\n    }\n  },\n},\n","ts","",[85,105,106,115,139,148,158,180,186,246,252,258],{"__ignoreMap":103},[107,108,111],"span",{"class":109,"line":110},"line",1,[107,112,114],{"class":113},"sAwPA","// nuxt.config.ts\n",[107,116,118,122,126,129,132,136],{"class":109,"line":117},2,[107,119,121],{"class":120},"svObZ","components",[107,123,125],{"class":124},"s95oV",": { ",[107,127,128],{"class":120},"global",[107,130,131],{"class":124},": ",[107,133,135],{"class":134},"sDLfK","false",[107,137,138],{"class":124}," },\n",[107,140,142,145],{"class":109,"line":141},3,[107,143,144],{"class":120},"hooks",[107,146,147],{"class":124},": {\n",[107,149,151,155],{"class":109,"line":150},4,[107,152,154],{"class":153},"sU2Wk","  'components:extend'",[107,156,157],{"class":124},"(components) {\n",[107,159,161,165,168,171,174,177],{"class":109,"line":160},5,[107,162,164],{"class":163},"snl16","    for",[107,166,167],{"class":124}," (",[107,169,170],{"class":163},"const",[107,172,173],{"class":134}," component",[107,175,176],{"class":163}," of",[107,178,179],{"class":124}," components) {\n",[107,181,183],{"class":109,"line":182},6,[107,184,185],{"class":113},"      // CMS elements are resolved by name at runtime and must stay global\n",[107,187,189,192,194,197,201,204,206,209,211,214,217,219,221,224,226,229,231,234,237,240,243],{"class":109,"line":188},7,[107,190,191],{"class":163},"      if",[107,193,167],{"class":124},[107,195,196],{"class":153},"/",[107,198,200],{"class":199},"sRjNt","\\/",[107,202,121],{"class":203},"sns5M",[107,205,200],{"class":199},[107,207,208],{"class":203},"(?:cms",[107,210,200],{"class":199},[107,212,213],{"class":163},"|",[107,215,216],{"class":203},"public",[107,218,200],{"class":199},[107,220,213],{"class":163},[107,222,223],{"class":203},"errors",[107,225,200],{"class":199},[107,227,228],{"class":203},")",[107,230,196],{"class":153},[107,232,233],{"class":124},".",[107,235,236],{"class":120},"test",[107,238,239],{"class":124},"(component.filePath)) component.global ",[107,241,242],{"class":163},"=",[107,244,245],{"class":134}," true\n",[107,247,249],{"class":109,"line":248},8,[107,250,251],{"class":124},"    }\n",[107,253,255],{"class":109,"line":254},9,[107,256,257],{"class":124},"  },\n",[107,259,261],{"class":109,"line":260},10,[107,262,263],{"class":124},"},\n",[77,265,267],{"id":266},"_2-about-160-prefetch-hints-per-page","2. About 160 Prefetch Hints per Page",[10,269,270,271,274],{},"The build emitted a speculative ",[85,272,273],{},"\u003Clink rel=\"prefetch\">"," for every lazy chunk and asset, around 160 hints per page. Prefetching sounds free, but on a mobile connection those downloads compete with the hero image and the CSS the page actually needs. Removing them from the build manifest means lazy chunks load when they're needed:",[98,276,278],{"className":100,"code":277,"language":102,"meta":103,"style":103},"'build:manifest'(manifest) {\n  for (const chunk of Object.values(manifest)) {\n    chunk.dynamicImports = []\n    chunk.assets = []\n  }\n},\n",[85,279,280,288,311,321,330,335],{"__ignoreMap":103},[107,281,282,285],{"class":109,"line":110},[107,283,284],{"class":153},"'build:manifest'",[107,286,287],{"class":124},"(manifest) {\n",[107,289,290,293,295,297,300,302,305,308],{"class":109,"line":117},[107,291,292],{"class":163},"  for",[107,294,167],{"class":124},[107,296,170],{"class":163},[107,298,299],{"class":134}," chunk",[107,301,176],{"class":163},[107,303,304],{"class":124}," Object.",[107,306,307],{"class":120},"values",[107,309,310],{"class":124},"(manifest)) {\n",[107,312,313,316,318],{"class":109,"line":141},[107,314,315],{"class":124},"    chunk.dynamicImports ",[107,317,242],{"class":163},[107,319,320],{"class":124}," []\n",[107,322,323,326,328],{"class":109,"line":150},[107,324,325],{"class":124},"    chunk.assets ",[107,327,242],{"class":163},[107,329,320],{"class":124},[107,331,332],{"class":109,"line":160},[107,333,334],{"class":124},"  }\n",[107,336,337],{"class":109,"line":182},[107,338,263],{"class":124},[10,340,341,342,345],{},"To keep navigation fast without blanket prefetching, a small client plugin now prefetches the ",[90,343,344],{},"data"," of a page when the user shows intent: 80 ms hovering over a link, or 50 ms on touch. The prefetched data is cached briefly and capped at 20 entries. It's cleared on login and logout, because prices depend on the customer group.",[77,347,349],{"id":348},"_3-product-cards-carried-the-full-product-page","3. Product Cards Carried the Full Product Page",[10,351,352],{},"This was the biggest single payload problem, and it sat in the backend. A product card in a listing shows a name, a price, an image and maybe a subtitle. The API sent the full product for every card: all translated fields, every custom field, category tree, stream IDs, property IDs, tax, manufacturer, every media thumbnail. Multiply that by a listing page and by the server-rendered payload Nuxt embeds in the HTML.",[10,354,355],{},"The fix came in three parts:",[42,357,358,364,370],{},[45,359,360,363],{},[14,361,362],{},"Mark card criteria."," Every place that loads products for cards (listings, product boxes, cross-selling, athlete recommendations) tags its criteria as \"card\".",[45,365,366,369],{},[14,367,368],{},"Skip detail-page enrichment"," for those products, and don't read description or SEO text fields from the database at all.",[45,371,372,375],{},[14,373,374],{},"Slim the result"," to what a card renders: the name, five specific custom fields, and the cover with its URL. The filter aggregations of the listing went the same way: option name, colour code and position, no descriptions or custom fields.",[10,377,378],{},"The second batch, a few days later, went further: media thumbnails nobody read in the CMS page payload, all sales-channel domains in the session context, unused fields in the language list. The fallback translation catalogue had been shipped twice, once on its own and once merged, and now ships once.",[77,380,382],{"id":381},"_4-third-party-scripts-running-before-the-page-was-usable","4. Third-Party Scripts Running Before the Page Was Usable",[42,384,385,391,397],{},[45,386,387,390],{},[14,388,389],{},"The cookie consent dialog"," is the LCP element for first-time visitors, and its stylesheet and texts only started loading after its script had run. Preload hints for both, chosen in the page's language, let them load in parallel.",[45,392,393,396],{},[14,394,395],{},"Sentry"," (second batch) now loads when the browser is idle after hydration, and only the parts in use are bundled.",[45,398,399,402],{},[14,400,401],{},"The search client"," (second batch) sat in the entry chunk. Now it loads with the search flyout, the first time someone opens search.",[77,404,406],{"id":405},"_5-hydration-competing-with-the-first-paint","5. Hydration Competing With the First Paint",[10,408,409],{},"The app's module scripts were moved out of the critical path. The server-rendered page paints first, and hydration starts after the load event, on the first interaction, or after 1.5 seconds, whichever comes first. Clicks on buttons before hydration are captured and replayed once the app is ready. Links keep working natively the whole time.",[10,411,412],{},"That's the riskiest change in the batch. A click that's swallowed and never replayed is worse than a slow page. It shipped with tests for the replay logic and a 15-second fallback that removes the guards if hydration never signals.",[34,414,416],{"id":415},"what-i-reverted","What I Reverted",[10,418,419],{},"Not everything that speeds up Lighthouse is worth keeping:",[42,421,422,428],{},[45,423,424,427],{},[14,425,426],{},"Skipping the rendering of off-screen product cards on mobile"," looked like an easy Total Blocking Time win. An interleaved A/B test on the deployed stage build, eight runs each, showed no gain: the category page's mobile median was 92.5 with and without it. Reverted the same day.",[45,429,430,433],{},[14,431,432],{},"Lazy hydration for a cross-selling block"," had been tried earlier. Four cards saved too little JavaScript to justify the extra test complexity, so it went back to normal hydration. Larger blocks on the product page kept it.",[10,435,436],{},"Every optimization adds code someone has to understand later. It has to save enough to pay for that.",[34,438,440],{"id":439},"a-bug-found-along-the-way","A Bug Found Along the Way",[10,442,443],{},"While reading the components for performance work, I found this:",[98,445,447],{"className":100,"code":446,"language":102,"meta":103,"style":103},"const smallerThanLG = breakpoints.smaller('lg') // a Ref\u003Cboolean>\n\nif (smallerThanLG) {\n  // always runs: a ref object is always truthy\n}\n",[85,448,449,477,483,491,496],{"__ignoreMap":103},[107,450,451,453,456,459,462,465,468,471,474],{"class":109,"line":110},[107,452,170],{"class":163},[107,454,455],{"class":134}," smallerThanLG",[107,457,458],{"class":163}," =",[107,460,461],{"class":124}," breakpoints.",[107,463,464],{"class":120},"smaller",[107,466,467],{"class":124},"(",[107,469,470],{"class":153},"'lg'",[107,472,473],{"class":124},") ",[107,475,476],{"class":113},"// a Ref\u003Cboolean>\n",[107,478,479],{"class":109,"line":117},[107,480,482],{"emptyLinePlaceholder":481},true,"\n",[107,484,485,488],{"class":109,"line":141},[107,486,487],{"class":163},"if",[107,489,490],{"class":124}," (smallerThanLG) {\n",[107,492,493],{"class":109,"line":150},[107,494,495],{"class":113},"  // always runs: a ref object is always truthy\n",[107,497,498],{"class":109,"line":160},[107,499,500],{"class":124},"}\n",[10,502,503,504,507,508,511],{},"A ",[85,505,506],{},"Ref"," is an object, and objects are always truthy. The condition never checked the breakpoint. The fix is ",[85,509,510],{},"smallerThanLG.value",". Then I searched the whole codebase for the same pattern: it appeared in exactly two components, and both were fixed together. When you find a bug like that, look for its siblings before you close the ticket.",[34,513,515],{"id":514},"results","Results",[10,517,518],{},"Production, Lighthouse mobile, median of three runs, measured after the deployment:",[520,521,522,544],"table",{},[523,524,525],"thead",{},[526,527,528,532,535,538,541],"tr",{},[529,530,531],"th",{},"Page",[529,533,534],{},"Performance before",[529,536,537],{},"Performance after",[529,539,540],{},"Requests before",[529,542,543],{},"Requests after",[545,546,547],"tbody",{},[526,548,549,553,555,557,560],{},[550,551,552],"td",{},"Homepage (brand A)",[550,554,20],{},[550,556,31],{},[550,558,559],{},"531",[550,561,562],{},"101",[10,564,565],{},"Other pages after the deployment: a product page at 99, a category page of the second brand at 96. One product-series page of the second brand is still at 74 with an LCP of 7.0 seconds, and that's the next ticket. The second batch (Sentry and search loading later, sliders that mount on first interaction, the footer skipped while off-screen, resized images requested as WebP so cold CDN misses skip JPEG) shipped after this measurement and isn't in the table.",[34,567,569],{"id":568},"checklist-for-your-storefront","Checklist for Your Storefront",[571,572,573,579,593,602,608,614],"ol",{},[45,574,575,578],{},[14,576,577],{},"Count requests on your mobile homepage."," Lighthouse or DevTools, with the cache disabled. Several hundred is a finding by itself.",[45,580,581,588,589,592],{},[14,582,583,584,587],{},"Check ",[85,585,586],{},"components.global"," in your Nuxt config."," If it's ",[85,590,591],{},"true",", find out which components really need it.",[45,594,595,598,599],{},[14,596,597],{},"Look for prefetch hints in your HTML."," ",[85,600,601],{},"curl -s https://your-shop.de | grep -c 'rel=\"prefetch\"'",[45,603,604,607],{},[14,605,606],{},"Look at one product card in your API response."," Count the fields the card actually renders and compare that to what's sent.",[45,609,610,613],{},[14,611,612],{},"List every third-party script"," and ask for each one: does it need to run before the page is usable?",[45,615,616,619],{},[14,617,618],{},"Benchmark on stage or production",", three runs per page, before and after each change. Not locally.",[10,621,622,623,628,629,633,634,638],{},"For more on the individual metrics, see ",[624,625,627],"a",{"href":626},"/blogs/core-web-vitals-inp-2026","mastering INP"," and the ",[624,630,632],{"href":631},"/blogs/lcp-debugging-case-study","LCP case study on this site",". If your storefront feels like this one did, a ",[624,635,637],{"href":636},"/contact","performance audit"," starts with exactly this benchmark.",[640,641,642],"style",{},"html pre.shiki code .sAwPA, html code.shiki .sAwPA{--shiki-default:#8B949E}html pre.shiki code .svObZ, html code.shiki .svObZ{--shiki-default:#B392F0}html pre.shiki code .s95oV, html code.shiki .s95oV{--shiki-default:#E1E4E8}html pre.shiki code .sDLfK, html code.shiki .sDLfK{--shiki-default:#79B8FF}html pre.shiki code .sU2Wk, html code.shiki .sU2Wk{--shiki-default:#9ECBFF}html pre.shiki code .snl16, html code.shiki .snl16{--shiki-default:#F97583}html pre.shiki code .sRjNt, html code.shiki .sRjNt{--shiki-default:#85E89D;--shiki-default-font-weight:bold}html pre.shiki code .sns5M, html code.shiki .sns5M{--shiki-default:#DBEDFF}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);}",{"title":103,"searchDepth":117,"depth":117,"links":644},[645,646,653,654,655,656],{"id":36,"depth":117,"text":37},{"id":74,"depth":117,"text":75,"children":647},[648,649,650,651,652],{"id":79,"depth":141,"text":80},{"id":266,"depth":141,"text":267},{"id":348,"depth":141,"text":349},{"id":381,"depth":141,"text":382},{"id":405,"depth":141,"text":406},{"id":415,"depth":117,"text":416},{"id":439,"depth":117,"text":440},{"id":514,"depth":117,"text":515},{"id":568,"depth":117,"text":569},"A headless Shopware 6 + Nuxt storefront loaded 531 requests on its mobile homepage and scored 56 in Lighthouse. After one batch of changes on production it was 101 requests and 88. How I measured, where the weight came from, what I reverted, and a checklist for your own storefront.","md",{"seoTitle":660,"date":661,"image":662,"imageWidth":663,"imageHeight":664,"alt":665,"tags":666,"author":669,"published":481,"featured":670},"Headless Storefront Performance: 531 to 101 Requests","29.10.2026","/blogs-img/storefront-requests.webp",1536,1024,"A storefront waterfall chart shrinking from a dense wall of requests to a short, tidy list, with a performance gauge moving from orange to green",[667,668],"performance","shopware","Marco Faul",false,"/blogs-img/storefront-requests.png","/blogs/storefront-requests-531-to-101",{"title":5,"description":657},"blogs/30. storefront-requests-531-to-101","AzzAmfm4G3cfKlw4YCPT2nBh-RSa9jdFoB3XYRQJg0I",[677,686,697,707,717,729,740,749,759,769,779,787,797,806,815,824,833,843,853,863,873,882,893,902,905,916,925,934,943,953,962],{"path":678,"title":679,"description":680,"meta":681},"/blogs/shopware-6-performance-guide","Shopware 6 Developer Performance Guide - Essential Improvements and Fixes","Performance optimization is crucial for any e-commerce platform. Here are the most impactful performance improvements and fixes for Shopware 6 developers.",{"seoTitle":682,"date":683,"image":684,"imageWidth":663,"imageHeight":664,"alt":679,"tags":685,"published":481,"featured":670},"Shopware 6 Performance Guide","24.10.2025","/blogs-img/shopware-performance.webp",[668,667],{"path":687,"title":688,"description":689,"meta":690},"/blogs/shopware-frontends-composable-storefront","Shopware Frontends - Building a Composable Storefront with Vue and Nuxt","Shopware Frontends is the official way to build headless storefronts on Shopware 6. Learn the Vue Starter Template, Nuxt layers, composables, and the Store API architecture.",{"seoTitle":691,"date":692,"image":693,"imageWidth":663,"imageHeight":664,"alt":694,"tags":695,"author":669,"published":481,"featured":670},"Shopware Frontends - Composable Storefronts","06.06.2026","/blogs-img/shopware-frontends.webp","Shopware Frontends composable storefront with Vue and Nuxt",[668,696],"frontend",{"path":698,"title":699,"description":700,"meta":701},"/blogs/headless-shopware-cost","What Does a Headless Shopware Store Really Cost? A Realistic 2026 Breakdown","Thinking about going headless with Shopware? An honest breakdown of what a headless storefront actually costs - build, hosting, maintenance - and when it pays off.",{"seoTitle":702,"date":703,"image":704,"imageWidth":663,"imageHeight":664,"alt":705,"tags":706,"author":669,"published":481,"featured":670},"What a Headless Shopware Store Really Costs","02.06.2026","/blogs-img/headless-cost.webp","What a headless Shopware store really costs in 2026",[668,696],{"path":708,"title":709,"description":710,"meta":711},"/blogs/headless-vs-traditional-shopware-2026","Headless vs. Traditional Shopware - How to Choose in 2026","Headless or the classic Twig storefront? A practical 2026 decision framework for Shopware 6 - performance, cost, flexibility, SEO, and team fit - with a clear recommendation.",{"seoTitle":712,"date":713,"image":714,"imageWidth":663,"imageHeight":664,"alt":715,"tags":716,"author":669,"published":481,"featured":670},"Headless vs. Traditional Shopware in 2026","30.05.2026","/blogs-img/headless-vs-traditional.webp","Headless vs traditional Shopware 6 decision framework 2026",[668,696],{"path":718,"title":719,"description":720,"meta":721},"/blogs/supply-chain-security-2026","The Supply Chain Is the New Attack Surface - npm Worms and Slopsquatting in 2026","A self-replicating npm worm and AI-hallucinated packages are the supply-chain threats hitting JavaScript developers right now. Here's how they work and how I lock my projects down.",{"seoTitle":722,"date":723,"image":724,"imageWidth":663,"imageHeight":664,"alt":725,"tags":726,"author":669,"published":481,"featured":481},"npm Worms and Slopsquatting - Supply Chain 2026","11.06.2026","/blogs-img/supply-chain-security.webp","npm supply chain worms and slopsquatting - 2026 developer security threats",[727,728],"security","devops",{"path":730,"title":731,"description":732,"meta":733},"/blogs/harness-vs-model","The Real Variable in AI Coding Isn't the Model — It's the Harness","Benchmarks show that switching edit formats improved Grok Code Fast by 10x — zero training compute required. As a developer who relies on AI agents daily, the harness deserves far more scrutiny than we give it.",{"seoTitle":734,"date":735,"image":736,"imageWidth":663,"imageHeight":664,"alt":737,"tags":738,"author":669,"published":481,"featured":481},"AI Coding - The Harness Beats the Model","12.06.2026","/blogs-img/harness-vs-model.webp","AI model connected to a codebase through a harness bridge",[739,728],"ai",{"path":741,"title":742,"description":743,"meta":744},"/blogs/oh-my-pi","Oh My Pi — The Open-Source Coding Agent I Actually Use Every Day","Oh My Pi is a fork of Mario Zechner's Pi coding agent with ~1,300 commits of incremental improvements. Here's what makes it different, why harness quality shapes agent reliability more than model choice, and why I run it instead of Claude Code.",{"seoTitle":745,"date":735,"image":746,"imageWidth":663,"imageHeight":664,"alt":747,"tags":748,"author":669,"published":481,"featured":670},"Oh My Pi - My Daily Open-Source Coding Agent","/blogs-img/oh-my-pi.webp","Oh My Pi open-source coding agent harness with flowing code streams",[739,728],{"path":750,"title":751,"description":752,"meta":753},"/blogs/1password-claude-agentic-security","1Password for Claude - AI Agents That Log In Without Ever Seeing Your Password","1Password and Anthropic shipped a zero-exposure integration that lets Claude log into websites and finish real tasks without the model ever touching a credential. Here's how it works, what it's good for, and where the limits are.",{"seoTitle":754,"date":755,"image":756,"imageWidth":663,"imageHeight":664,"alt":757,"tags":758,"author":669,"published":481,"featured":670},"1Password for Claude - Logins Without Secrets","20.07.2026","/blogs-img/1password-claude.webp","1Password and Anthropic zero-exposure credential access for Claude AI agents",[727,739],{"path":760,"title":761,"description":762,"meta":763},"/blogs/nuxt-4-5-road-to-nuxt-5","Nuxt 4.5 - Vite 8, Rspack 2, SSR Streaming, and the Road to Nuxt 5","Nuxt 4.5 is the biggest release in a while - Vite 8, an Rsbuild-powered Rspack 2 builder, experimental SSR streaming, stable error codes, and a pile of groundwork for Nuxt 5. Here's what actually matters, what to test before upgrading, and why the Nuxt 3 clock is about to run out.",{"seoTitle":764,"date":765,"image":766,"imageWidth":663,"imageHeight":664,"alt":767,"tags":768,"author":669,"published":481,"featured":670},"Nuxt 4.5 - Vite 8 and the Road to Nuxt 5","18.07.2026","/blogs-img/nuxt-4-5.webp","Nuxt 4.5 release - Vite 8, Rspack 2, SSR streaming and the road to Nuxt 5",[696,728],{"path":770,"title":771,"description":772,"meta":773},"/blogs/netlify-cloudflare-cache-purge","Purging Cloudflare's Cache Automatically on Every Netlify Deploy","This site sits on Netlify behind Cloudflare, and after every deploy Cloudflare kept serving stale HTML. Here's why the Netlify-CDN-Cache-Control header was a dead end for static files, and the 26-line build plugin that purges Cloudflare's edge cache the moment a deploy goes live — including the CJS/ESM gotcha that broke the first build.",{"seoTitle":774,"date":775,"image":776,"imageWidth":663,"imageHeight":664,"alt":777,"tags":778,"author":669,"published":481,"featured":670},"Auto-Purge Cloudflare Cache on Netlify Deploys","22.07.2026","/blogs-img/netlify-cloudflare-purge.webp","Netlify deploy triggering an automatic Cloudflare edge cache purge",[667,728],{"path":631,"title":780,"description":781,"meta":782},"Debugging LCP on a Real Site - A Case Study on marcofaul.de","A first-person walkthrough of fixing LCP on this very site - a JS reveal animation gating first paint, a font preload that held rendering hostage, a 5.8s image CDN cold start, and the measurement noise that almost sent me chasing ghosts.",{"seoTitle":783,"date":775,"image":784,"imageWidth":663,"imageHeight":664,"alt":785,"tags":786,"author":669,"published":481,"featured":670},"Debugging LCP - A Real-World Case Study","/blogs-img/lcp-debugging.webp","Debugging Largest Contentful Paint - a real-world case study on marcofaul.de",[667,696],{"path":788,"title":789,"description":790,"meta":791},"/blogs/clean-code-summary-robert-martin","Summary of Clean Code by Robert C. Martin - Essential Guidelines for Better Software","Code is clean if it can be understood easily by everyone on the team. A comprehensive summary of Robert C. Martin's Clean Code principles and best practices.",{"seoTitle":792,"date":793,"image":794,"imageWidth":663,"imageHeight":664,"alt":789,"tags":795,"published":481,"featured":670},"Clean Code by Robert C. Martin - Summary","25.10.2025","/blogs-img/clean-code.webp",[796],"best-practices",{"path":798,"title":799,"description":800,"meta":801},"/blogs/pg-boss-10-to-12-upgrade","Upgrading pg-boss 10 → 12 When There Is No Migration Path","pg-boss 12 cannot migrate a v10 schema - v11 moved job storage to partitioned tables and the migration chain starts after that cliff. Here's how I upgraded a production job queue anyway - drop the schema, rebuild queue state from my own tables, and the job-ownership guard the rollout taught me to add.",{"seoTitle":802,"date":775,"image":803,"imageWidth":663,"imageHeight":664,"alt":804,"tags":805,"author":669,"published":481,"featured":670},"pg-boss 10 to 12 Upgrade Without a Migration Path","/blogs-img/pg-boss-upgrade.webp","Postgres-backed job queue being rebuilt during a pg-boss major version upgrade",[796,728],{"path":807,"title":808,"description":809,"meta":810},"/blogs/building-an-seo-crawler","I Built My Own SEO Crawler - Architecture Notes from seo-pulse","Instead of paying for Screaming Frog or Ahrefs, I built my own SEO audit tool - a Bun monorepo with a Nuxt 4 UI, a pg-boss worker that crawls and scores sites, and an MCP server so AI agents can trigger crawls and read findings. Here's the real architecture, and the parts that hurt - deploys killing workers mid-crawl, queue schema upgrades, and Docker builds dying without an error.",{"seoTitle":811,"date":775,"image":812,"imageWidth":663,"imageHeight":664,"alt":813,"tags":814,"author":669,"published":481,"featured":670},"Building an SEO Crawler - Architecture Notes","/blogs-img/seo-pulse-crawler.webp","Architecture diagram of a self-hosted SEO crawler with web app, Postgres queue, and worker",[739,728],{"path":816,"title":817,"description":818,"meta":819},"/blogs/claude-code-freelance-workflows","Claude Code in Real Client Work — Workflows, MCP, and Where It Breaks","A year of running Claude Code on actual freelance and agency projects — the workflows that hold up, why MCP is the real game changer for client work, the failure modes nobody puts in demos, and what I promise clients about AI-assisted development.",{"seoTitle":820,"date":775,"image":821,"imageWidth":663,"imageHeight":664,"alt":822,"tags":823,"author":669,"published":481,"featured":670},"Claude Code in Freelance Work - Workflows & Limits","/blogs-img/claude-code-workflows.webp","AI coding agent connected to real project tooling in a client development workflow",[739,728],{"path":825,"title":826,"description":827,"meta":828},"/blogs/shopware-mcp-ai-agents","Shopware 6 Meets AI Agents - What an MCP Server for Your Shop Could Do","MCP gives AI agents a standard way to talk to real systems. Here's what an MCP server over Shopware's Admin API could look like - the tool surface, the architecture, and the honest risks of letting an agent near a live shop.",{"seoTitle":829,"date":775,"image":830,"imageWidth":663,"imageHeight":664,"alt":831,"tags":832,"author":669,"published":481,"featured":481},"Shopware 6 + AI Agents - An MCP Server for Your Shop","/blogs-img/shopware-mcp.webp","AI agent connected to a Shopware 6 shop through an MCP server",[668,739],{"path":834,"title":835,"description":836,"meta":837},"/blogs/jtl-to-shopify-migration","Migrating a JTL-Shop to Shopify: What to Import and What to Skip","There is no one-click connector from JTL-Shop to Shopify. Here is how I planned a real migration - what I imported, what I deliberately did not, how scripts verify the result, how to stop notification mails during an order import, and the launch checklist.",{"seoTitle":838,"date":839,"image":840,"imageWidth":663,"imageHeight":664,"alt":841,"tags":842,"author":669,"published":481,"featured":670},"JTL-Shop to Shopify Migration: Plan and Verify","06.10.2026","/blogs-img/jtl-shopify-migration.webp","Legacy shop with an encrypted database feeding a verified import pipeline into a Shopify storefront",[739,728],{"path":844,"title":845,"description":846,"meta":847},"/blogs/shopware-configurator-share-links","Shareable Product Configurator in Shopware 6 — State in the URL","How I built a product configurator for a Shopware 6 storefront where the whole state lives in a ?cfg= URL parameter — what to serialize, how the PDF export works, what breaks, and the trade-offs of letting users edit a shared configuration.",{"seoTitle":848,"date":849,"image":850,"imageWidth":663,"imageHeight":664,"alt":851,"tags":852,"author":669,"published":481,"featured":670},"Shopware 6 Configurator: Share Links & PDF Export","02.10.2026","/blogs-img/shopware-configurator.webp","Product configurator card whose state is encoded into a share link that fans out to a phone, a PDF and an email, with an orange loop marking the edit-a-shared-state problem",[668,696],{"path":854,"title":855,"description":856,"meta":857},"/blogs/shopify-personalized-products-and-packaging-fees","Personalized Products and Packaging Fees in Shopify","How I modeled printed cups with tiered prices and a logo upload in Shopify, and the options I weighed for passing a per-item packaging licence fee through to customers — with the pitfalls I hit.",{"seoTitle":858,"date":859,"image":860,"imageWidth":663,"imageHeight":664,"alt":861,"tags":862,"author":669,"published":481,"featured":670},"Shopify Personalized Products & Packaging Fees","04.10.2026","/blogs-img/shopify-personalization.webp","Product configurator with size and quantity tiles and a logo upload, next to a cart that separates a regulatory packaging fee line",[796,728],{"path":864,"title":865,"description":866,"meta":867},"/blogs/proving-where-data-stops-integration-debugging","Proving Where Data Stops — How I Debug Multi-System Integrations","A shop field that never updates, a CDN that can't find its images, a sync that \"randomly\" skips entries. A method for multi-system integrations — instrument every hop, read the boundary evidence, hand over proof instead of opinions — with five real cases from the last weeks.",{"seoTitle":868,"date":869,"image":870,"imageWidth":663,"imageHeight":664,"alt":871,"tags":872,"author":669,"published":481,"featured":670},"Integration Debugging - Prove Where Data Stops","05.10.2026","/blogs-img/integration-debugging.webp","Data pipeline across four connected systems with a check at every hop and one orange marker where the data flow breaks",[796,728],{"path":874,"title":875,"description":876,"meta":877},"/blogs/scheduled-ai-agents-lessons","Scheduled AI Agents — What Weeks of Unattended Runs Teach You","Notes from running scheduled, unattended AI agents for a few weeks — a daily upstream-sync job, a research agent that publishes a page, and review-bot tuning. Guards, state files, failing publish steps, and where it breaks.",{"seoTitle":878,"date":839,"image":879,"imageWidth":663,"imageHeight":664,"alt":880,"tags":881,"author":669,"published":481,"featured":670},"Scheduled AI Agents: Lessons From Unattended Runs","/blogs-img/scheduled-agents.webp","Scheduled agent runs flowing through a guard into a published page, with one failing publish step highlighted",[739,728],{"path":883,"title":884,"description":885,"meta":886},"/blogs/bfsg-accessibility-online-shops","BFSG for Online Shops — What an Accessibility Audit Actually Finds","The BFSG has applied to B2C online shops since 28 June 2025. What an accessibility audit on a real headless Shopware storefront turned up, which fixes a developer can ship right away, which ones need design sign-off, and a checklist for your own shop.",{"seoTitle":887,"date":888,"image":889,"imageWidth":663,"imageHeight":664,"alt":890,"tags":891,"author":669,"published":481,"featured":670},"BFSG for Online Shops: Real Audit Findings","14.10.2026","/blogs-img/bfsg-accessibility.webp","Online shop wireframe with keyboard focus moving through header buttons, navigation and a product card, each checked against an accessibility list",[892,696],"accessibility",{"path":894,"title":895,"description":896,"meta":897},"/blogs/shopware-decoration-best-practices","Shopware Decoration Best Practices: Override One Method, Keep Others Untouched","Learn the golden rule of Shopware decorations - how to efficiently override only what you need while letting PHP inheritance handle the rest automatically.",{"seoTitle":898,"date":899,"image":900,"imageWidth":663,"imageHeight":664,"alt":895,"tags":901,"author":669,"published":481,"featured":481},"Shopware 6 Decoration Best Practices","26.10.2025","/blogs-img/shopware-decoration.webp",[668,796],{"path":672,"title":5,"description":657,"meta":903},{"seoTitle":660,"date":661,"image":662,"imageWidth":663,"imageHeight":664,"alt":665,"tags":904,"author":669,"published":481,"featured":670},[667,668],{"path":906,"title":907,"description":908,"meta":909},"/blogs/ai-agent-readiness-website","Making Your Website Readable for AI Agents — What Actually Matters","llms.txt, agents.md, ai-catalog.json, AI-bot rules in robots.txt. I shipped all of it on marcofaul.de, then audited it and found four of my own files broken or missing. What the 2026 data says about these files, what really decides whether AI tools can read your site, and a checklist to verify it.",{"seoTitle":910,"date":911,"image":912,"imageWidth":663,"imageHeight":664,"alt":913,"tags":914,"author":669,"published":481,"featured":670},"AI Agent Readiness: llms.txt, AGENTS.md and What Matters","31.10.2026","/blogs-img/agent-readiness.webp","A website feeding server-rendered HTML, structured data and small machine-readable files to AI crawlers, with one broken file highlighted",[739,915],"seo",{"path":917,"title":918,"description":919,"meta":920},"/blogs/headless-gamechanger","Why Headless Shopware 6 with Nuxt is a Game-Changer for Your Online Store","Going headless with Shopware 6 and Nuxt isn't just a tech trend—it's a competitive advantage. Discover why separating your frontend from backend delivers blazing-fast performance, incredible flexibility, and happier customers.",{"seoTitle":921,"date":899,"image":922,"imageWidth":663,"imageHeight":664,"alt":923,"tags":924,"published":481,"featured":481},"Headless Shopware 6 with Nuxt - Why It Wins","/blogs-img/shopware-nuxt-headless.webp","Headless Shopware 6 with Nuxt - The future of e-commerce",[668,696],{"path":926,"title":927,"description":928,"meta":929},"/blogs/quality-tools-that-matter","Code Quality Tools That Actually Matter - Your PR Review Checklist","Stop shipping bugs and messy code. These essential code quality tools catch issues before they hit production, making your team faster and your code cleaner.",{"seoTitle":930,"date":899,"image":931,"imageWidth":663,"imageHeight":664,"alt":932,"tags":933,"published":481},"Code Quality Tools That Actually Matter","/blogs-img/code-quality-tools.webp","Essential code quality tools for modern development",[796,728],{"path":935,"title":936,"description":937,"meta":938},"/blogs/shopware-67-migration-guide","Shopware 6.6 to 6.7 Migration Guide - Breaking Changes and a Safe Upgrade Path","Upgrading Shopware 6.6 to 6.7? Here are the real breaking changes - Vite, Symfony 7.4, Pinia, delayed cache - and a tested upgrade path that won't break production.",{"seoTitle":939,"date":723,"image":940,"imageWidth":663,"imageHeight":664,"alt":941,"tags":942,"author":669,"published":481,"featured":481},"Shopware 6.6 to 6.7 Migration Guide","/blogs-img/shopware-67-migration.webp","Shopware 6.6 to 6.7 migration guide - breaking changes and upgrade path",[668,728],{"path":944,"title":945,"description":946,"meta":947},"/blogs/nuxt-4-migration-guide","Migrating to Nuxt 4 - The New app/ Directory, Smarter Data Fetching, and a Painless Upgrade","Nuxt 4 is here. Learn the new app/ directory structure, improved useFetch/useAsyncData, the path-alias gotcha, and how to upgrade safely with codemods.",{"seoTitle":948,"date":949,"image":950,"imageWidth":663,"imageHeight":664,"alt":951,"tags":952,"author":669,"published":481,"featured":481},"Nuxt 4 Migration Guide","10.06.2026","/blogs-img/nuxt-4-migration.webp","Migrating to Nuxt 4 - new app directory and data fetching",[696,728],{"path":626,"title":954,"description":955,"meta":956},"Core Web Vitals 2026 - How to Master INP (Interaction to Next Paint)","INP is the Core Web Vital most sites fail. Learn what INP measures, the 200ms threshold, and concrete JavaScript techniques to make your store feel instant.",{"seoTitle":957,"date":958,"image":959,"imageWidth":663,"imageHeight":664,"alt":960,"tags":961,"author":669,"published":481,"featured":670},"Core Web Vitals 2026 - Mastering INP","04.06.2026","/blogs-img/core-web-vitals-inp.webp","Master INP Interaction to Next Paint Core Web Vitals 2026",[667,696],{"path":963,"title":964,"description":965,"meta":966},"/blogs/ai-product-search-shopware","AI-Powered Product Search in Shopware - Semantic and Vector Search That Converts","Keyword search misses what shoppers mean. Here's how to add AI semantic/vector search to Shopware 6 with embeddings - the architecture, the tradeoffs, and a practical build.",{"seoTitle":967,"date":968,"image":969,"imageWidth":663,"imageHeight":664,"alt":970,"tags":971,"author":669,"published":481,"featured":481},"AI Product Search in Shopware","09.06.2026","/blogs-img/ai-product-search.webp","AI-powered semantic and vector product search in Shopware 6",[668,739],1793447959684]