A heavy WordPressstack, rebuilt for speed.
A WordPress site that had been there too long, without a cleanup cycle.
Most clinical-network sites accumulate weight over time. Plugins stack. Themes fork. Post revisions never get pruned. Page builders leave deprecated widgets in the DOM. That's what we inherited here, and it was quietly throttling the content strategy above it.
- 01A
5.8-second load timeon the top ten landing pages, which is exactly where the highest-intent search traffic was landing.Patients typing “suboxone clinic near me” don’t wait six seconds. Every additional second on LCP above 2.5s compounds bounce rate exponentially in a crisis-intent category. - 02A database bloated with
orphaned revisions, autosaves, and expired transients, slowing every uncached page query.68% of the database turned out to be deletable rows that hadn’t done useful work in months. The cleanup alone cut query time before a single server change. - 03Core Web Vitals in the
Failed tieracross LCP, INP, and CLS on the clinic-location-page template.The template that carries 70% of non-brand organic traffic was the worst-performing one. Every location page’s CWV score dragged the domain’s crawl priority down with it. - 04A
62% bounce rateon organic landings, masking the real underlying content engagement.When the page takes six seconds, you can’t tell whether the user bounced because the content was wrong or because they gave up waiting. Fixing the infrastructure was the only way to see if the content was doing its job. - 05A page-builder stack with
deprecated widgets on 14 location pages, shipping unused JavaScript on every request.Dead widgets rendered invisible DOM, forced layout shifts, and bloated the main thread. We audited and cut every widget that didn’t participate in a real user interaction.
Prune first. Rebuild the template second. Measure everything.
Dropped orphaned post revisions, autosaves older than 30 days, expired transients, and residue from three uninstalled plugins. 68% row-count reduction, same content.
Rebuilt the clinic-location-page template in native WordPress blocks + a thin custom loop. Killed the page-builder dependency that accounted for 14 deprecated widgets and ~40% of the main-thread work.
Images converted to WebP at responsive sizes via srcset. Render-blocking scripts deferred. Unused plugin scripts dequeued per-template so they only load where they run.
WP Rocket page cache rules reset to respect the updated template hierarchy. Cloudflare rules tightened to cache aggressively and bypass wp-admin only. HTML/CSS/JS hit the edge.
Search Console CWV report wired to Orbit. Every deploy that touches the site gets a post-deploy crawl and fails loudly if any page leaves the Good tier.
60-day window before measuring the bounce-rate and content-engagement impact, so the lift was attributable to the infrastructure change, not seasonal traffic or content rotation.
Four metrics. Same site. Different infrastructure.
Desktop LCP, measured in PageSpeed Insights across the top ten landing pages.
Row count + table size after cleanup of orphaned post revisions, autosaves, expired transients, and legacy plugin residue.
All three metrics (LCP, INP, CLS) moved into Good across the clinic-location-page template, which carries most of the non-brand traffic.
GA4, 30-day rolling window pre-rebuild vs. 30-day window 60 days post-rebuild. Same template, same content, faster delivery.
A fast site did not cause the lead growth. It removed the reason the lead growth wasn't happening yet.
Four compounding effects.
- Crawlers reached more pages. Faster server response lifted crawl budget; Search Console indexed coverage grew without adding content.
- CWV feeds ranking signals. Good-tier Core Web Vitals on the clinic-location template removed a negative ranking factor that had been quietly capping the pages that carry the most non-brand intent.
- Real engagement became visible. Dropping bounce from 62% to 41% wasn't the rebuild convincing people to read; it was the rebuild getting out of the way so the people who wanted to read could.
- Attribution stayed honest. A fast site means the first-session CRM pixel fires on the actual first session, not after a reload. The +9% YoY organic-lead story is only believable because the measurement stack was clean.
Same engagement, different case.
The content model + attribution infrastructure built on top of this rebuild is what drove SaVida's +9% organic-lead YoY growth through Google's AI Overviews rollout, while the industry lost 32% of its #1 clicks.
This page covers the foundation. The full engagement covers what was built on top of it.
Read the full SaVida case studyYour WordPress siteis probably slower than this was.
If your site predates 2022, there's a good chance it's carrying a database that hasn't been pruned, a template loaded with deprecated page-builder widgets, and Core Web Vitals that are quietly capping the pages you depend on to rank. A 5.8-second page doesn't just lose bounce; it loses crawlers, rankings, and attribution accuracy before any of that shows up in a report.