Practise the standard verbs for optimising images in Next.js.
0 / 5 completed
1 / 5
Fill in: 'We ___ the built-in Image component so Next.js automatically serves a resized, modern-format version of every asset.'
We 'use' a component — the standard, simple collocation for adopting a built-in feature. The other options are less idiomatic here.
2 / 5
Fill in: 'Skipping width and height props can ___ a layout shift as the browser reflows once the image finally loads.'
We say missing dimensions will 'trigger' a layout shift — the standard, established web-performance collocation. The other options aren't the recognised term here.
3 / 5
Fill in: 'We ___ lazy loading on below-the-fold images so the initial page load doesn't fetch everything at once.'
We 'enable' a feature — the standard, simple collocation for turning on a loading optimisation. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a priority flag on the hero image so it preloads instead of competing with lower-priority assets.'
We 'set a flag' — the standard, simple collocation for configuring a per-image option. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ Largest Contentful Paint after an image optimisation change to confirm it actually improved load speed.'
We 'measure' a metric — the standard, simple collocation for evaluating a performance effect. The other options are less idiomatic here.