Slow loading times on simple dynamic pages
Unanswered
Harlequin posted this in #help-forum
HarlequinOP
I have a page that renders a list of items, the network requests on the server are around ~30ms but the response time on the client is close to ~500-700ms. I've tried testing with a very simple page, no layout or anything just some simple text and the best I've gotten it down to is ~250ms.
I'm thinking I may need to switch from dynamic pages to static pages with client-side fetching for the dynamic components. This way the pages can be served via cache etc and the requests to the api won't be wrapped by nextjs so should hopefully be as fast as possible.
I'm just not sure on the downsides, I remember this was the approach the vercel dashboard took a few years back, but I'm not sure if it's still recommended.
I'm thinking I may need to switch from dynamic pages to static pages with client-side fetching for the dynamic components. This way the pages can be served via cache etc and the requests to the api won't be wrapped by nextjs so should hopefully be as fast as possible.
I'm just not sure on the downsides, I remember this was the approach the vercel dashboard took a few years back, but I'm not sure if it's still recommended.
3 Replies
West African Crocodile
Okay, I think so.
We can use static pages, just like dashboard pages without user integrations.
We can use static pages, just like dashboard pages without user integrations.
HarlequinOP
Have you seen any downsides at all @West African Crocodile ? My app is also a dashboard so I'm thinking it's a good way to go considering it should be significantly faster than server rendering it and basically middle-manning the API requests.
West African Crocodile
You can use static pages if you don't need user integration and your pages won't change.
but if your pages can change, you can use sever side rendering page.
but if your pages can change, you can use sever side rendering page.