Images are often the largest opportunity
Use modern formats, correct dimensions and compression appropriate to the image. A thumbnail does not need the same file dimensions as a full-width hero.
Control JavaScript and third-party scripts
Chat widgets, analytics, advertising, maps and tag managers can add substantial work to the browser. Audit what is actually used and load non-critical features thoughtfully.
Prevent layout shifts
Reserve space for images and embeds, avoid inserting content above what the user is reading and use fonts carefully. Visual stability is part of perceived quality.
Cache stable assets
CSS, JavaScript, fonts and images that change infrequently can generally use effective browser caching. Server configuration and CDN choices depend on the hosting environment.
Measure real templates
Testing only the homepage can hide problems on product, service or blog templates. Check the pages that receive traffic and contain the heaviest components.
Do not sacrifice clarity for a score
Performance tools are diagnostic aids. Removing a useful image, map or feature solely to gain a point can make the site worse. Optimize important functionality instead of chasing a perfect number.
Set a performance budget
Decide reasonable limits for image weight, JavaScript and third-party services on important templates. A budget makes trade-offs visible. Adding another tracking script then becomes a conscious choice rather than an invisible accumulation of page weight.
Optimize the largest visual first
The hero or primary content image is often a major loading factor. Size it for its rendered dimensions, choose an efficient format and avoid delaying an image that needs to appear immediately. Lower-page imagery can generally load later.
Performance is also a content-management issue
Editors can undo a fast build by uploading multi-megabyte photographs or embedding several third-party widgets. Give content managers image guidance and periodically review the heaviest pages after launch.