Skip to main content
Case studyWeb Development

We rebuilt The Heinrich Firm’s Duda site into a high-performance Next.js platform with a 100/100 Lighthouse Performance score (desktop, September 7, 2026)

A 12-week legal website migration focused on speed, credibility, and scalable content architecture.

The Heinrich Firm website showcase
The Heinrich Firm website: tablet layout
The Heinrich Firm website: mobile layout
195
Pages Live
100/100
Lighthouse Performance

We took The Heinrich Firm’s aging Duda site-builder website and rebuilt it as a modern Next.js application designed for performance, accessibility, and long-term growth. The result was a legal website with 195 live pages (as of October 12, 2026), 100/100 Lighthouse Performance and SEO scores (desktop, median of 3 runs, measured September 7, 2026), and a cleaner foundation for conversion-focused content.

View live site
Services
  • Website Migration
  • Next.js Development
  • Information Architecture
  • Performance Optimization
  • Technical SEO Foundation
  • Accessibility Improvements
Orange fire glowing between cracked black forge coals, the heat stage of this case study, where the project's problems were brought into focus
  1. 01Heat
  2. 02Shape
  3. 03Temper
  4. 04Finish

01HeatAct 1 of 4

Where the heat was.

We gave The Heinrich Firm a faster, more credible legal website built to support consultation paths and scalable service content.

We found The Heinrich Firm's builder-based site burdened by heavy code, builder-generated URLs, weak trust and consultation paths, and reseller-controlled legal links.

The problem

Four things stood in the way.

What the work had to clear, and how each one was cleared.

  1. Challenge 1: The site builder shipped a heavy payload on every page

    The old homepage came in at about 120KB of builder-generated HTML, plus jQuery, a jQuery migrate shim, the platform’s shared runtime bundle, and two separate analytics libraries. All of it was served by the builder and its reseller, not added by the firm.

    How we cleared it

    We rebuilt the site in Next.js with route-based code splitting, lean component architecture, and only the code required for each page.

    ResultThe live site measured 100/100 for Lighthouse Performance (desktop, median of 3 runs, September 7, 2026).

  2. Challenge 2: Practice area pages sat behind builder-generated URLs

    Every interior page lived at an address like /custody/3826625, and the homepage carried two H1 headings, the second of which was the firm’s street address. The structure suited the builder rather than the people and search engines reading it.

    How we cleared it

    We designed a custom page system in Next.js that gave us full control over layout, content hierarchy, calls to action, and reusable legal service templates.

    ResultThe Heinrich Firm gained a more flexible website structure across 195 live pages (as of October 12, 2026), built to support practice area expansion and better user journeys.

  3. Challenge 3: The legacy site lacked persuasive content architecture

    The site analysis showed a homepage shell with weak content hierarchy, no visible persuasive messaging, limited trust signals, and unclear consultation pathways.

    How we cleared it

    We rebuilt the information architecture around legal practice area discovery, consultation CTAs, attorney credibility, local trust signals, and stronger internal linking.

    ResultWe delivered a clearer, conversion-oriented legal website experience designed to guide visitors toward contacting the firm.

  4. Challenge 4: The site lived inside a reseller’s account

    The firm’s site ran on a Duda instance resold through Hibu. Even the privacy, cookie, and terms links in the footer pointed at the reseller’s own pages rather than anything belonging to The Heinrich Firm.

    How we cleared it

    We rebuilt the site as a standalone Next.js application that isn’t tied to a builder platform or a reseller account.

    ResultThe firm ended up with a foundation it controls, with far fewer moving parts and no third party in the middle.

Bright molten metal flowing between dark, cracked crusts, the shape stage of this case study, where the build took its form
  1. 01Heat
  2. 02Shape
  3. 03Temper
  4. 04Finish

02ShapeAct 2 of 4

Taking shape.

We planned and built a custom Next.js site around clearer legal service pathways, reusable components, technical SEO, accessibility, and launch validation.

Build history

Project timeline.

How the work unfolded, with the decisions, releases, and deliverables recorded along the way.

  1. 01Milestone

    Platform audit and migration planning

    We started by evaluating the limitations of the existing Duda implementation, identifying performance bottlenecks, content gaps, and structural issues that were holding the site back.

    Clearschallenge 01: The site builder shipped a heavy payload on every pagechallenge 02: Practice area pages sat behind builder-generated URLschallenge 03: The legacy site lacked persuasive content architecture

    Handed over

    • Duda site architecture review
    • Migration roadmap
    • Content inventory
    • Template requirements
    • Performance and SEO baseline assessment
  2. 02Milestone

    Information architecture and legal UX planning

    We restructured the site around what prospective legal clients actually need: clear service pathways, trust-building content, and direct consultation opportunities.

    Clearschallenge 02: Practice area pages sat behind builder-generated URLschallenge 03: The legacy site lacked persuasive content architecture

    Handed over

    • Revised sitemap
    • Homepage content hierarchy
    • Practice area page framework
    • CTA strategy
    • Internal linking plan
  3. 03Milestone

    Next.js design and development

    We rebuilt the site as a custom Next.js application, moving off the builder’s page templates to reusable components and performance-first layouts.

    Clearschallenge 01: The site builder shipped a heavy payload on every page

    Handed over

    • Custom Next.js frontend
    • Responsive component library
    • Reusable page templates
    • Optimized routing structure
    • Image and asset optimization
  4. 04Milestone

    Technical SEO and accessibility implementation

    We implemented a clean technical foundation to support discoverability, crawlability, and usability from launch.

    Clearschallenge 02: Practice area pages sat behind builder-generated URLs

    Handed over

    • Metadata framework
    • Semantic heading structure
    • Accessibility improvements
    • Technical SEO setup
    • Structured page-level optimization
  5. 05Milestone

    QA, launch, and post-launch validation

    Before launch, we validated site performance, responsiveness, and implementation quality across the full build to ensure a strong production release.

    Handed over

    • Cross-device QA
    • Launch checklist
    • Lighthouse validation
    • Accessibility review
    • Production deployment support

The structure

How the site is laid out.

195 pages structured across 6 content categories.

/195 pages
195Pages
6Categories

The materials

Seven tools in the build.

What the finished site runs on, and what each piece is there to do.

  • N
    Next.jsFramework

    We used Next.js to replace Duda with a custom application architecture that supported SSR, SSG, and modern performance optimization.

  • R
    ReactFrontend Library

    We built the interface in React to create reusable components, flexible layouts, and a maintainable design system.

  • J
    JavaScriptProgramming Language

    We used modern JavaScript to power interactive components and client-side functionality across the site.

  • H
    HTML5Markup

    We structured content with semantic HTML to improve accessibility, SEO, and content clarity.

  • C
    CSS3Styling

    We used modern CSS to create a responsive, polished visual system tailored to a professional legal brand.

  • D
    DudaPrevious Platform

    The firm’s previous site ran on Duda, a hosted site builder resold through Hibu. We migrated off it to a custom Next.js build.

  • L
    LighthousePerformance Auditing

    We used Lighthouse to measure performance, SEO, accessibility, and best-practice scores on the live site (desktop, September 7, 2026).

Hammered steel shading from warm gold through violet to blue, the temper stage of this case study, where the finished build was tested
  1. 01Heat
  2. 02Shape
  3. 03Temper
  4. 04Finish

03TemperAct 3 of 4

Made to hold up.

We validated the live desktop build with Lighthouse audits and QA across performance, SEO, accessibility, and implementation quality.

The checks

Measured on the finished build.

Desktop Lighthouse, measured September 7, 2026.

100
Performance
100
SEO
100
Accessibility
96
Best Practices
A smooth steel ridge reflecting cool light, the finish stage of this case study, where the work went into service
  1. 01Heat
  2. 02Shape
  3. 03Temper
  4. 04Finish

04FinishAct 4 of 4

Put to work.

We left The Heinrich Firm with a live legal content framework built for service discovery, local visibility, and future expansion.

The outcome

What the finished work is doing.

The outcomes the project produced, with the source of each number beside it.

Best-practice implementation across the build
96/100
Lighthouse Best Practices scored 96/100 on the nkylawfirm.com homepage (desktop, median of 3 runs, measured September 7, 2026).
Measured
Accessibility at a strong production standard
100/100
We built the site with accessibility in mind, and Lighthouse Accessibility scored 100/100 on the nkylawfirm.com homepage (desktop, median of 3 runs, measured September 7, 2026).
Measured
Large-scale content foundation live
195 pages
We built the architecture behind the firm’s site, which has 195 live pages as of October 12, 2026: a scalable framework for legal service content, local visibility, and future expansion.

Answerschallenge 03: The legacy site lacked persuasive content architecture

Measured

The handover

Five things we delivered.

The work that went into the finished build, and what each part of it covered.

  • 01

    Duda to Next.js Migration

    We migrated The Heinrich Firm from a legacy Duda site-builder setup to a modern Next.js application built for speed, flexibility, and long-term maintainability.

    • Legacy platform replacement
    • Modern React-based architecture
    • Template and content migration planning
    • 195 pages live (October 12, 2026)
  • 02

    Custom Legal Website Development

    We designed and developed a custom site experience tailored to the needs of a law firm, with stronger service discovery and consultation pathways.

    • Custom page templates
    • Responsive frontend development
    • Practice area page structure
    • Trust-focused homepage design
  • 03

    Performance Optimization

    We engineered the site for speed from the ground up using Next.js capabilities and a lean frontend approach.

    • Route-based code splitting
    • Optimized assets
    • Efficient rendering strategy
    • Performance-first build decisions
  • 04

    Technical SEO Foundation

    We implemented the structural elements needed for search visibility, crawlability, and scalable content publishing.

    • Metadata framework
    • Semantic page structure
    • Internal linking support
    • SEO-ready content architecture
  • 05

    Accessibility and QA

    We validated the build across devices and usability standards to ensure the site launched with a polished, production-ready experience.

    • Accessibility review
    • Cross-browser QA
    • Responsive testing
    • Launch validation

The record

The project, on one sheet.

The facts of the engagement, for the record.

Industry
Legal Services
Delivered in
12 weeks
Launched
January 23, 2026
Start here

Need a legal website that builds trust before the first consultation?

We help law firms move beyond outdated platforms and launch high-performance websites built to showcase practice areas, strengthen credibility, and drive more qualified inquiries.