Content pfp
Content
@
0 reply
0 recast
0 reaction

dylan pfp
dylan
@dylsteck.eth
some things that have been making nextjs faster/cheaper for me lately: - prefetch your links with their <Link> - don’t use their <Image>, use <img> + a CDN(I like Cloudinary) - if you use RSCs you need to use suspense and proper data loading patterns(and caching) otherwise your app becomes sooo slow - keeping certain values either strictly static or on the client
3 replies
2 recasts
11 reactions

dylan pfp
dylan
@dylsteck.eth
anything I’m missing? also I feel like a lot of this just comes down to general best practices
3 replies
0 recast
0 reaction

dylan pfp
dylan
@dylsteck.eth
just in time lol, bookmarking this for later https://www.youtube.com/watch?v=mMQCLQTky34
0 reply
0 recast
0 reaction

alex pfp
alex
@alexgrover.eth
you can use the Image component with a third party CDN/optimizer! that way you don’t miss out on the rest of the optimizations the component includes. docs here: https://nextjs.org/docs/pages/api-reference/components/image#loaderfile
1 reply
0 recast
1 reaction