Most New Zealand business owners have been told to care about how fast their website loads. The advice was right for a long time. Load speed sat at the centre of every conversation about web performance, and tools like Google PageSpeed Insights trained a generation of agency clients to chase the green numbers next to largest contentful paint and first input delay.
But the way Google now measures whether a site actually feels good to use has moved on, and a quietly damaging gap has opened up. A site can load quickly, score well on every public-facing performance test, and still feel sluggish the moment a real customer tries to do anything on it.
The metric that captures this is called Interaction to Next Paint, or INP. It replaced First Input Delay as one of the three Core Web Vitals on 12 March 2024, and after two full years inside the formal Google ranking signal, INP is now the responsiveness number that matters. Where First Input Delay only ever scored the first tap or click after page load, INP looks at every interaction across an entire visit and reports the slowest one your customers actually experienced. The bar is 200 milliseconds at the seventy-fifth percentile, and any site over 500 milliseconds is flagged as poor.
According to the 2025 HTTP Archive Web Almanac, 77 percent of mobile pages and 97 percent of desktop pages now pass INP. Those headline numbers sound healthy until you look at where the failures cluster. Secondary pages on mobile, the product pages, the shopping carts, the contact forms, the booking screens, sit eleven percentage points behind the home page. In other words, the page a visitor lands on tends to be fine. The page that actually decides whether they buy something or pick up the phone is where the responsiveness problems hide.
This pattern shows up consistently in the audits Forge Creative runs on inherited New Zealand websites. A retail home page loads in well under two seconds. A customer adds a product variant on a mobile, taps the size selector, and waits half a second for the dropdown to respond. The page already loaded. Speed is not the problem. The main thread is the problem.
Almost everything that makes a modern website feel sluggish after load comes down to how busy JavaScript keeps the browser. Every plugin, every tag, every chat widget, every analytics pixel, every popup builder, every social share bar adds code that runs on the same single main thread that also has to react to taps and clicks. When the browser is in the middle of running a long task, your customer tap goes into a queue. Two hundred milliseconds is roughly the threshold where a human starts to feel that the interface is stuck.
Long tasks of more than fifty milliseconds are the silent killers. Performance work documented across the WordPress optimisation community keeps surfacing the same culprits, and they are not exotic. Social share buttons that inject heavyweight scripts into every interaction routinely add 200 to 300 milliseconds to a tap. Chat and live help widgets, Google Tag Manager loaded eagerly rather than deferred, A/B testing scripts that block rendering until they decide which variant to show, heatmap tools that record every move on the page, and retargeting pixels from advertising platforms all stack into one slow interface.
The damage is twofold. The first is human. People who experience a sluggish site leave a sluggish site, and they do not return. NZ Post Business IQ data on online spending shows New Zealanders are now buying more often but spending less each time, and 46 percent of shoppers say discounts and special offers are the single biggest factor in deciding where to shop. That puts intense pressure on conversion. A slow tap on a product variant or a buggy postcode field is the difference between a basket and a bounce. The second is structural. Google has built INP into search ranking, which means a site that feels slow under real customer use is also a site that ranks lower than the competitor who does not.
Most of the work to fix INP is unglamorous but cheap. It starts with an honest audit of what the site is loading and why. New Zealand small business sites I look at typically run between fifteen and forty active third-party scripts. Most of them are forgotten. A site might still be loading a Facebook pixel from a campaign that ended in 2022, a Hotjar recording session sampling one in every hundred users that nobody has reviewed in eighteen months, and three different analytics tools because three different agencies set them up at different points and nobody removed the previous one.
The next step is to defer everything that does not need to run before the page becomes interactive. A chat widget does not need to load in the first second. A retargeting pixel does not need to run before a customer has decided to look at the product. Most popular plugins and tag managers now support deferred or interaction-based loading. They are simply not switched on by default.
Beyond that, modern frontend tooling makes breaking up long tasks more practical than it used to be. The Scheduler API and helpers like requestIdleCallback let JavaScript yield to the browser between chunks of work, which means a tap can be processed during what would otherwise be a single long task. Web workers move heavy work like search indexing or pricing calculations off the main thread entirely. None of this is bleeding-edge, and almost none of it is being used on the typical New Zealand small business website.
There is one habit worth changing for any business owner reading this. Stop testing your site only on the home page, only on desktop, and only on the fast wifi connection in your office. Open it on your own phone, in the carpark, on the page where customers actually decide to give you money. Tap things. If you have to wait a noticeable beat between any tap and the screen responding, you have an INP problem, and you have a customer-experience problem that is showing up in revenue whether you can see it or not.
The websites that quietly win in 2026 are not the ones with the highest PageSpeed score. They are the ones that respond instantly to every tap, on a mid-range Android, on a four-bar 4G connection, on the page that matters. Two hundred milliseconds is not a technical target. It is the line between a customer who feels in control and a customer who reaches for the back button.
Roger McSaveney is General Manager of Forge Creative, an Auckland web design and development agency.
Have you noticed your own websites feeling slow even after they load? Share what you have found and what has helped in the comments below.
This article was written by AI, briefed to report the facts, hopefully without some of the bias people bring to the job 🙂
Leave a Reply