Time to first byte very slow

[matteo-naif]

Describe the Bug

I deployed my application on Vercel and the load is very slow. If I analyze with a SEO tool I can see that the first javascript bundle request the document and the time to receive it and then load all the resources is very long.

Link to the code that reproduces this issue

Reproduction Steps

I use a catch all page with the following structure
src/app/(app)/(other)/[[...slug]]/page.tsx

In this page I retreive the document content (collection page) with a query of the local api and then I loop the layout made of blocks inside the lexical editor.

The blocks are rendered searching in an object where the key is the string blockType and the value, the server component.

Can you tell me if there is any precaution to avoid it?

Which area(s) are affected? (Select all that apply)

area: core

Environment Info

Binaries:
Node: 20.12.2
npm: 10.5.0
Yarn: 1.22.22
pnpm: 9.6.0
Relevant Packages:
payload: 3.0.0-beta.118
next: 15.0.0
@payloadcms/db-mongodb: 3.0.0-beta.118
@payloadcms/email-nodemailer: 3.0.0-beta.118
@payloadcms/graphql: 3.0.0-beta.118
@payloadcms/next/utilities: 3.0.0-beta.118
@payloadcms/plugin-cloud-storage: 3.0.0-beta.118
@payloadcms/plugin-form-builder: 3.0.0-beta.118
@payloadcms/plugin-nested-docs: 3.0.0-beta.118
@payloadcms/plugin-seo: 3.0.0-beta.118
@payloadcms/richtext-lexical: 3.0.0-beta.118
@payloadcms/storage-s3: 3.0.0-beta.118
@payloadcms/translations: 3.0.0-beta.118
@payloadcms/ui/shared: 3.0.0-beta.118
react: 19.0.0-rc-65a56d0e-20241020
react-dom: 19.0.0-rc-65a56d0e-20241020
Operating System:
Platform: darwin
Arch: x64
Version: Darwin Kernel Version 21.6.0: Mon Jun 24 00:58:06 PDT 2024; root:xnu-8020.240.18.709.2~1/RELEASE_ARM64_T6000
Available memory (MB): 32768
Available CPU cores: 10

[denolfe]

Hey @matteo-naif , thanks for the issue. This is due to the fact that Vercel using serverless technology and will almost always incur a cold-start. There is not anything we can do on our end here.

[github-actions]

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.