Website speed optimisation: Faster websites. More customers.

What I measured on New Zealand websites

• 62%

  of 715 popular .co.nz websites fail Google's Core Web Vitals for their real visitors.

• 39%

  of them take longer than 2.5 seconds to show their main content.

• 14

  third-party services load on the typical slow site I audited, bringing 1.3 MB of JavaScript with them.

Method, sample sizes and all results: Core Web Vitals in New Zealand, 2026 →

What other research found

• +8.4%

  more conversions for retail sites after a 0.1-second mobile speed improvement.

• +32%

  higher chance a mobile visitor bounces when load time goes from 1 to 3 seconds.

• Core Web Vitals

  are part of the page experience signals Google Search uses for ranking.

Even a small image can be the slow part if the browser finds it late: Why your LCP image loads late →

• Fixed price

  Performance audit

  A thorough, data-driven analysis of what slows your site down, with a clear plan to fix it.

  • Core Web Vitals analysis (loading, responsiveness, visual stability) from real-user and lab data
  • Review of JavaScript, CSS, images, fonts, third-party scripts, caching and hosting
  • A prioritised action plan, walked through with your team in 60 minutes

  Duration

  about 1 week

  What the audit covers →

  Ask about an audit

• Hands-on

  Optimisation sprint

  I implement the fixes directly in your codebase, on my own or alongside your developers.

  • The highest-impact fixes, delivered as reviewed pull requests
  • Before/after measurements for every change
  • Knowledge transfer, so your team keeps the gains

  Duration

  2–4 weeks or custom

  Ask about a sprint

• Ongoing

  Performance partner

  Keep your site fast as it grows and changes.

  • Real-user monitoring and alerts
  • Performance budgets in your CI pipeline
  • Regular performance reviews of new features
  • Team workshops on writing fast frontend code
  Ask about ongoing support

Planning a relaunch? I've led greenfield builds on Next.js and Angular that are fast from day one. Let's talk →

I specialise in JavaScript-based websites and apps: React, Next.js, Angular and Node.js, headless CMSs like Storyblok, and shop systems like Shopware and Shopify.

• Lead Developer (Fullstack) · 2024–2025 · Adult education

  One fast platform for several academies

  Education Partners

  One website platform and CMS to replace several ageing systems, including the whole build and release process; six academies live, ahead of schedule.

  Read the details

  The challenge

  Each academy website ran on its own ageing tech stack, with nothing shared between them.

  What I did

  • A new platform built from scratch on Next.js and Storyblok as a CMS (Headless).
  • A set of reusable content blocks, so editors can build pages themselves.
  • A design system that still lets every academy keep its own look and feel.
  • Automated build and release on Vercel, so a change goes live without manual steps.
  • Automated tests, covering both the single pieces and whole user journeys.
  • Speed treated as a requirement from day one, not as a fix afterwards.
  • Shared standards, guidelines and tooling, so the whole project works the same way.

  The outcome

  • Six academies finished and deployed ahead of schedule.
  • Search results with no noticeable wait.
  • Google page-speed scores around 95 out of 100.

  • React
  • Next.js
  • TypeScript
  • Storyblok
  • Shopware
  • Stripe
  • Vercel

  marketing-fernakademie.de (opens in a new tab)

• Senior Fullstack Developer · 2024 · Travel e-commerce

  A new shop version, shipped on a tight deadline

  7Fridays

  Extra senior capacity for the shop, back office and merchant portal, with the older code brought up to date along the way; the new shop version shipped on time.

  Read the details

  The challenge

  An eco-travel shop covering the whole journey, from accommodation to activities, needed more senior development capacity for its shop, back office and merchant portal — on a tight release timeline.

  What I did

  • New features across the shop itself and the systems behind it.
  • Performance work, so pages respond quickly for customers.
  • Older parts of the codebase brought up to current practice, so new features stay quick to build.
  • Automated tests, covering both the single pieces and whole customer journeys.
  • Advice on how the team planned and ran its sprints.

  The outcome

  • The new shop version released on time, despite a tight timeline.
  • A codebase the in-house team can keep moving in.

  • React
  • Next.js
  • NestJS
  • GraphQL
  • TypeScript

  7f.com (opens in a new tab)

• Frontend Developer · 2021–2023 · Building-supplies retail

  50,000 products in one table, still responsive

  hagebau

  Internal tool for editing prices and stock.

  Read the details

  The challenge

  The pricing and stock team needed up to 50,000 articles in front of them at once, in the browser, with search that answers instantly and prices that can be changed in bulk.

  What I did

  • A React component library as the shared foundation for the tool.
  • Components built to redraw only what actually changed on screen — needless redrawing is one of the most common reasons an app feels sluggish.
  • A purpose-built table instead of an off-the-shelf one, so it could carry the full data set.
  • Code loaded only when it is needed, instead of everything upfront.

  The outcome

  • All 50,000 articles in a single view, scrolled or paged through.
  • Search results with no noticeable wait.
  • Pricing rules changed for thousands of articles in one go.

  • React
  • TypeScript
  • Node.js

• Lead Developer (Frontend) · 2022–2024 · B2B e-commerce

  Data-heavy dashboards that stay fast on low-end PCs

  hygi.de

  Internal reporting platform where teams build their own dashboards, and the charts stay fast even with a lot of data on ageing office PCs.

  Read the details

  The challenge

  Build an internal reporting platform on Angular, where every team can put together its own dashboards from several data sources. The charts hold a lot of data points, and the people using them work on low-powered office computers.

  What I did

  • An Angular component library as the shared foundation for the whole platform.
  • A configuration system that turns a saved setup into a live metric, with its own queries and filters.
  • A flexible data layer that pulls from several sources and combines them into one chart or KPI.
  • A full set of metric types: pie, XY and stock charts, tables and KPIs.
  • A point-and-click interface, so users build their own dashboards without a developer.
  • Performance work so all of it stays responsive on everyday office hardware.

  The outcome

  • Part of the company's day-to-day BI systems.
  • Handles large, complex metrics on low-powered computers.
  • Every dashboard change is kept, so any earlier setup can be restored.
  • Documented for a smooth handover to in-house developers.

  • Angular
  • TypeScript
  • GraphQL
  • Hasura

1. 01

   Free speed check

   You send me your URL. I run a first analysis and tell you honestly whether there's real potential.

2. 02

   Audit and plan

   I analyse real-user data and lab tests, look at your code and infrastructure, and hand you a prioritised plan.

3. 03

   Fix and measure

   I implement the highest-impact improvements with your team and measure each change against the baseline.

4. 04

   Keep it fast

   Performance budgets and monitoring catch regressions before your customers notice them.

• What does the free speed check include?

  I look at your homepage and one key page, such as a product or landing page, using lab tests and real-user data where Google has it. You get the 3 most valuable quick wins. There's no obligation and no sales pitch.

• Which technologies do you work with?

  I specialise in JavaScript-based stacks: React, Next.js, Angular, Node.js and NestJS, headless CMSs like Storyblok, and shop systems like Shopware and Shopify, hosted on platforms like Vercel. The fundamentals (images, fonts, caching, third-party scripts) apply to any website.

• Do you need access to our code?

  Not for the free check or the first part of an audit, which works on your public website. For a deeper analysis and for implementing fixes, read access to your repository and analytics helps a lot.

• How do you measure success?

  We agree on a baseline and targets at the start, usually Core Web Vitals from real users plus lab measurements. Every change is measured against that baseline, and you get a before/after report.

• How long does it take?

  The free speed check comes back within 2 business days. An audit takes about a week, from the go-ahead to the walkthrough. Optimisation sprints run 2–4 weeks, depending on scope.

• I'm in Europe. Does working with someone in New Zealand work?

  Yes, I've worked with German companies for more than ten years. Calls fit into your morning (my evening), and much of the work happens while you sleep, so there's progress waiting when you start your day. Communication is available in German or English.

• Can you sign an NDA?

  Yes, of course.

• What does it cost?

  The speed check is free. Audits have a fixed price of US$2,400, excluding GST. Implementation work is priced per sprint or day rate, depending on scope. You'll always get a quote before any work starts.

• Do you also build new websites?

  Yes. I've led greenfield projects such as a unified Next.js platform for several education academies. If a relaunch is the better option, I'll tell you.

Still have a question? Just ask →