Results

We fix the problems other developers don’t want to touch.

These are four real jobs from New Zealand client sites, with the starting numbers, the decision we made and what changed. Client names are withheld at their request, not to make the work sound bigger than it was.

Case notes

A 4,000-SKU store on shared hosting in Sydney

Category pages went from 8.4 seconds to 1.6, without a bigger server

The situation
Checkout worked, but category and search pages took eight seconds or more at any traffic. Two hosts had already recommended a larger plan.
What we found
A faceted-filter plugin was running an unindexed query across the full product table on every page render, then discarding most of the result. Server load was a symptom, not the cause.
The decision
Fix the query before touching the hardware. We rewrote the filter to use indexed lookups, added an object cache for the term counts, then migrated to Auckland for the latency win.
8.4s → 1.6sCategory page, median
−62%Database queries per page
$0Extra hardware spend

12 sites, one agency, one developer who had stopped replying

Access recovered and everything migrated in nine days

The situation
No control panel logins, no documentation, no reply from the previous developer in four months. Three sites were still running PHP 5.6 and one had an expired certificate.
What we found
Domains were registered to the agency, which was the opening: registrar-side control meant we could rebuild DNS and mail without the old developer’s cooperation.
The decision
Migrate in batches of three rather than all at once, lowest-traffic sites first, so any surprise hit the least important site. Every site came up on a supported PHP version.
12 / 12Sites recovered
9 daysStart to finish
0 minUnplanned downtime

A trades business quoting from a form nobody was receiving

Six weeks of missed enquiries found in an afternoon

The situation
Enquiries had “gone quiet”. The owner assumed the market had softened and was about to spend on advertising.
What we found
A plugin update had changed how the form sent mail. The page still showed a thank-you message; the mail was being silently rejected by the receiving server’s SPF check.
The decision
Fix the sending path, then add a database record of every submission so a mail failure can never again mean a lost enquiry, plus a monthly automated test submission that alerts us if it doesn’t arrive.
6 weeksOf enquiries recovered from logs
1 afternoonTo diagnose and fix

A membership site with 3,000 accounts and a compromised install

Cleaned, hardened and back online the same day

The situation
Google had flagged the site as deceptive. Members were seeing redirects to a third-party page on some devices but not others.
What we found
An abandoned theme with a known file-upload vulnerability, and injected code that only fired for mobile user agents arriving from search, which is why the owner never saw it.
The decision
Restore from a pre-compromise backup rather than clean in place, because a cleaned install you can’t fully verify is a liability. Then close the vector, rotate every credential and re-submit for review.
Same dayBack online, clean
0Member accounts lost

About the anonymity. Client names are withheld at their request. Every figure above is from before-and-after measurement on the live site, with page timings from server-side logs rather than synthetic tests. If you’re evaluating us seriously and want a reference, ask: some clients are happy to speak privately even when they’d rather not appear on a website.

How we decide

We’d rather show you our reasoning than our certificates

Anyone can list technologies. What’s harder to fake is a trade-off you can explain, including the times the impressive option was the wrong one.

One static HTML file per page

Where a page needs no back end, it’s plain HTML. No build step, no framework, no dependency graph. It loads fast and it will still work, unmodified, in ten years.

We talked a client out of a $30k rebuild

They’d been quoted a full headless rebuild to fix a slow store. The actual problem was two plugins and a missing index: about six hours of work.

We restore rather than clean

Cleaning a hacked install in place looks decisive, but you can never prove you found everything. Restoring from a known-good backup and closing the vector is the version we’d stake our name on.

PHP stays current, never silently

An unsupported PHP version is a security problem, so we move sites forward. Staged first, tested, switched with a rollback ready, and never without warning you.

Twenty-three years of building for New Zealand businesses, and the most valuable thing we sell is still knowing which problem you actually have.

Last reviewed 11 November 2026. Prices are in NZD and exclude 15% GST.

Next step

Recognise your site in any of that?

Tell us what you’re running and what’s going wrong. You’ll get a straight answer about what’s involved before you commit to anything.

Hand it over