Improving page performance | Next.js

preview_player
Показать описание
Hi all,

Рекомендации по теме
Комментарии
Автор

Tldr
- use next/dynamic - to dynamically import components
- use next/image - to optimize image sizes

davidsiewert
Автор

Dynamic import is great but I don't think lazy loading text content is reasonable. The main reason we use Next over React is improving SEO and this way we're generating the text content on the client again.

nawti
Автор

inorder to dynamically load something, it has to be conditionally rendered. thats why you didn't see any changes after implementing dynamic loading.

Getentertainedp
Автор

Hey, awesome video, it helps me to improve my score :). But my main problem is with Total Block Time, its at 350ms right now, my nextjs app only uses tailwind and headlessui, i dont know why it's so big. I hope you can help me, thanks in advance

samuelpalacios
Автор

What about we use video rather than image

vavinashece
Автор

How will this impact seo? For example, the content is not rendered from start, this means for what I understand, that the Google bot will not see it either.. Right?

thenoobdev
Автор

Brother image rendering has an issue bro...here you are using images from other website using a link..but in my case i have the images in public folder and iam using that in my IMAGE src...iam also using tailwind as like you do...but the image is only rendering in dvelopment if i build it for production i dont see any images...i only see the ALT tag value of the image...why is this happening bro....i used next image component..wrapped it with a div and addedd tailwind classes on that div and did everything fine..but why is my image not getting rendered only on production build

jawidhmuhammadh
Автор

How can we change the next image cache header

rabinthapa