\n\n\n\n```\n\nWhile they're marked `async` (good β not render-blocking), 10+ separate HTTP requests add overhead even over HTTP/2. Turbopack's chunking strategy here appears overly granular for a single-page landing site.\n\n**Fix:** Review Next.js `experimental.optimizePackageImports` and ensure bundle analysis (`next build --profile`) is used to identify chunk bloat. Consider if all third-party libraries (Stripe, GTM, Facebook Pixel) are truly needed on initial load.\n\n---\n\n### 3. Facebook Pixel + Google Ads Loading\n\n```html\n\n\n\n```\n\nGTM and Meta Pixel are third-party scripts that can significantly delay Time to Interactive (TTI) and Total Blocking Time (TBT). These are loaded eagerly and could be deferred until after the main thread is free.\n\n**Fix:** Load these via GTM's own tag firing rules with `Page View` triggers set to \"DOM Ready\" or \"Window Loaded\" rather than immediately. Or use Next.js `
πͺ We use cookies and tracking to improve your experience and for analytics.
See our Cookie Policy.