Performance starts with page weight
Many slow sites do not have one dramatic technical problem. They have a collection of small decisions that add up: oversized hero images, duplicate libraries, too many fonts, scripts that load on every page and widgets nobody uses.
Images deserve deliberate treatment
Serve images close to the size they are displayed, use modern compression where hosting supports it, provide width and height attributes, and avoid lazy-loading the main hero image when it is the likely Largest Contentful Paint element.
Keep JavaScript focused
A navigation menu or simple accordion rarely needs a large framework. Every library increases download, parse and maintenance cost. Interactive code should earn its place.
Measure real pages
Do not optimize only the homepage. Fleet pages, city pages, service pages, product pages and articles can have completely different performance profiles because their images and templates differ.
Hosting cannot fix a heavy front end
Better server response time helps, but it does not solve oversized images or excessive client-side work. The fastest infrastructure still sends the bytes the page requests.
Start with the largest assets
Images are often the biggest opportunity on small-business websites. A full-width hero image should be delivered at an appropriate size, compressed well and given explicit width and height. Images below the fold can usually be lazy-loaded, while the primary above-the-fold image should not be delayed unnecessarily.
Performance work also includes fonts, third-party scripts, duplicated libraries and CSS that loads on pages where it is not needed. A page with minimal JavaScript can still be slow if it ships oversized media or waits on multiple external services.
Measure the page people actually use
Homepages receive attention, but service pages, booking steps, contact pages and content-heavy guides may be more important to users. Test representative templates rather than assuming a single PageSpeed score describes the entire website.
Keep design and performance in the same conversation
Visual decisions have technical consequences. Large carousels, background video, multiple font families and decorative effects can increase page weight or delay rendering. A polished site does not need to be visually sparse, but each element should earn its cost.
CoquitlamLimo.ca is a useful example of a relatively lean local-service build, while Surrey-BC.ca illustrates the additional performance considerations that come with image-heavy editorial content. Different sites need different budgets.
Set practical performance budgets
- Keep hero media appropriate to the actual rendered dimensions.
- Limit third-party scripts to tools that provide clear value.
- Use modern responsive image markup where the server supports it reliably.
- Avoid loading entire icon libraries when only a few icons are used.
- Review cache behaviour after launch rather than assuming the hosting defaults are ideal.