Your digital business.
Connected. Protected. Growing.

The problem

The original pages had all been generated by a bulk import tool that packed each page into one dense, unreadable block rather than proper design-tool components. That meant the client couldn't safely update their own content — and we couldn't either, without real risk of breaking the page for visitors.

What Lighthouse did

• Rebuilt all 13 core pages using proper, editable design components — extracting every piece of existing content (text, images, layout) from the old format rather than rewriting it
• Preserved exact SEO titles and meta descriptions across every page
• Kept sensitive details (donation account information, an embedded map) exactly correct, double-checked before and after the change
• Built and QA'd each page privately first, then swapped it into the live URL — so visitors never saw a broken or half-finished page
• Found and fixed a genuine server bug along the way — a data-formatting issue that caused one page to briefly fail — before it could affect any other page

The result

• All 13 pages live, independently verified page-by-page by fetching the real production URLs directly — not just checking that a database write succeeded
• Every page is now made of real, distinct, editable sections — the client's own team can safely update their content going forward
• Zero URLs changed, so nothing was put at risk in search rankings by the rebuild itself

The problem

The site was intermittently slow and showing signs that didn't fully match normal WordPress behaviour. Rather than just clearing caches and moving on, we treated it as a possible security issue and investigated at the server level.

What Lighthouse did

• Connected directly to the server to inspect real files and the database, not just the WordPress admin screen — which a compromised site can't be trusted to report honestly
• Identified a disguised plugin functioning as a backdoor, confirmed it had zero legitimate use on the site, and removed it
• Verified the core site configuration was clean and no other unauthorised access points existed
• Separately root-caused a recurring slow/unresponsive server issue to genuine memory pressure — partly normal traffic, partly our own monitoring checks running too aggressively — and corrected the monitoring pacing

The result

• Backdoor fully removed and independently reverified through a second server check, not just assumed fixed
• Site confirmed healthy and stable throughout, with no evidence the vulnerability had been exploited
• Monitoring adjusted so it observes the site without contributing to the same load problem it exists to catch

The problem

The domain needed to move to a modern DNS provider for better security and performance, but the same domain also routes the business's day-to-day email — a single wrong record during the switch is a common way real companies lose email for hours or days.

What Lighthouse did

• Audited every existing DNS record before touching anything, so nothing — especially mail records — was assumed rather than confirmed
• Rebuilt the full DNS record set on the new provider first, verified it matched exactly, then switched nameservers
• Left mail delivery completely untouched by the change, by design, not by luck
• Verified propagation and live functionality for both the website and email after the switch, rather than assuming the change had taken effect

The result

• Full nameserver migration completed with zero reported downtime for either the website or email
• Modern DNS security and performance gained without the risk usually associated with this kind of change