Speed is both a user experience issue and a competitive issue. Customers abandon slow checkout flows; Google uses page experience signals among many ranking factors. For NZ businesses, the biggest wins usually come from image discipline, reducing render-blocking scripts, better hosting, and avoiding oversized “everything-in-one” page builders.
What are Core Web Vitals in plain English?
- LCP (Largest Contentful Paint): how quickly the main content becomes visible.
- INP (Interaction to Next Paint): how responsive the page feels when users tap or click.
- CLS (Cumulative Layout Shift): how much the layout jumps around while loading.
Think of them as “loads fast, feels responsive, does not jiggle”.
What are the usual culprits on small business sites?
- Massive unoptimised images and hero banners.
- Too many third-party widgets (chat, trackers, heatmaps, ads).
- Heavy themes and excessive plugins.
- Slow server response time on cheap hosting.
What fixes give the best ROI first?
- Resize and compress images; use modern formats where possible.
- Remove widgets you do not actively use.
- Enable caching appropriately (without breaking checkout).
- Upgrade hosting if time-to-first-byte is consistently poor.
How do you measure honestly?
Use a combination of Lighthouse (lab tests) and real-user monitoring where available. Test on a mid-range phone. A desktop-only score is misleading for most NZ local traffic.
Where can you get help implementing fixes?
If your site needs performance hardening alongside design work, NZDH can assist—especially when speed problems are structural, not just “one plugin toggle”.
Frequently asked questions
Do I need a perfect100 score?
No. Aim for “fast enough” for users and stable metrics, not trophy scores.
Will AMP fix everything?
Not necessarily. AMP is a strategy, not a substitute for good assets and templates.
Why did speed get worse after a redesign?
New visuals often add weight. Redesigns should include a performance budget and testing.
LCP, INP, and CLS in plain language
Largest Contentful Paint (LCP) measures how quickly the main content appears—often a hero image or heading block. Optimise server response, preload critical assets, and avoid massive unoptimised images.
Interaction to Next Paint (INP) replaces First Input Delay as the responsiveness metric—how fast the page reacts when someone taps a button or opens a menu. Reduce JavaScript bloat and third-party widgets.
Cumulative Layout Shift (CLS) captures visual stability—elements jumping while loading frustrate users and fail thresholds. Set width/height on images and reserve space for ads or embeds.
Google documents these at web.dev/vitals; field data in Search Console reflects real NZ users on real connections.
Fix order for SME sites
- Upgrade hosting or enable caching if TTFB is slow.
- Compress and resize images; use modern formats (WebP/AVIF).
- Audit plugins and chat widgets adding JavaScript.
- Implement lazy loading without breaking LCP hero images.
- Re-test with PageSpeed Insights and our website checker.
Professional page speed optimisation addresses theme-level issues that plugins alone cannot fix.
More guides in this topic
- Image formats for the web: WebP, AVIF, and “good enough” JPEG
- Lazy loading without wrecking Largest Contentful Paint
- Font loading strategies that reduce layout shift
- Third-party scripts: chat widgets, trackers, and the performance tax
- Caching layers explained simply: browser, page, and object cache
Browse the full Speed & performance guide hub or return to the guides home.
Explore on NZDH.co.nz
- All practical guides
- Website design services
- SEO services
- Recent website projects
- Frequently asked questions
Authoritative further reading
These independent resources complement this guide. Search engines and customers both reward accurate, helpful information—we link out where official documentation or regulators explain the topic better than a generic blog post could.