What we’re wondering: Are we approaching SSR + edge caching in a Nuxt-idiomatic way?
Would you structure content fetching differently? (Currently planning to centralize route/content resolution into a single server API and preload in serverPrefetch or top-level asyncData)
Any tips for performance wins in similar Nuxt 3 apps?
side note:
we have seen that our search crawlers often see empty <main><!-- --></main> pages during hydration, hurting our SEO, however we can not seem to reproduce this is in any living way, and even our crawls not always see this problem on the same url.
Illustreret Videnskab er et internationalt populærvidenskabeligt magasin, som giver læseren indsigt i verdens førende forskning i alle grene af videnskaben.
"Find de nyeste biltests, anmeldelser og guides til biler fra Bilmagasinet. Hold dig opdateret på alt om biler, nyheder, elbiler, SUV'er og meget mere."