Website speed: what actually moves the numbers
Speed work has a clear order of return. Images and fonts first, then how much code runs before the page is usable, then everything else. Most sites can be substantially faster without a rebuild.
By Saleem Ahmed · · 6 min read
Last updated:

Fix the heavy assets
- Serve images in modern formats at the size they are displayed
- Lazy-load anything below the first screen
- Reserve space for images and embeds so the layout does not jump
- Limit web fonts to the weights you actually use and let text render immediately
Reduce what runs before first use
Third-party scripts — chat, analytics, tag managers, embeds — are the most common cause of a slow-feeling site. Load them after the page is interactive, and remove the ones nobody reads reports from.
On the build side, render pages server-side where you can, split large bundles, and keep the interactive code on a page proportional to what that page does.
Measure on real visits
Lab scores are useful for diagnosis but field data decides. Watch the experience of real visitors on mobile connections, and treat a single slow page template as a bigger problem than an average across the site.

About the author
Saleem Ahmed, Director of CodeCue Technologies
With an MSc in Project Management and degrees in Computer Science, Saleem has led a 40+ person in-house team delivering software, mobile and AI projects for international clients since 2018.
View profile