We need to ___ app size so downloads complete faster.
To reduce app size means to shrink the download or install footprint of a mobile app. It is the standard performance collocation: "reduce app size by removing unused assets". "Lessen down", "cut over", and "shrink off" are not idiomatic. Reduce pairs with size, latency, and footprint, and smaller apps install and update more readily.
2 / 5
Let's ___ the app to find what is consuming CPU on startup.
To profile an app means to measure where it spends time and resources so you can find bottlenecks. It is the precise collocation: "profile the cold-start path". "Scan over", "measure up", and "check off" are not the term. Profile pairs with app, code, and startup, and is the diagnostic step before optimisation.
3 / 5
We can ___ images so they are not fetched repeatedly.
To cache assets means to store them locally so they need not be downloaded again, improving speed. It is the standard collocation: "cache the thumbnails on disk". "Store over", "keep off", and "hold up" are not idiomatic. Cache pairs with assets, images, and responses, and is a primary lever for perceived performance.
4 / 5
We should ___ the heavy list so it loads only when scrolled to.
To lazy-load means to defer loading content until it is actually needed, such as when it scrolls into view. It is the established collocation: "lazy-load images below the fold". "Slow-load", "late-fetch over", and "delay-pull" are not standard. Lazy-load pairs with images, components, and modules, reducing initial load time.
5 / 5
A key goal is to ___ so the app feels instant when opened.
To optimise startup means to reduce the time and work needed for the app to become usable after launch. It is the natural collocation: "optimise startup by deferring non-critical work". "Better startup", "speed startup over", and "quick startup" are not idiomatic. Optimise pairs with startup, launch, and cold-start, all central to mobile UX.