5 collocation exercises on frontend performance optimisation.
0 / 5 completed
1 / 5
To benchmark UX, you ___ Core Web Vitals.
You measure Core Web Vitals — the user-centric metrics (LCP, CLS, INP) Google uses to assess page experience. The verb measure collocates with metrics, performance and vitals. Gauge up, meter off and clock out are not idiomatic. You typically measure these in the field with real-user monitoring and in the lab with tools like Lighthouse, then optimise the worst-scoring metric first.
2 / 5
To avoid blocking render, you ___ a script.
You defer a script — using the defer attribute so it loads in parallel but executes only after the HTML is parsed. Defer is the precise collocation (alongside async). Delay off, hold up and lag out are wrong. Deferring non-critical JavaScript keeps the main thread free during initial render, improving metrics like LCP and time-to-interactive without changing what the script ultimately does.
3 / 5
To fetch a critical asset early, you ___ it.
You preload a resource — using a preload link hint to tell the browser to fetch a critical asset (a font, hero image or key script) with high priority. Preload is the fixed term. Pre-grab off, fore-load up and early-pull out are invented. Preloading the right resources reduces render-blocking delays, but over-preloading wastes bandwidth and can hurt performance, so use it selectively.
4 / 5
To ship less JS upfront, you ___ the app.
You code-split an application — breaking the bundle into smaller chunks loaded on demand, often per route. Code-split (or code splitting) is the standard term in bundlers like webpack and Vite. Chop down, break off and divide out are not idiomatic. Code-splitting means users download only the JavaScript they need for the current view, speeding up initial load on large applications considerably.
5 / 5
To reduce download size, you ___ the bundle.
You optimise the bundle — reducing its size through minification, tree-shaking and dependency pruning. The verb optimise (US: optimize) collocates with bundle, build and performance. Slim off, trim up and shrink out are not standard collocations. Optimising the bundle directly improves load time; analysing it with a bundle visualiser helps you spot oversized dependencies to replace or lazy-load.