Can you run next build and then next start and see how it performs in prod mode?

did that already, same in prod. 😦

Have you migrated to app dir or using pages with v14

still pages

can you explain 'lags'

Yes sorry, I have an animated cursor too a simple circle that follows the cursor, that plus the particles in the background seem to much for some reason in 14 because the cursor lags but interestingly in 12 not.

do you have deployed version

this is the laggy version 14 X

so weird, have you changed anything after updating to 14

nothing just ran the codemod to keep legacy image component, does it lag on your side as well?

yep i saw lags

weird must be some bundle issue no idea..

can i see your build logs

have you also updated this lib tsparticles

no still the same version I wanted to keep everything the same to then slowly migrate to app

they look fine

are you seeing any red page at build logs

no the page builds with 0 errors and runs

no i mean as color at terminal

like / 32kb (red)

also i could say, particles are okay, just cursor is laggy

Yes, the thing is the cursor is only on the index page laggy all other pages are fine

probably your index page is big, i need to see build log at terminal local build

yes the index is indeed heavy the guy who did the brain loads 100 + images at once which kills everything...

yep, that images are <Image or <img

normal images since this is a special animation library which uses local images called "Lottie"

hmm, if you dont need that animations and thinking those are redundant or heavy, you can remove that things, this affects performance a lot positive

yeah true I need to novince them 😄

personally i am not using any animation, motion, three libs in my projects and they are loading under .5 sec

yeah I know the problem is some people want it

that animation side is different than web dev tbh, you need to compress images, optimize particles, use better libs etc

its loading heavy on your GPU, but web app working on CPU mostly