Assets for Frontend Performances
Asset optimisation reduces the cost of the images, fonts and third-party scripts a page loads. Images use modern formats such as AVIF and WebP with responsive srcset sizes and lazy loading, fonts use subsetting and font-display, and third-party tags are audited, deferred or removed.
Stage: Loading · Part of the Frontend Performance roadmap · Last reviewed 19 November 2026
What to learn in Assets
- Serve responsive images with srcset, sizes and the picture element
- Choose between AVIF, WebP, JPEG and SVG for a given image
- Prevent invisible text with font-display and subset the font files
- Measure the main-thread cost of a third-party tag
- Load non-critical scripts with defer, async or after interaction
Assets interview questions
When should you not lazy-load an image?
Do not lazy-load the image that is likely the Largest Contentful Paint element, or anything visible in the first viewport. Lazy loading delays it until layout and scripts decide it is near the viewport, which makes LCP worse.
How do third-party scripts hurt performance?
They add network requests you do not control and run JavaScript on your main thread, which delays rendering and input handling. Some also cause layout shifts or block other resources. Audit each one and load it late or remove it.
Where Assets fits in the Frontend Performance roadmap
Assets belongs to the Loading stage (intermediate level), which takes about 13 hours. Get bytes to the user.
Other units in this stage
Back to the full Frontend Performance roadmap