@nuxt/content website is slow (google page speed)

[pseudo spear]

Hi @safe loom. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

Thanks for sharing context. Based on the Nuxt performance docs and related modules, here’s a focused checklist to raise PageSpeed scores and reduce CLS for your Nuxt + Content site on Netlify:

• Measure precisely

  • Use Nuxt DevTools Timeline/Assets/Render Tree/Inspect to spot hydration and render bottlenecks. [Nuxt DevTools]
  • Cross-check with Chrome DevTools (Performance + Lighthouse), PSI, and WebPageTest to see LCP/CLS/INP and regressions per route. [Chrome DevTools; PageSpeed Insights; Web Page Test]

• Optimize images (major LCP/CLS lever)

  • Use Nuxt Image everywhere. For above-the-fold/LCP, eagerly load with explicit width/height (or aspect-ratio) and consider preload + high fetch-priority. Lazy-load all non-critical images. [Images]
  • On Netlify, set image provider to netlify for on-demand transformations and optimal formats. [Netlify provider]
  • If you go fully static via nuxt generate, Nuxt Image can pre-generate optimized files. If SSR is disabled, pre-render IPX URLs via nitro.prerender.routes. [Static Images]

• Prerender critical routes

  • Pre-render your service pages to reduce server work and improve TTFB/LCP on Netlify. Use nuxt generate and/or Nitro prerender routes or routeRules for specific pages. [Prerendering]

• Fonts (reduce CLS)

  • Ensure Nuxt Fonts is active so fonts are self-hosted, proxied/cached, with fallback metrics to minimize layout shift. [Images → Fonts section]

• Common pitfalls to audit

  • Remove/trim heavy plugins; convert simple ones to composables/utilities to avoid hydration delays. [Common problems]
  • Eliminate unused deps/code to keep the bundle lean. [Common problems]
  • Apply Vue perf tips where needed (e.g., v-once, v-memo, shallowRef) to reduce reactivity overhead. [Common problems]
  • Sequence loading (progressive enhancement) so non-essential widgets load later. [Common problems]

• Nuxt Content v3

  • Consider upgrading if you’re on v2: v3 moves to SQL-backed storage with better performance and improved client-side navigation, plus serverless compatibility—useful on Netlify. [Content v3 blog; Frontmatter form changelog]

• Extra learning

  • Review the PRPL pattern, perceived performance, and critical rendering path to guide trade-offs. [Useful resources]

If you share which elements on /oferta/sxo are causing LCP/CLS in PSI (e.g., hero image, heading, font swap, late layout CSS), you can target the exact components with the above steps.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: