v1 - Performance 📈

[alisonjoseph]

Hi 👋 Thanks for joining our v1 "Test Fest"!

Are you noticing any performance issues? Please log them here. We really appreciate your help ❤️

📈 Performance issue
**Page:** URL
**Browser:** 
**Issue:** 
**Suggestion:** 

[mattrosno]

@jdharvey-ibm those docs are confusing. Per other examples, it appears you can use fallback: true with ISR. See: https://www.smashingmagazine.com/2021/04/incremental-static-regeneration-nextjs/#generating-paths

https://www.smashingmagazine.com/2021/04/incremental-static-regeneration-nextjs/#isr-fallback-options

[jharvey10]

Oh interesting! Yeah the nextjs docs definitely don't make that clear. We could definitely try out fallback: true for pages for which we don't care about SEO.

[mattrosno]

@jdharvey-ibm per https://nextjs.org/docs/api-reference/data-fetching/get-static-paths#fallback-true

Web crawlers, such as Google, won't be served a fallback and instead the path will behave as in fallback: 'blocking'.

I think Next.js is smart enough to know if the request is from a crawler, to not show the fallback or any loader rendered when no fallback is available, and instead wait on the SSR (fallback: 'blocking') page.

[jharvey10]

Well that's pretty cool, haha. Takes a lot off of our plate then!

[mattrosno]

Tracked here: #1313