The Moses Law Firm

The challenge

People land on a workers’ comp site at a bad moment: hurt, off work, and unsure whether to trust anyone. The site has to answer the questions insurance carriers won’t (what’s covered, how attorneys actually get paid, what to do first) and make reaching a real person feel easy, not like filing paperwork.

Where it started: WordPress

Our first build for the firm was on WordPress. It led with the client’s question (“Have you suffered a work-related injury?”) and answered it in plain language: how contingency fees work, why reporting the injury early matters, and video explainers of the system, with Google reviews and a two-decade track record carrying the credibility. The firm managed its own content, and that plain-language approach is what carried forward.

Why we streamlined it

The firm’s site is mostly stable, written guidance: what to do after an injury, what benefits exist, how a denial is appealed. On WordPress that guidance sat behind a theme, a plugin stack, and a database, all of which needed patching, and every page was assembled again for every visitor. For a small practice with no web staff, that was upkeep with nothing to show for it.

So we kept the voice and the structure, and replaced the delivery model with something much smaller.

The rebuild on Astro

The new site is built with Astro and served from Vercel. All 48 public URLs are rendered to finished HTML at build time, so nothing is assembled per visit and there is no database behind the pages. The home page loads a single script of about 1 kB gzipped. Firm details are published as LegalService and Attorney structured data on every page.

Heavier features load only when someone uses them. The attorney’s explainer video shows a poster until a visitor presses play, and only then brings in the Vimeo player. On Areas We Serve, a ZIP check tells a visitor whether they are in the region, and the Mapbox map library downloads only as the map scrolls near the screen.

The content grew with the move: a guide for each of the 15 communities the firm serves, covering local employers and where to start, and 18 Insights articles in four topics (filing a claim, your benefits, your rights, denied claims) answering the questions clients actually ask.

Intake, one question at a time

The free case review is a four-step conversation instead of a long form. It asks which situation sounds closest (a new injury, a denial, benefits that stopped, pressure to return to work), when it happened, how far along the claim is, and how the person would like to be reached. Every option carries a short line in plain language, such as “Timing decides which deadlines apply. An estimate is fine.”

Submissions post to a single server endpoint behind Cloudflare Turnstile, and the form says plainly that the message goes to the firm directly and that contacting them does not create an attorney-client relationship.

Nothing lost in the move

Old WordPress addresses forward permanently to their new homes, so the blog and resources now land on Insights and the attorney profile on the new attorney page, keeping years of inbound links working. The deployment adds a strict Content Security Policy, HSTS preload, a locked-down permissions policy, and a rule that the site cannot be framed by anyone else.

Accessibility, stated precisely

Injured workers include people navigating with one hand, on a phone, in pain. The rebuild has a skip link, a single page heading on each page, and pause controls on both moving elements, the practice-area ticker and the review carousel. The video player loads with a title for screen readers.

To be precise about the claim: those are patterns we built and checked, and the dated Lighthouse run below reports a 100 for accessibility on the home page. We have not published a formal conformance audit of the site.

Google PageSpeed Insights