A cleanup and modernization of the Huntington's Disease Foundation site on the new host — a dramatically lighter database, a security exposure closed, screen-reader accessibility improved, and the site's most recent content carried across, with its look untouched.
Because recent updates had been made to the live site, the foundation's most current content — including new 2026 posts, press releases and media — was captured and merged onto the cleaned version, so nothing recent was lost.
The current live content (all pages, posts, and 311 recently-added media files) was brought across and verified, then the cleanup was applied on top. All 364 form submissions were preserved.
The database had accumulated debris that slows every page load and backup — none of it actual content.
Removed years of page-builder revision history, expired temporary data, and stale security-scan caches — with every page and form submission preserved.
The site still carried ManageWP remote administrative access tied to the previous developer's account — a standing security exposure. It has been removed, along with redundant caching and backup plugins.
A light accessibility pass focused purely on screen-reader usability, with no change to appearance.
Social-media and profile links (including the Candid / GuideStar transparency seal) that previously had no readable label now announce themselves to screen readers. For a nonprofit, this reduces exposure to accessibility-related legal claims — a far more real risk than most realize, and a more relevant one here than cookie compliance.
We reviewed whether a cookie-consent banner was needed. As a nonprofit that sells no products and shares no personal data, the site falls outside California's CCPA/CPRA (which exempts nonprofits and applies only above high revenue/data thresholds). Rather than add an unnecessary banner, effort went to the accessibility work above — the compliance area that genuinely matters for a nonprofit site.
The staging copy was open to Google (a duplicate-content risk to the live site) and has been switched to no-index. This must be switched back on at go-live — flagged so it can't be missed.