Existing sites & shops

Modernize, migrate, or AI-improve the site or shop you already have.

For businesses stuck on an outdated website or online store — on any common platform — we audit first, scope the work clearly, and improve what matters: performance, mobile experience, structure, checkout flows, and a supported PHP version where your stack depends on it.

Audit-first mindset

The free audit is clinical and direct: what platform and runtime signals we see, why they matter, and what attack paths are realistic — no blame for an inherited stack. You get facts first, then we scope a safe upgrade path if you want to move forward.

The report names CMS, theme, and runtime signals (e.g. PHP 7.4, EOL 28 Nov 2022), explains why unpatched stacks get compromised, and lists realistic attack paths — then optional scope for modernization.

Any stack

sites, shops, and mixed setups

PHP 8.4

HeptaLex baseline — 8.5 upgrade soon

AI + review

accelerated work, human sign-off

Scoped

from €800 under custom implementation

What we typically improve

  • Theme refresh, layout cleanup, and clearer service or product presentation
  • Mobile responsiveness, page speed, and basic SEO structure
  • Major version upgrades, module or plugin compatibility, and safer migrations
  • Planning and executing a move to a supported PHP version alongside theme or module work
  • Catalog, checkout, and operational flows for legacy e-commerce stores

Platforms we can work with

  • Sites built on WordPress software and WooCommerce-based stores
  • Stores running on PrestaShop and other legacy e-commerce setups
  • Sites on Wix and other popular site builders or CMS platforms
  • Custom or mixed stacks — scoped after an initial audit

How AI fits in

  • AI accelerates audit, content structure review, and refactoring drafts
  • Human review on every production change — no blind automation on live sites
  • Scoped delivery: fix what blocks growth, not a vague “full rebuild”
  • Clear handoff when migration or platform change is the better path
Why now

Unsupported PHP is a security risk — not just a hosting detail.

Unsupported PHP versions no longer receive security patches — PHP 7.4 reached end of life on 28 November 2022. Your site or shop stays exposed until the runtime is upgraded. Often this comes from an older agency, theme, or hosting setup — not something you should have had to track day to day. Hosting providers may also force a move, which can break themes or modules if the upgrade is not planned.

  • No security updates means known vulnerabilities stay unpatched on the server.
  • Many legacy WordPress, PrestaShop, and custom PHP shops we audit still run PHP 7.4 or older — usually because maintenance was never part of the original delivery.
  • We help you plan and execute the upgrade path — we are not a certified security auditor, but you get a clear picture of the situation and practical next steps.
Where we are

HeptaLex runs on supported PHP — and stays current on purpose.

PHP is the engine behind many websites and shops — the software on the server that makes pages load, forms work, and checkouts run. Version numbers are like updates on your phone: supported releases still get security fixes and keep working with modern hosting.

HeptaLex runs on PHP 8.4 today — actively maintained and supported. We are upgrading to PHP 8.5 very soon so our own platform stays on a safe, modern baseline.

If a site still runs PHP 7.4 — often inherited from an older setup — it uses a runtime that has not received security patches since 28 November 2022 (EOL), like an old phone OS that no longer gets security updates. We build and upgrade client work on supported versions so the stack does not get left behind.

Our job is to translate the technical picture into decisions you can evaluate. We stay current on supported PHP ourselves and scope a safe path for your site or shop.

Execution path
01

Audit

Clinical read of the live stack: CMS/platform, theme signals, PHP/runtime markers, plugin surface, and conversion blockers — what is there, why it matters, what an attacker can realistically do. No judgment for inherited setups.

02

Scope

Technical details translated into practical decisions you can weigh — we propose the narrowest path: supported runtime, in-place modernization, partial migration, or targeted rebuild.

03

Deliver

We implement, test on staging where possible, and roll out with human review on production changes.

Good fit if

  • Your current site or shop works, but feels slow, dated, or hard to maintain
  • The stack runs on an unsupported PHP version — hosting may force an upgrade, or the site stays exposed until the runtime is updated
  • You need a major version upgrade without breaking modules, themes, or checkout
  • You want AI-assisted improvement with a team that reviews before go-live

Anonymous examples

  • One professional services site — clearer structure, faster mobile, better inquiry flow
  • One retail e-commerce store — version upgrade, theme cleanup, and checkout reliability
  • No client names published; scope always starts from your actual setup

WordPress, WooCommerce, PrestaShop, and Wix are trademarks of their respective owners. HeptaLex is an independent service provider and is not affiliated with or endorsed by the WordPress Foundation, Automattic, PrestaShop, Wix, or any other platform mentioned on this page.