Next.js Discord

Discord Forum

Default NextJS app - poor performance

Unanswered
Great black wasp posted this in #help-forum
Open in Discord
Great black waspOP
Default NextJS app - poor performance

I created blank default NextJS app with npx create-next-app (node 18, next 14)... Tailwind included, app router ..
Performance is 75% on mobile ..
Also, I got "WebSocket connection to 'wss://my.url/_next/webpack-hmr' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED"

So just a default app .... No fetching or importing anything.... No tinkering whatsoever...

Any thoughts ?

17 Replies

American Chinchilla
@Great black wasp you said you created a new next app but that error comes out when you start the server?
* when you run npm run dev
Great black waspOP
No, it is displayed in pagespeed insights (google) under "best practices" ... Of course, npm run build and deployed to server ...
Windows server, by the way, with node 18 supported....
It works fine, just this poor performance is a bit annoying ...
I also deployed vite default app to the same server.... Got all 100%, no errors....
It seems to me that with tailwind performance of next js goes down....
When I removed tailwind, I got 100%.... But it is not fun without tailwind...
@American Chinchilla <@349618426383302668> you said you created a new next app but that error comes out when you start the server?
Great black waspOP
No, it is displayed in pagespeed insights (google) under "best practices" ... Of course, npm run build and deployed to server ...
@American Chinchilla <@349618426383302668> you said you created a new next app but that error comes out when you start the server?
Great black waspOP
Windows server, by the way, with node 18 supported....
It seems to me that with tailwind performance of next js goes down....
@Great black wasp When I removed tailwind, I got 100%.... But it is not fun without tailwind...
Sloth bear
Tailwind shouldn't impact performance should be negligible should be barely noticible sef
@Great black wasp When I removed tailwind, I got 100%.... But it is not fun without tailwind...
Lukas
Tailwind doesn't/shouldn't even run here. Make sure tailwind is a dev dependency and lmk if that fixes it
Lukas
let me know
Great black waspOP
Ok, problem solved ... Did not install next globally so vs code produced dev version regardless of npm run build....
Now, with proper production build, blazing fast 🙂