5 Signs Your Website Needs a Redesign (And How to Build the Business Case).
Nobody wakes up one morning and decides their website needs a redesign. It happens slowly. The complaints trickle in. The analytics start telling a story you'd rather ignore. Someone on the team says "we should really update the site" in a meeting, and everyone nods, and then nothing happens for another six months.
Meanwhile, your website is quietly working against you. It's frustrating visitors and underperforming on mobile. Accessibility checks are failing. And the whole thing makes your organization look five years behind where it actually is.
The uncomfortable part? SoftwareReviews found that 80% of website redesigns fall short of their full potential, largely because of a disconnect between what the business prioritizes and what users actually need (Source: SoftwareReviews/Info-Tech Research Group, 2023). That gap shows up in familiar ways: scope that wasn't grounded in real user behavior, content migration that nobody planned for, and governance that stayed undefined until after launch. Strategy matters more than pixels.
So before you start picking colors, make sure you're solving the right problems.
Sign 1: Your Mobile Experience Is an Afterthought
Pull up your website on your phone right now. If you have to pinch and zoom to read anything, or if the navigation is buried three taps deep, you have a problem.
Mobile devices now account for roughly 58% of all U.S. web traffic (Source: Similarweb/StatCounter, 2024), up from a fraction of that a decade ago. For associations and nonprofits, the numbers skew even higher because members and donors are checking in during commutes, between meetings, and from their couches. When a mid-sized Pennsylvania municipality issued its website redesign RFP, it reported that 57.5% of its traffic was coming from mobile devices on a site that was never designed for them.
Visitors are not patient about it, either. Google research found that 53% of mobile site visits are abandoned if pages take longer than three seconds to load (Source: Google, "The Need for Mobile Speed"). Your desktop site squeezed onto a phone screen doesn't count as a mobile experience. If your current site wasn't built mobile-first, you're losing people before they ever read a word of your content.
Quick check:
- Key pages are readable on a phone without pinch-and-zoom
- Navigation works with one thumb and does not require precision taps
- Primary calls to action are visible and tappable on small screens
- Pages load in under three seconds on a cellular connection
Sign 2: People Can't Do What They Came to Do
Your users came to your website to accomplish something, and they can't. They want to pay a bill, submit a permit, register for an event, renew a membership, or find a specific document. Instead, they get a phone number or a PDF they have to print, sign, and mail.
When a regional transit authority in the Midwest issued its redesign RFP, it cited the need to give riders real-time route information and mobile trip planning, capabilities their existing site couldn't support. A national trade association in the consumer health space needed its redesigned site to support member self-service for renewals, event registration, and resource access. A regional water utility serving 1.8 million customers was managing roughly 2,000 pages and 3,500 documents on a platform that couldn't support modern self-service transactions.
Every one of these organizations had a website. None of them had a website that could do what their users actually needed it to do. If your users are calling, emailing, or walking in to complete tasks they expected to handle online, your website is generating demand for support instead of reducing it.
Quick check:
- Top user tasks can be completed end-to-end online
- Forms work correctly on both mobile and desktop
- Users can find answers without calling or emailing for help
- Self-service capabilities match what peer organizations offer
Sign 3: Content Is Stale, Scattered, or Stuck
When your "latest news" section hasn't changed in four months, visitors notice. So do search engines when the same information lives on three different pages with three different versions. And usually, the root cause isn't laziness. It's the CMS.
Modern content management platforms like Drupal are built to give content teams direct control over their pages. But if a program manager can't update a deadline without filing a developer ticket, or if your comms team has stopped posting news because the workflow is too painful, your platform is actively preventing the people who run the organization from running the website. Publishing a simple content change should not require a code deployment.
The longer this goes unfixed, the worse it gets. Stale content erodes credibility. Duplicated content tanks your search rankings. And the eventual cleanup costs more with every month of neglect.
Quick check:
- Non-technical staff can update key pages without a developer
- Content ownership, review cadence, and archiving rules are documented
- PDFs, images, and deadlines can be swapped in minutes, not days
- Publishing does not require code deployments
Sign 4: You're Running Into Compliance Walls
The compliance picture is getting sharper, especially for government. The White House's "America by Design" initiative (August 2025) reported that only 6% of the estimated 26,000 federal websites are rated "good" for mobile performance, and 45% are not mobile-friendly at all (Source: White House fact sheet). Less than 20% use code from the U.S. Web Design System (USWDS), which was designed to help agencies build accessible, mobile-friendly sites.
Meanwhile, the DOJ's 2024 final rule under ADA Title II now formally requires state and local government web content and mobile apps to meet WCAG 2.1 Level AA standards by April 2026 or 2027, depending on entity size (Source: DOJ Final Rule, April 2024). That applies to counties, cities, school districts, transit authorities, and special districts.
Healthcare organizations are dealing with tightening HIPAA requirements around digital patient interactions. Associations face expanding member data privacy expectations. If your site architecture makes it difficult to implement security patches, meet accessibility standards, or keep pace with regulatory changes, you're not looking at a maintenance issue. You're looking at structural risk.
Quick check:
- Accessibility checks are run routinely, and issues are triaged and fixed
- Security patching is predictable and does not require heroics
- Design system and component standards are enforced consistently
- The platform supports the compliance posture your organization requires
Sign 5: The Platform Itself Is Holding You Back
Sometimes the problem isn't the design or the content. It's the technology underneath. If your site runs on an outdated CMS version, an unsupported framework, or a custom-built system that only one developer fully understands, you're building on a shaky foundation.
The real test: can your current platform support what your organization will need in the next three years? Single sign-on integration. Multilingual content. API connections to your CRM or case management system. Marketing automation. When a national association representing state workforce agencies pursued its website modernization, the need for dynamic member engagement tools and integrated data resources drove the decision more than aesthetics ever did.
Platforms like Drupal 11 on Acquia Cloud handle those requirements natively, with enterprise-grade security and FedRAMP authorization for government use. If your platform can't get there without extensive custom development, every future improvement carries a premium.
Quick check:
- Platform is supported and on a current major version
- Integration paths exist for SSO, CRM, payments, analytics, and search
- Multilingual and language-access needs can be met
- The platform roadmap aligns with the next three years of requirements
How to Build the Business Case
If you had several items across those checklists where you could not confidently check "yes," the site is probably due for modernization. Fine, so it needs work. Now you need the money.
Quantify the cost of doing nothing. If more than half of your mobile visitors are bouncing, calculate what that means in lost engagement, missed form completions, or constituent complaints routed to your call center. The numbers are usually more compelling than the complaints.
Benchmark against peers. When similar agencies or organizations have already modernized, use their results as proof points. Government consolidation efforts are routinely pursued because they reduce duplicative platforms and overhead while freeing up funding for CX and security improvements.
Frame it as risk reduction. Compliance gaps, security vulnerabilities, and accessibility failures carry real financial and legal consequences. The DOJ's WCAG 2.1 AA compliance deadlines are already here for larger entities. A redesign stops being a nice-to-have once the alternative is regulatory exposure.
You don't always need to propose the full project upfront. Sometimes the smartest move is to fund a discovery phase: audit the current state, document the gaps, produce a phased plan with clear costs. That's a much easier ask than "we need half a million dollars for a new website," and it gives leadership a concrete decision to make rather than an open-ended commitment.
At Tactis, we've consolidated more than 40 federal agency websites (roughly 300,000 pages) onto a single accessible platform and improved accessibility scores from 56% to nearly 85% in the process. The lesson that sticks with us from every one of those projects: the redesign itself is the easy part. Getting the strategy, migration, and governance right is what determines whether it actually works.
If your website is showing any of these signs, we offer a free website assessment that documents where your site stands on each of these five dimensions and maps out a realistic, phased path forward. Contact us to get started.
[1] U.S. mobile web traffic: approximately 58% of U.S. web traffic from mobile devices (2024). Source: Similarweb / StatCounter. Mobile vs. Desktop - Market Share in United States [January 2026] | Similarweb
[2] Google mobile abandonment: 53% of mobile site visits are abandoned if pages take longer than 3 seconds to load. Source: Google, "The Need for Mobile Speed" (2016). Think with Google - Marketing Research, Insights, and Trends
[3] Federal mobile performance: only 6% of ~26,000 federal websites rated "good" for mobile performance; 45% not mobile-friendly. Source: White House "America by Design" fact sheet (August 2025). Fact Sheet: President Donald J. Trump Improves our Nation Through Better Design
[3a] USWDS usage: less than 20% of federal websites use code from USWDS. Source: same White House fact sheet.
[4] DOJ ADA Title II web accessibility rule: WCAG 2.1 Level AA required for state and local government websites and mobile apps. Compliance deadlines: April 24, 2026 (entities with population 50,000+); April 26, 2027 (smaller entities and special districts). Source: DOJ Final Rule (April 24, 2024). Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments
[5] Website redesign underperformance: 80% of website redesigns fall short of their full potential. Source: SoftwareReviews / Info-Tech Research Group (July 2023). 80% of Website Redesigns Fall Short of Full Potential Due to Business-Consumer Disconnect, Says SoftwareReviews Research
*[6] Municipal mobile traffic: 57.5% mobile visitors. Source: Public website redesign RFP, mid-sized Pennsylvania municipality.
*[7] Tactis federal consolidation project: 40+ websites consolidated, ~300,000 pages migrated to unified Drupal platform, accessibility scores improved from 56.2% to 84.7%. Source: Tactis past performance records.