Knowledgebase

Optimising Front-End Assets Print

  • developersgitdeployment, developers, performance, caching, troubleshooting, guide, howto, solution
  • 0

The part of performance visitors feel most.

THE BASICS

Compress and resize images before they are served Minify CSS and JavaScript Combine files where it helps, testing carefully since this breaks things most often Enable compression and browser caching headers Defer or async scripts that are not needed for initial render

IMAGES

Usually the largest part of a page. Serve appropriately sized images, use modern formats where supported, and lazy load anything below the fold.

FONTS

Each weight is a separate download. Limit to what you actually use, and preload the critical one.

THIRD-PARTY SCRIPTS

Chat widgets, trackers, ad tags and embeds are frequently the slowest part of a page and you control none of their code.

Audit them, remove what does not earn its place, and load the rest asynchronously.

MEASURING

The waterfall view in a performance testing tool shows what loaded, in what order, and how long each took. That identifies the problem far better than an overall score.

TEST ON MOBILE

On a mobile connection, where most visitors are.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot