TL;DR
- A 12-attorney firm had multiple outages per month on GoDaddy shared hosting — each lasting 15–45 minutes — with no monitoring, no alerting, and no knowledge of when the site was down
- We migrated to Nexcess managed hosting, configured Cloudflare edge caching and DDoS protection, and set up real-time uptime monitoring
- Uptime reached 99.98% over 12 months (less than 9 minutes of downtime); load time dropped from 6.8s to 2.1s
- 50% increase in contact form submissions in the 6 months following migration
A Law Firm's Website Became a Liability
A mid-sized law firm's website on GoDaddy shared hosting had become a problem they could no longer ignore. Multiple outages per month, each lasting 15–45 minutes, were causing contact form submissions to disappear and leaving prospective clients looking at error pages during the window they'd decided to reach out.
The firm had no way to know when the site was down. No monitoring, no alerting — downtime was reported by staff who happened to notice or, worse, by clients who had tried to use the contact form. On a shared hosting plan, the support response was to reset the server. The root cause was never addressed.
What the audit found:
- Shared hosting environment averaging 1.8 seconds Time to First Byte — before any page content loaded
- Largest Contentful Paint of 6.8 seconds — well into Google's "Poor" category for Core Web Vitals
- No page caching, no CDN, no object caching of any kind
- Multiple outages per month with no monitoring to detect them and no alerting to notify anyone
- Support interactions that diagnosed "high server load" without addressing why a single-site legal firm was on infrastructure that couldn't handle normal traffic
The 6.8-second LCP was a search ranking issue as well as a user experience issue. Google's Core Web Vitals are a direct ranking signal; a "Poor" rating actively suppresses visibility in organic search results for competitive legal keywords.
Full Infrastructure Migration to Managed Hosting
We ran the migration and optimization in parallel to minimize the transition window.
Hosting migration to Nexcess: Isolated managed WordPress environment with per-account resource allocation — no shared-server neighbors consuming the same CPU and memory pool. Server configuration tuned for WordPress workloads with PHP-FPM, built-in page caching, and Redis object caching at the infrastructure level.
Cloudflare CDN and DDoS protection: Edge caching for static assets served from Cloudflare's global network, reducing latency for visitors outside the server's immediate geography. DDoS mitigation at the network edge. Additional WAF rules for common WordPress attack patterns.
Performance tuning: Image optimization and lazy loading for above-the-fold content, caching headers configured correctly, server response time reduced by 60%.
Monitoring and alerting: Real-time uptime monitoring with instant email and SMS alerts. Downtime is now detected in under two minutes, not discovered by staff or reported by clients.
SSL and security hardening: Automatic HTTPS with Cloudflare-managed certificates, WordPress security best practices applied across the configuration.
99.98% Uptime Over 12 Months
Results measured over the 12 months following migration:
- 99.98% uptime — less than 9 minutes of total downtime across 12 months, compared to multiple outages per month previously
- Largest Contentful Paint: 2.1 seconds (down from 6.8 seconds) — moved from Google's "Poor" category to "Good"
- 3x improvement in overall Core Web Vitals scores
- 60% reduction in server response time
- Zero unplanned outages in 14+ months
- 50% increase in contact form submissions in the 6 months following migration, attributed to improved uptime and load time
The firm's website went from a liability — losing prospective client contacts during outages they didn't know were happening — to infrastructure that performs at the level a professional services firm should expect.
Frequently Asked Questions
How long does a WordPress hosting migration take for a law firm website? For a straightforward brochure-style legal site, the migration itself runs over a weekend — we migrate the files and database, verify everything works on the new host, then update DNS to point to the new server. The total project, including audit, optimization, and monitoring setup, runs 2–3 weeks.
Will migrating hosts affect search rankings? A migration done correctly — preserving all URLs, redirect rules, and canonical tags — should not negatively affect rankings. A migration to faster infrastructure typically improves rankings over time because Core Web Vitals scores improve. In this case, moving LCP from 6.8s to 2.1s moved the site from "Poor" to "Good" on Google's performance scale, which is a positive ranking signal.
What is 99.98% uptime in real terms? 99.98% uptime over a 12-month period means less than 105 minutes of downtime for the year — roughly 9 minutes per month. By comparison, multiple 15–45 minute outages per month (what the firm was experiencing on shared hosting) could total 2–4 hours of downtime per month, or 24–48 hours per year. The difference is significant for a site that depends on contact form submissions for client acquisition.
What caused the 50% contact form submission increase? Two factors: availability (the site was now actually reachable during previous outage windows) and speed (faster load times reduce abandonment before the contact page even loads). We can't attribute the full 50% to one cause, but the timing — measured against the prior 6-month baseline — correlates directly with the migration.
Does page speed affect legal search rankings specifically? Yes. Core Web Vitals are a ranking signal for all categories of content, including local legal searches. For competitive terms — "personal injury attorney [city]" or "business litigation [city]" — a "Good" Core Web Vitals rating provides a ranking advantage over competitors with "Poor" scores, all else being equal. Legal sites often have significant SEO investment that's undermined by poor infrastructure performance.