A professional site that takes three seconds too long to load on mobile is a contact form that no one fills out. We see it in practice: most redesigns start after an operational observation, not after a technological watch. The trigger comes from a rising bounce rate, an unmanageable back office, or a regulatory obligation that arises.
Web accessibility and the European Accessibility Act: the constraint that changes the specifications
Since June 28, 2025, the European Accessibility Act requires private companies selling digital services to consumers in the European Union to make their journeys accessible. We are no longer just talking about public pages: e-commerce, booking, payment, and customer support tunnels are included in the scope.
In practical terms, this means that a website created today without considering WCAG 2.2 accumulates a technical debt as soon as it goes live. National authorities are intensifying checks, and dedicated reporting channels are appearing in several European countries to allow consumers to report shortcomings.
On the ground, we see redesign projects where the accessibility budget represents a significant portion of the total, where it was almost nonexistent two years ago. Ignoring this item exposes one to a second corrective redesign in the short term.
To assess the extent of the technical work involved in achieving compliance coupled with a graphic redesign, one can consult the Digiterio website in detail, which outlines web design methodologies adapted to these requirements.
CMS choice and technical architecture: WordPress, headless, or custom
The choice of CMS determines the maintainability of the site over several years. We encounter three recurring scenarios.
WordPress with page builder
This is the most common scenario for SMEs. The plugin ecosystem covers most common functionalities (forms, SEO, caching). The main risk remains the accumulation of poorly maintained plugins that degrade performance and create security vulnerabilities.
Headless architecture (decoupled CMS)
This separates the back office (content management) from the front end (display). This approach is suitable for companies that publish content across multiple channels (website, mobile app, kiosks). It requires front-end development skills in-house or with the provider, and the initial cost is higher.
Custom development
This is reserved for projects with specific business functionalities that no CMS covers natively. Custom solutions offer total control, but maintenance relies entirely on the technical team. If this team changes, documentation becomes critical.
The right reflex: list the functionalities actually used on the current site before making a choice. It is often observed that half of the functionalities planned in a specifications document are never utilized after going live.
Website redesign without harming SEO: the checkpoints
A poorly managed redesign in terms of SEO can lead to the loss of organic traffic built over several years in just a few weeks. The 301 redirect plan is the first deliverable to request, not the last.
- Export the complete list of indexed URLs before the redesign (via Search Console or a Screaming Frog crawl), then map each old URL to its new destination.
- Keep the performing title and meta description tags. Rewrite only those with a low click-through rate.
- Check that the internal linking remains coherent after the change in structure: broken internal links are the primary cause of position loss post-redesign.
- Submit the new XML sitemap as soon as it goes live and monitor indexing in the weeks that follow.
Feedback varies on the duration of traffic stabilization after a redesign, but a floating period of a few weeks is generally observed before positions consolidate.
Budget and objectives of creating a professional website: what really affects the bill
The price of a professional website depends less on the number of pages than on three factors rarely detailed in quotes.
The level of integration with existing business tools (CRM, ERP, billing tool) is the first complexity factor. Connecting a form to a CRM via an API requires specific development, and each connector adds testing time.
The second factor is content production. A ten-page site with written texts, professional photos, and short videos costs more than a thirty-page site fed with stock content. Content is often the most underestimated item in web creation projects.
The third factor concerns compliance. Accessibility (WCAG 2.2), GDPR (cookie banner, compliant forms, privacy policy), legal notices: these elements require design time and sometimes an external audit. Ignoring them during the project phase means having to catch up after going live, at a higher cost.
User-centered design: test before developing
This is evident in many projects: the design is validated internally by executives, without confrontation with real users. The result is a site that pleases the management committee but does not convert.
Two practices significantly change the game:
- User testing on an interactive mockup (clickable Figma prototype), conducted with five to eight people representative of the target, before development. Five testers are sufficient to identify the majority of usability issues.
- Analyzing user journeys on the existing site (heat maps, session recordings) to identify real friction points before designing the new structure.
Redesigning without usage data is like rebuilding blindly. The design must respond to observed behaviors, not to the intuitions of the project owner.
The creation or redesign of a professional website in 2024-2025 hinges on concrete trade-offs: regulatory compliance, technical architecture choice, SEO preservation, and content production. Each neglected item upstream incurs costs in corrections after going live, often more expensive than if it had been integrated from the start.
