Measure, analyze, optimize.

You should be able to deploy your app locally, access it via a logging proxy, (say mitmproxy), and observe the logged HTTP traffic to identify what's going on. Pay attention to HTTP cache mechanisms.

Rinse and repeat until you are less than baseline (and if you don't/can't, is SSR really a good tradeoff for your use-case?).

Once you have verified your app behaves itself it's time to repeat on the cloud platform and address the public setup.

There are so few details here, it’s difficult for me to comprehend how you could expect anyone be able to provide any helpful advice. What troubleshooting and analysis have you done?

I checked the Vercel logs and found that many crawlers are scraping my pages, which leads to frequent database queries. Since Neon doesn't have caching, the data transfer is being consumed very quickly, and I'm currently using Prisma. Now I'm planning to migrate to Supabase and use supabase-js.

(Prisma team member here)

Try Prisma Postgres: prisma.io/postgres

No data transfer costs at all, and built-in caching across 300+ global PoPs (still valuable to decrease latency): https://www.prisma.io/docs/postgres/database/caching