Healthcare sites rebuilt off WordPress

The starting point

Eight healthcare provider websites ran on WordPress, each with between 1,000 and 6,000 pages. Page layouts were built in Elementor, structured content lived in Advanced Custom Fields (ACF), and large batches of pages were created and updated with WP All Import.

Every site also carried a heavy marketing and compliance stack. On mobile, PageSpeed Insights performance scores sat between 65 and 75; on desktop, between 80 and 95. With that many pages and that many scripts, tuning the existing WordPress builds had stopped paying off.

What had to keep working

A faster site that loses calls, leads or consent records is not an improvement. These had to work on the new build from day one:

• CallTrackingMetrics for call tracking
• Google Tag Manager and Google Analytics 4 for tags and analytics
• Usercentrics for cookie consent
• Microsoft Clarity for session recordings and heatmaps
• VWO for A/B testing
• Jotform HIPAA forms for patient-facing forms
• A custom chat widget
• A custom HIPAA-compliant endpoint that creates leads automatically in whichever CRM the client uses

What we built

Each site was rebuilt as code written in Cursor. Before generating pages, we chose and wrote down the guardrails for each codebase: how the code is organized, and the quality bar every change has to meet. Cursor works inside those rules, so page 5,000 is built the same way as page one.

ACF and WP All Import were the two tools the content teams relied on most, so each got a custom replacement that lives inside the codebase: structured content fields in place of ACF, and bulk page imports in place of WP All Import. Because they live in the project, maintaining thousands of pages happens in Cursor, which is faster and more accurate than editing one page at a time in the WordPress admin.

Results

• Speed: mobile PageSpeed scores rose from 65–75 to 92–98, and desktop scores from 80–95 to 92–98. Each range covers all eight sites.
• Core Web Vitals: the old sites weren’t passing. About four days after launch, Search Console showed the new builds passing on both mobile and desktop.
• Traffic and leads: held steady or grew after launch. The figures belong to the clients, so we don’t publish them.
• Tracking: the full stack above carried over to the new builds.

PageSpeed scores are lab measurements from a single test run. Core Web Vitals are a separate pass or fail check based on real visitors, which is why we report both.

Who owns the result

Each client has full access to its finished codebase. Their team can keep updating the site in Cursor, or hand it to another developer. Nothing is locked to us—see code ownership for how that independence works after delivery.

For the ninth site in the same rebuild program—the named 48V Products ecommerce migration—and how PunkSolid dogfoods the same gates on its own twelve-site network, see those case studies on this hub.