Compress the hero image and serve it in WebP or AVIF, self-host one or two font files, keep JavaScript off the critical path, and serve static pages from a CDN. Google's published "good" thresholds are Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less.
The three numbers that matter
Google measures real visits through the Core Web Vitals, and publishes thresholds for each metric on web.dev:
| Metric | Measures | Good |
|---|---|---|
| LCP | When the main content appears | 2.5 s or less |
| INP | How quickly taps and clicks respond | 200 ms or less |
| CLS | How much the layout jumps while loading | 0.1 or less |
For a local business site, LCP is almost always the hero image or the main heading. Start there, because it is the largest and most fixable number.
1. Fix the hero image first
- Export at the size it is displayed, not at camera resolution. A 3000px screenshot shown at 700px is wasted bytes.
- Use WebP or AVIF rather than PNG or JPEG where the browser support allows it.
- Set width and height attributes so the space is reserved before the image loads. This one habit removes most layout shift.
- Add
fetchpriority="high"to the hero image and lazy-load everything below the fold. - Skip the slideshow. A carousel of three images usually triples the hero weight and nobody sees slide three.
As a rough guide, a full-width hero should be a few hundred kilobytes, not several megabytes. I resized nine portfolio screenshots for this site from about 21MB of PNG files to roughly 1MB of compressed JPEG and WebP.
2. Cut the fonts down
Every extra family is another connection and another file. Two is plenty: one for
headings and body, one for labels if you need it. Self-host the files, use woff2 with
font-display: swap, preload the one used above the fold, and load only the
weights you actually use.
Third-party font services add a DNS lookup and a connection before the text can render. Self-hosting removes both and keeps working if that service has a bad day.
3. Keep JavaScript off the critical path
A local business site needs very little JavaScript: a menu toggle, form validation and maybe analytics. That is fine. What hurts is a stack of trackers, a chat widget that loads before the page, an animation library for a fade-in, and sliders that pull in several more files.
Put content in the HTML so it appears before scripts run, defer anything non-essential, and ask whether each script earns its weight. If you cannot name what a script does for the customer, remove it.
4. Serve it from somewhere close
Static files behind a CDN are hard to beat for a site that changes weekly: the visitor is served from a nearby location and the origin is barely involved. Cache HTML and images with long lifetimes and versioned file names, and the repeat visit becomes almost instant.
5. Measure before and after
- Run the page through PageSpeed Insights on the mobile profile.
- Record LCP, INP and CLS. Write the numbers down.
- Make one change and measure again. Changes made in a batch cannot be judged.
- Once the site has real traffic, use the field data in Search Console. Lab scores can be optimistic.
A site can score well and still feel slow if the first screen is a blank placeholder. Speed is not the score; it is whether the visitor sees the answer before they lose patience.
Font, image and hosting decisions overlap. If you are still choosing where the files will live, read website hosting explained, and for the layout side of the same problem, mobile-first design.