Use Promise.all whenever possible

[conico974]

This should decrease TTFB for page that needs to be generated

Close RND-7316

[linear]

RND-7316 GBO V2 use `Promise.all`whenever we can

[changeset-bot]

⚠️ No Changeset found

Latest commit: a875bb2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Summary of the deployments:

Version 1

Version	URL	Status
Latest commit	https://100b5b52.gitbook-open.pages.dev	✅
PR	https://pr3319.gitbook-open.pages.dev	✅

Version 2

Version	URL	Status
Vercel	https://gitbook-v2-ijcmkm3ga-gitbook.vercel.app	✅
Cloudflare	https://0468dc42-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	v1	2v	2c
GitBook	https://100b5b52.gitbook-open.pages.dev/gitbook.com/docs	https://gitbook-v2-ijcmkm3ga-gitbook.vercel.app/url/gitbook.com/docs	https://0468dc42-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs
E2E	https://100b5b52.gitbook-open.pages.dev/gitbook.gitbook.io/test-gitbook-open	https://gitbook-v2-ijcmkm3ga-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open	https://0468dc42-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.gitbook.io/test-gitbook-open

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
customers-v1 (Inspect)	✅ No changes detected	-	Jun 13, 2025, 5:19 PM
customers-v2 (Inspect)	✅ No changes detected	-	Jun 13, 2025, 5:20 PM
default (Inspect)	✅ No changes detected	-	Jun 13, 2025, 5:21 PM
v2-cloudflare (Inspect)	👍 Changes approved	7 changed	Jun 13, 2025, 5:24 PM
v2-vercel (Inspect)	✅ No changes detected	-	Jun 13, 2025, 5:23 PM

[SamyPesse]

It makes sense, but I don't think it'll have much impact, I think we should look more at how Next.js process components rendered as siblings that are suspending: is it serial or parallel?

[conico974]

It makes sense, but I don't think it'll have much impact, I think we should look more at how Next.js process components rendered as siblings that are suspending: is it serial or parallel?

Totally agree, it's just the first step. But in some cases it could still save a couple hundreds of milliseconds, that's an easy win.

One suspended component will not render it's children before actually reaching the JSX component. For some nested deep in multiple <Suspense />, we have to wait a lot of time before starting to fetch even though we could fetch it right away.

I'm working on a PR that will prefetch things ASAP in the component tree (basically in the layout/page), and we then use these prefetched data instead of fetching them directly in the component.
The ultimate step would probably be to try to get all the necessary data in one single API call (or as few as possible)