You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is based on the suggestions and discussions in #81 and #87.
Currently, all images have loading="lazy" attribute applied via render-image.html hook. This raises warnings in Lighthouse reports and might lead to delayed load and render times for the images present above the fold causing a large LCP score in Web Vitals reports.
To improve performance and perceived experience, it's better ideally to load and render the images above the fold as fast as possible. For this, it's recommended to not add loading="lazy" and to add fetchpriority="high". See https://web.dev/articles/fetch-priority#increase-lcp-priority
However, we don't have a single "above the fold" size as that depends on the user agents and their screen sizes. Instead, the proposal as per discussions is to apply these optimizations to a constant number of images appearing at the top of the content's markup. For now, we can go with the first 3 images.
So, the overall change proposed:
For the first 3 images in the article:
Add fetchpriority="high"
Do not add loading="lazy"
For remainder of images:
Add loading="lazy"
Optionally, we could add a config for the number of images to optimize.
The text was updated successfully, but these errors were encountered:
This is based on the suggestions and discussions in #81 and #87.
Currently, all images have
loading="lazy"
attribute applied viarender-image.html
hook. This raises warnings in Lighthouse reports and might lead to delayed load and render times for the images present above the fold causing a large LCP score in Web Vitals reports.To improve performance and perceived experience, it's better ideally to load and render the images above the fold as fast as possible. For this, it's recommended to not add
loading="lazy"
and to addfetchpriority="high"
. See https://web.dev/articles/fetch-priority#increase-lcp-priorityHowever, we don't have a single "above the fold" size as that depends on the user agents and their screen sizes. Instead, the proposal as per discussions is to apply these optimizations to a constant number of images appearing at the top of the content's markup. For now, we can go with the first 3 images.
So, the overall change proposed:
fetchpriority="high"
loading="lazy"
loading="lazy"
Optionally, we could add a config for the number of images to optimize.
The text was updated successfully, but these errors were encountered: