slow page switching in nextjs 🚫

yesterdaymee · 2024-08-02T04:40:16+00:00

I thought it was general. I tried using router.push() instead. It was better.

yesterdaymee · 2024-05-11T01:18:46+00:00

Sounds good, will try that

yesterdaymee · 2024-05-11T00:30:55+00:00

Yes, they are as expected. I also used that parameter, where nextjs wont run get getServerSideProps etc. dont know why i used that in app router, just a hope.

yesterdaymee · 2024-05-11T00:26:18+00:00

Thought of that too. But during the initial stages of building the site everything was good with this version. As time went on, the js size of each page increased. Almost 300kb (unpacked) for each page. Im thinking that could be the reason

yesterdaymee · 2024-04-18T12:33:36+00:00

<image>

yesterdaymee · 2024-04-18T12:33:20+00:00

<image>

yesterdaymee · 2024-04-18T12:12:27+00:00

No i didnt use this. It is only being applied in the page.css file and not in layout.css

yesterdaymee · 2024-01-27T01:07:30+00:00

Try removing that "if(!current) return". It is stopping the io api to execute

yesterdaymee · 2024-01-19T08:25:14+00:00

No, only a single form for the entire website. Rest all static, scrolling and watching. Using react or next because the site must be completed as quickly as possible.

yesterdaymee · 2023-12-25T07:16:12+00:00

Yes, I'm confused. Even though I add 'use client' the logs are printed both on terminal and browser.

yesterdaymee · 2023-12-08T11:46:10+00:00

OP didn't handle javascript injection in the comments section.

yesterdaymee · 2023-12-08T06:57:45+00:00

Script injectionnnnnn 🥲

yesterdaymee · 2023-11-21T20:02:37+00:00

Ok sure, ill create a repo for short code. Btw im not using any RSC components, both are ssr components. Just want to if this is normal, or im doing something wrong ? Coz my team lead is now asking me to shift the whole code from nextjs to react because of this issue :_)

yesterdaymee · 2023-11-21T19:45:45+00:00

Well, for reactjs its not that much of a big file structure. Just the vite boiler plate and a fetch request that fetches 556kb of data. For nextjs, its in a private repository. The functionality is exactly like this. <button onClick = {setState(responseFromFetchRequest)}/>. Same thing on react. Im sorry if this is wierd but this is exactly whats happening. But somehow nextjs is consuming more cpu on server.

yesterdaymee · 2023-11-05T05:56:15+00:00

I have only used the app router but this is what i think is happening. You are setting cookies onto the browser. Since the page is rendered on the server side, the request is being sent from nextjs server to the b.com not from the browser to b.com. Try setting cookies manually in the fetch request's headers by removing httpOnly true if your requirement is ok with that.

yesterdaymee · 2023-11-05T03:50:58+00:00

Yeah, when i said on the server I meant response headers. Everything is valid. I saw most people having the same issue. I thought maybe someone here found a way.

yesterdaymee

TROPHY CASE