Website Speed and Core Web Vitals for NZ Businesses

Website speed in NZ is measured by Google with three Core Web Vitals: Largest Contentful Paint (LCP), which should be 2.5 seconds or less; Interaction to Next Paint (INP), which should be 200 milliseconds or less; and Cumulative Layout Shift (CLS), which should be 0.1 or less. Hit all three for at least 75% of real visits and your pages pass. For New Zealand businesses, the biggest wins usually come from smaller images, fewer plugins and scripts, efficient fonts, and hosting close to your customers.

A fast website does two jobs. It gives Google one more reason to rank you, and it keeps impatient mobile visitors on the page long enough to call or buy. This guide explains each metric in plain English, how NZ conditions affect them, and the fixes we apply when building and tuning sites.

What are Core Web Vitals?

Core Web Vitals are a set of metrics Google uses to measure real-world user experience on a web page: how quickly the main content appears, how quickly the page responds when someone interacts, and how stable the layout is while it loads. They form part of Google's page experience signals in search. The official definitions and thresholds are published on web.dev.

Google assesses each metric at the 75th percentile of page loads, split by mobile and desktop. In practice, that means your slowest quarter of visits decides whether you pass.

LCP: how fast the main content appears

LCP usually measures your hero image or headline. On most small-business sites, slow LCP comes from a large, uncompressed hero photo, a slow server response, render-blocking CSS and JavaScript, or a hero image that is lazy-loaded when it should load first.

INP: how responsive the page feels

INP replaced First Input Delay (FID) as a Core Web Vital in March 2024. Where FID only looked at the first interaction, INP looks at responsiveness across the whole visit. Poor INP is usually caused by heavy JavaScript: page builders, chat widgets, tracking tags, sliders and pop-ups all competing for the phone's processor. Google's INP guide covers the technical detail.

CLS: whether the layout jumps around

CLS measures unexpected movement, such as when you go to tap a button and an image or banner loads above it, pushing everything down. The usual causes are images without width and height set, ads or embeds without reserved space, cookie banners that push content, and web fonts that swap in at a different size.

Why website speed matters for NZ businesses

Most local searches happen on phones, often on the go. Someone searching "emergency plumber Mt Albert" from their driveway will not wait for a slow page. They will hit back and call the next result. Speed is rarely the only reason a site does not convert, but it is often the first reason people leave.

Speed also affects your marketing costs. Google Ads considers landing page experience when assessing ad quality, and a slow landing page can push up what you pay for each click. If you are running ads, our Google Ads management includes checking that your landing pages load fast.

NZ factors that affect website speed

Mobile networks and coverage

New Zealand's mobile networks (One NZ, Spark and 2degrees) offer fast 4G and 5G in cities, but real-world speeds vary a lot. Signal drops inside buildings, in parts of rural and semi-rural Auckland such as the Hunua Ranges or the outer west coast beaches, and when networks are busy. A page that loads instantly on office fibre can crawl on a weak mobile signal. Test on a real phone, not just your laptop.

Hosting location

New Zealand is a long way from most data centres. If your website is hosted in the United States or Europe, every request your visitor's phone makes has to cross the Pacific and back, adding noticeable delay before the page even starts loading. Hosting in New Zealand or Australia, or using a content delivery network (CDN) with nearby edge locations, cuts that delay. Our guide to choosing website hosting in NZ goes into this in detail.

Cheap shared hosting

Location is only half the story. Budget shared hosting crams hundreds of sites on one server, and a slow server response hurts LCP on every page. Quality managed hosting with server-side caching often makes a bigger difference than any plugin.

How to speed up your website: the fixes that matter

1. Optimise images

   Resize images to the size they are actually displayed, compress them, and serve modern formats such as WebP or AVIF. Set width and height on every image to prevent layout shift. Lazy-load images below the fold, but never the hero image, which should load immediately.

2. Prioritise the hero

   Make sure the LCP element loads first. Preload or set high fetch priority on the hero image, and avoid hero sliders and background videos that delay the main content.

3. Fix fonts

   Use one or two font families with only the weights you need. Self-host them in WOFF2 format, preload the main font, and use font-display settings that show text immediately. Pick fallback fonts with similar sizing to limit layout shift.

4. Cut plugins and scripts

   Audit every plugin, tracking tag and widget. Remove what you do not use, replace heavy page builders where possible, and delay non-essential scripts like chat widgets until after the page loads. This is the single biggest INP fix on most WordPress sites.

5. Improve hosting and caching

   Move to quality hosting close to your audience, enable page caching, use a CDN, and keep PHP and server software up to date.

6. Reserve space for late content

   Give embeds, maps, banners and cookie notices a fixed space in the layout so nothing jumps when they load.

Common speed killers on NZ small-business websites

When we audit slow sites for Auckland businesses, the same culprits come up again and again.

• Full-size phone photos: a 5MB photo straight off a camera, displayed at 600 pixels wide, is one of the most common causes of poor LCP.
• Hero sliders and background video: they look impressive on a desktop screen but delay the main content and often get ignored on mobile anyway.
• Page builders stacked on page builders: heavy WordPress builders combined with add-on packs load large amounts of CSS and JavaScript on every page, whether it is needed or not.
• Too many tracking tags: old pixels from past campaigns, multiple analytics tools and duplicated tags all compete for the browser's attention and hurt INP.
• Chat and review widgets: useful, but many load large scripts immediately. Delay them until the visitor interacts or scrolls.
• Embedded maps and videos: a Google Map or YouTube embed can add a lot of weight. Use a lightweight placeholder that loads the real embed only when tapped.
• Overseas budget hosting: a cheap plan on a crowded server in another hemisphere adds delay before anything else starts.

None of these require a full rebuild to fix. Most can be resolved in a focused speed tune-up, which is often the quickest way to improve both rankings and enquiries.

How to measure your Core Web Vitals

• PageSpeed Insights: enter a URL to see both field data (real visitors, from the Chrome User Experience Report) and a lab test with specific recommendations. Field data is what Google uses.
• Google Search Console: the Core Web Vitals report groups your URLs into good, needs improvement and poor, for mobile and desktop.
• Chrome DevTools and Lighthouse: useful for developers diagnosing exactly what loads and when.

Small sites with low traffic may not have enough real-world data for field results. In that case, use the lab scores as a guide, and test on a mid-range phone over mobile data.

Platform choice and speed

Platform affects how easy it is to stay fast. Hand-coded static sites are usually the quickest because there is no database or plugin layer. Well-built WordPress sites can be very fast, but plugin bloat is common. Shopify and Webflow handle hosting and CDN for you, so speed mostly comes down to theme quality, apps and images. Wix and Squarespace have improved, but you have less control. We compare the options in WordPress vs Shopify vs Webflow.

Keeping your website fast after launch

Speed tends to degrade over time as new plugins, tracking tags and full-size photos get added. Check your Core Web Vitals report every month or two, compress images before uploading, and question every new script. Our website maintenance and hosting plans include NZ hosting, updates and performance checks so the site stays quick.

Built fast from the start

Every site we build is designed mobile-first, with performance budgets, optimised images and minimal scripts, and checked against Core Web Vitals before launch. If you need something more custom, our web development team builds hand-coded and headless sites where speed is the priority. Speed is part of what web design in Auckland should include by default, not an extra.

Want to know where your current site stands? See our website pricing or book a free 20-minute website plan, and we will check your speed, your competitors' speed and what is worth fixing.