Case study · Legal · Client work

A law-firm site rebuilt about 12 times lighter.

A consumer lemon-law firm came to us with a content-heavy WordPress site. We rebuilt it on a modern stack, folded about 99 hand-built pages into one codebase without changing a single URL, and built Spanish versions across the site. The client's name is withheld for privacy.

Client work, described by industry and region. Every number below comes from our own audit and build records.

Consumer lemon-law firm homepage on a laptop, client site blurred for privacy
Consumer lemon-law firm on a phone
225 KB
Page weight afterDown from 2,742 KB on WordPress
client site · client site, blurred · captured live Oct 9, 2026
2,742 KB225 KB

page weight, old WordPress build vs our rebuild

8292

Lighthouse Performance, mobile

8695

Lighthouse Accessibility

~453

static pages with English and Spanish parity

Lighthouse numbers come from one side-by-side run of the old WordPress site and our rebuild. Page counts come from the build itself.

ClientLegalWordPress to modern rebuild
The situation

Heavy pages, two codebases.

People land on a lemon-law site while they are stressed about a car that keeps breaking down. The old WordPress pages weighed 2,742 KB each, and every extra kilobyte is time a worried visitor spends waiting on a phone.

After the first rebuild, the site still lived in two places: the modern app, plus about 99 hand-built static pages that bypassed the shared layout. Anything sitewide, like the cookie consent banner, never reached those 99 pages.

Lighthouse, three sites side by side

Same run, same settings. Green is our rebuild.
MetricOld WordPressOur rebuildNational firm
Performance829253
Accessibility8695100
SEO100100100
Largest Contentful Paint1.8s2.7s9.4s
Page weight2,742 KB225 KB961 KB

The national firm is a large consumer-law competitor, name withheld. It beats our rebuild on accessibility by 5 points, and the old site's caching plugin beats us on LCP. We show both.

What we did

A law-firm site rebuilt about 12 times lighter than the WordPress version it replaced.

Roughly 12 times lighter pages with higher performance and accessibility scores, on a codebase where one change reaches every page.

01 · The rebuild

Cut the weight, keep the content.

We rebuilt the site on a modern, fast stack and carried the content across. Page weight fell from 2,742 KB to 225 KB, about 12 times lighter, while Performance rose from 82 to 92 and Accessibility from 86 to 95. SEO held at 100.

Lighthouse, before and after

Grey is the old WordPress site, green is our rebuild
02 · One codebase

99 pages moved, zero redirects needed.

We turned about 99 hand-built static pages into native routes in the main app. Each one kept its exact URL, title, description and canonical tag, so search engines saw no change and no redirects were needed. Now one change to the shared layout reaches every page.

  • URLs kept byte-identical, so no redirect chains and no lost rankings from the move
  • Sitewide pieces like cookie consent now load on every page
  • One layout to maintain instead of two surfaces

Page weight

Old WordPress page vs our rebuild
Old WordPress2,742 KB
2,742 KB
Our rebuild225 KB
225 KB
03 · Spanish

English and Spanish, page for page.

We built Spanish versions of the hubs, tools, guides and comparison pages, reusing the English templates so both languages stay in step. A full-site crawl found 98 broken links in the Spanish section; we fixed the language toggle and navigation, and the re-crawl found zero. Legal citations stay in English, because a statute is cited by its official text.

  • Spanish hubs for 46, 51 and 25 detail pages
  • 29 Spanish learning articles and 51 comparison pages
  • Broken Spanish links: 98 before, 0 after the re-crawl
How the Spanish build stays in syncIllustration
English template and dataOne source for layout, structure and links.
Spanish twin of each pageSame template, translated text, links pointed at Spanish pages where they exist.Built
Full-site crawl, both languages98 broken Spanish links found and fixed.0 broken
Diagram of our process, not a screenshot of the client's site.
Process

How the work actually ran.

The same order every time: measure, rank, fix, then measure again and report the result either way.

  1. 01

    Measure the old site

    A side-by-side Lighthouse run of the WordPress site, our build and a national competitor.

    Baseline
    Weight2,742 KB
    Performance82
  2. 02

    Rebuild

    A modern stack, the same content, a fraction of the weight.

    After
    Weight225 KB
    Performance92
  3. 03

    Merge the static pages

    About 99 hand-built pages became native routes with identical URLs.

    Redirects needed
    Count0
  4. 04

    Build Spanish

    Hubs, tools, guides and comparisons, crawled until clean.

    Spanish links
    Broken98 to 0
The honest part

We did not win every metric.

In the same Lighthouse run, the old site's caching plugin loaded its main content faster than our rebuild: LCP 1.8s against our 2.7s. The national firm we compared against scored 5 points higher on accessibility. We lead with weight and scores, not load time.

These are lab numbers from one run, not months of field data. We do not show this client's traffic or leads without their permission.

Questions

Case study FAQ

How much lighter did the law firm's pages get?

The old WordPress page weighed 2,742 KB. The rebuild weighs 225 KB, about 12 times lighter, measured in the same Lighthouse run.

Did the rebuild beat the old site on every metric?

No. The old site's caching plugin loaded its main content faster, with LCP of 1.8 seconds against our 2.7 seconds. Our rebuild scored higher on Performance (92 vs 82), Accessibility (95 vs 86) and page weight, and tied on SEO at 100.

Did moving the static pages break any URLs?

No. About 99 hand-built pages became native routes with byte-identical URLs, titles, descriptions and canonical tags, so no redirects were needed.

Is the Spanish site machine translated on the fly?

No. Spanish pages are real pages with their own URLs, built from the same templates as the English pages. A full-site crawl found 98 broken Spanish links, which we fixed, and the re-crawl found zero.

Why is the client's name hidden?

We describe client work by industry unless the client approves being named. On a consultation we can walk you through the work in more detail.

Start free

Want numbers like these for your site?

Book the free live audit. We measure where your site stands today and show you what we would fix first. Or call (702) 609-0182.