A showcase site delivered on a standard CMS with a premium theme is not a custom solution. Customization begins where the template ends: business logic integrated into the front end, interconnection with an ERP or billing tool, user journeys designed based on actual browsing data. For a small to medium-sized enterprise (SME), the difference is measured in conversion rates and maintenance costs over three years, not in the aesthetics of the homepage.
Technical architecture of an SME site: stack, performance, and hidden debt
The choice of the technical foundation determines the entire lifecycle of the site. A monolithic CMS (WordPress, Joomla) requires regular updates of plugins, some of which introduce critical vulnerabilities with each version upgrade. On an e-commerce site, a payment plugin that has been outdated for six months poses a risk of non-compliance with PCI-DSS.
We recommend that SMEs managing a product catalog or a customer area separate the front end from the back end via a headless architecture. The CMS remains the administration interface, but rendering is handled by a JavaScript framework (Next.js, Nuxt) connected via API. The benefits are twofold: loading times reduced by two or three on mobile, and complete independence between back-office updates and public display.
Technical debt often appears after eighteen months. A site built on a visual page builder accumulates unnecessary CSS, redundant database queries, and unverified JavaScript dependencies. For SMEs looking to discover the services of Simpler Computing, the challenge is precisely to obtain a maintainable foundation without hiring a full-time developer.
Web accessibility and the European Accessibility Act: what SMEs need to check
Digital accessibility is a legal obligation, not a UX bonus. Since June 28, 2025, the European Accessibility Act covers e-commerce services, banking services, transport, telecommunications, audiovisual media, and digital books. Companies exceeding the microenterprise threshold (fewer than 10 employees and at most 2 million euros in turnover or total balance sheet) are affected in these sectors.
Decree No. 2026-816 of August 24, 2026, which came into effect on August 27, aligned certain French rules with the dates and content of exemptions provided by European regulations. Specifically, an SME selling online must verify the compliance of the entire purchasing journey: forms, validation buttons, payment tunnel, order confirmations.
A common mistake is to limit the audit to color contrast and font size. Obligations also cover keyboard navigation, textual alternatives for informative images, and the publication of an accessibility statement compliant with the RGAA. On a custom site, these constraints are addressed from the mockup phase. On a template site, they often require a partial redesign of the theme.
Priority checkpoints for an SME e-commerce site
- Ensure that each form field has an explicit label associated with the for/id attribute, rather than just a placeholder that disappears upon input.
- Ensure that the ordering process, from product selection to payment confirmation, remains operable without a mouse, using only the keyboard and a screen reader.
- Publish an accessibility statement page mentioning the reference used (RGAA 4.1 or WCAG 2.2 level AA), the date of the last audit, and a contact method to report a defect.
Security and hosting: two underestimated items in SME budgets
A TLS certificate and shared hosting are not enough to secure a site that collects personal data or processes payments. French SMEs are facing increasing pressure regarding cyberattacks, and a website remains a preferred entry vector when it relies on outdated components.
We observe that the majority of SMEs confuse hosting with managed services. A host provides infrastructure. Managed services include monitoring server logs, applying security updates within 48 hours, and restoring from tested backups. Without a managed services contract, the responsibility for maintenance falls on the client, who often lacks the time or expertise to handle it.
Technical criteria for suitable hosting
- Hosting on a virtual dedicated server (VPS) or containerized, with resource isolation, rather than shared hosting where a neighboring traffic spike degrades performance.
- Daily automatic backups with retention of at least 30 days, stored in a data center geographically distinct from the main server.
- Application firewall (WAF) configured to filter SQL injections and XSS attacks, updated based on recent threat signatures.
- Real-time monitoring with email or webhook alerts in case of response times exceeding a contractually defined threshold.
Integrated SEO strategy from design: structure, content, and linking
The natural referencing of an SME site cannot be resolved by adding an SEO plugin after launch. The structure of URLs, semantic markup, and content hierarchy are defined during the design phase, not during the corrective phase.
A custom site allows control over the HTML output sent to search engines, independent of the front-end framework. Structured data (schema.org), canonical tags, fine management of crawl budget via the robots.txt file and XML sitemap: these elements are native in a controlled architecture, whereas they depend on third-party plugins (and their updates) on a standard CMS.
Content remains the main lever. An SME that regularly publishes pages with high search intent (product guides, technical FAQs, sector-specific use cases) builds thematic authority that technical optimization alone cannot replace. The internal linking between these pages should follow a semantic cocoon logic, not just a simple addition of links in the footer.
The choice of a custom web solution commits an SME for several years. It is better to invest in a clean and documented technical foundation than to patch a poorly adapted template. Regulatory accessibility, application security, and natural referencing are not options to be activated later: they are structuring constraints that dictate the architecture from the first wireframe.
