Measure first
Run the website speed checker on your page, on mobile. It shows the three numbers Google calls Core Web Vitals, plus a list of the biggest savings.
| Measure | Good | What it means |
|---|---|---|
| LCP | 2.5 s or less | How long the main content takes to appear. |
| INP | 200 ms or less | How quickly the page reacts when someone taps. |
| CLS | 0.1 or less | How much the page jumps around while loading. |
The usual fixes, biggest first
- Shrink your images. A photo straight from a phone can be 5 MB. Resize it to the size it is shown at and save it as WebP or AVIF. This alone often halves load time.
- Do not load images that are off screen. Add
loading="lazy"to images below the first screen, but not to the main image at the top. - Give images a width and height. The browser then saves the space, so text does not jump when the picture arrives. That fixes most layout shift.
- Use fewer fonts. One or two families, a couple of weights, hosted on your own site rather than a third party. Each extra file costs time.
- Cut scripts you do not need. Chat widgets, sliders, old tracking tags and social buttons are common culprits. If nobody uses it, remove it.
- Check your hosting. A slow server slows everything. Good hosting serves pages from a network close to the visitor and caches them.
- Keep pages simple. A page with no database to query and nothing to build on each visit is fast by default.
Why static sites are quick
Binfield builds static websites: ready-made pages with no database or login system behind them. There is nothing to compute when someone visits, so pages arrive quickly even on a slow mobile connection.
Check again
After each change, test again. Speed tests vary a little from run to run, so look for a clear improvement rather than a single point.
Get a speed score, the biggest savings and basic SEO checks for any page.
Test your site speed