What We've Actually Shipped, With the Numbers to Prove It.

A content-heavy WordPress site whose pages weighed 2,742 KB, slowing every visit from people researching a legal problem.

• Rebuilt the site on a modern, fast stack
• Later moved about 99 hand-built static pages into one codebase with byte-identical URLs, so that move needed no redirects
• Built full English and Spanish versions across roughly 450 static pages

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

Honest note: in the same side-by-side Lighthouse run, the old site's caching plugin still loaded its main content faster (LCP 1.8s vs 2.7s). We lead with weight and scores, not LCP.

Blog post hero images up to 400 KB were loading as CSS backgrounds, pushing mobile Largest Contentful Paint to 6.0 seconds. A crawl also found 1,243 pages sharing the homepage's social preview tags.

• Converted 14 hero images to WebP (3.2 MB down to 0.93 MB) and preloaded the hero
• Gave every page its own social preview URL and tags
• Fixed broken internal links and cleared two high-severity dependency vulnerabilities

Lighthouse 98 to 100 across the tested pages after the fix pass, and zero broken links across 2,689 internal links.

The site had outgrown its original plan: a homepage error broke its stat counters, most of the main menu was invisible to crawlers, thousands of directory pages pointed their canonical tags at the wrong URL, and one 670 KB banner slowed the whole church directory.

• Fixed the homepage rendering error so the stats show correctly on first load
• Made the full navigation crawlable, reconnecting pages that had no other path in
• Set self-referencing canonical and social URLs on 5,861 church pages and 62 other pages
• Compressed the shared directory banner and removed leftover store code and emails

The three critical findings, plus the live-email and form-security issues, were fixed and shipped the same day as the audit.

Moving off WordPress meant restructuring nested service URLs that Google had already indexed, without touching the company's Microsoft 365 email.

• Mapped every old URL, including legacy slugs WordPress never listed in its sitemap, to its new page with 301 redirects
• Kept all 12 blog posts on their exact original URLs
• Checked every page for a unique title and meta description before launch
• Changed only the two website DNS records, leaving every email record untouched

The final re-audit found zero 404s across every old sitemap URL, and email kept flowing through the cutover.

Honest note: two legacy URLs that WordPress served outside its sitemap surfaced after launch. We re-crawled the old site, found two more, and redirected all four.

The rebuilt site was live, and three months of Search Console data showed search terms its service pages could match far more closely.

• Rebuilt the service pages and 25 service-area city pages on one shared, consistent layout
• Matched 13 high-value pages to real search terms from three months of Search Console data
• Added FAQ sections and fixed cross-links between related services
• Sent every change for approval as a before-and-after document before it shipped

All 13 pages passed our pre-publish checks and went live after one approval round.

Ranking impact is being measured against the same search terms about four weeks after launch. We will add the numbers here when they are in, not before.

The firm needed a site that serves clients in English, Spanish and Haitian Creole, plus focused landing pages for its ad campaigns.

• Rebuilt the site in English, Spanish and Haitian Creole with proper language tags for search engines
• Organized practice areas into clear hub-and-spoke sections
• Built 10 focused ad landing pages and refreshed 24 blog posts
• Ran a state bar advertising-rule compliance sweep across the site
• Packaged a full handoff for the firm's own developers

A complete trilingual build, handed off with documentation, a content inventory and a redirect map for the firm's development team.