73b552a9a5
## History When we added `priority` prop to `next/image`, there was no `fetchPriority` so we instead used this to preload the image in the head. Then when browsers added support `fetchPriority`, we automatically added `fetchPriority=high` when `priority={true}` to signal to the browser that this was a high priority image. This priority is added to the img and the preload. However, we saw cases where images are blocking critical css. Per @gnoff: > React currently prioritizes font preloads then high priority images, then css in the initial page load Due to these changes in React (aka Float), we should no longer set `fetchPriority=high`, although the user can still manually add that prop if needed. |
||
---|---|---|
.. | ||
components | ||
pages | ||
public | ||
test | ||
style.module.css |