LWS WordPress: pricing, AI, backups and migration

Who LWS may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

French; separate country websites and multilingual help

Control panel

LWS Panel documented in French; language setting documented, not tested

Support

French support; tickets 7 days a week from 7 to 22 and hotline Monday–Friday from 9 to 19 according to the current guide

LWS WordPress: French shared hosting with management tools

LWS markets shared hosting for WordPress around three plans: Perso, Starter and Performance. The catalog consulted on 3 November 2026 combines storage, databases, email, a domain for one year and WP Manager. The word managed appears in the presentation, but examine the operations actually supplied rather than assuming editorial maintenance or custom development.

This profile relies on the public offer pages and provider guides. No account was created, payment made or site migrated or restored to evaluate it. Customer reviews, promotional average response times and speed promises therefore do not become test results. The proposed choice concerns documented features and concrete contractual constraints.

For a French reader, the appeal is a company, support and servers advertised in France, with instructions available in French. The main tradeoff concerns project count, the amount of data actually occupied and expected independence in recovering a site. A large included volume does not guarantee that all operations on that volume are free.

Promotional prices and the budget after the first year

Perso displays 1.49 € per month before tax for the first year, with 3.99 € as the current normal price. Starter displays 3.49 € then 5.99 €, and Performance 6.99 € then 11.99 €. The discount is explicitly limited to the first year. These figures are a snapshot of the catalog, not a guarantee of unchanging prices in future years.

To compare an annual budget, twelve indicative monthly amounts represent 17.88 € before tax then 47.88 € for Perso, 41.88 € then 71.88 € for Starter and 83.88 € then 143.88 € for Performance. These calculations exclude options and domain renewals. They reveal the recurring cost but do not prove that the provider accepts month-by-month payment.

Before paying, select the exact product and record the prepaid duration, initial total, normal amount, taxes and options. Keep this summary with the invoice. The page’s no-commitment wording must not be turned into an automatic refund of a period already paid. Confirm the cycle offered in the quote; no order was simulated with customer details.

VAT, free domain and costs outside the bundle

The French site shows prices before tax and VAT-inclusive equivalents: 1.79 €, 4.19 € and 8.39 € for the three promotions. The tax guide explains that the system uses billing details to determine tax. For a customer in France, it states VAT of 20%. Customers elsewhere must check their own quote with appropriate tax information.

Perso and Starter include a free domain for one year; Performance advertises two. Eligible extensions, registration or transfer, and renewal must be read in the order. A domain free in the first year may add a recurring line from the next year. Keeping it with another registrar is another possible arrangement, with DNS to configure.

Add any theme licenses, external services and the desired restoration level to the calculation. Free software versions do not automatically grant updates and support for a commercial edition. Compare the cost needed for your operational site rather than an entry price to which several essential services must be added.

Perso, Starter and Performance: sizing multiple sites

Perso advertises 100 GB of storage, three hostable sites, one MySQL database and five email addresses. Starter increases to 200 GB, ten sites, ten databases and twenty-five addresses. Performance offers 300 GB, fifty sites, fifty databases and one hundred addresses. Database count deserves separate attention from site count: three independent WordPress installations on Perso should not be assumed to have their own included database each.

The grid limits each database to 1 GB on all three plans and advertises 8, 20 and 30 MySQL connections respectively. It also sets one, two and three million inodes, which count files and directories. These limits may matter before total storage. For multiple projects, map installations, domains and databases; WordPress Multisite and separate installations are managed differently. The advertised site count does not guarantee isolation for each client.

Traffic is advertised as unlimited while physical resources remain shared. Descriptions of standard, doubled or tripled performance do not provide a measured simultaneous-visitor capacity here. For a store or dynamic site, start from actual database, PHP and media usage; request the plan’s technical limits if they determine your choice.

France, panel and languages: what location establishes

The WordPress page places its servers and technicians in France. The general data-center presentation mentions Adista and Equinix among others; this does not assign a specific address to a Perso, Starter or Performance account. The advertised country for the offer is France, with no established free choice of center here. Backup or third-party service location must be examined separately if it is a project condition.

The selected service uses LWS Panel and WP Manager. LWS also sells cPanel products, VPSs and other creation tools: their menus and quotas should not be copied into the Perso, Starter or Performance profile. Migration between ranges may require data restoration and change available tools.

The website and help are available in French; an account-language setting is documented. The panel has not been tested. For a team, distinguish WordPress permissions from those of the client account controlling domains and billing. French hosting also does not determine where data sent by payment services, analytics or AI features goes.

Workflow for installing and administering a first WordPress site

The workflow without an additional plugin suits a new site whose owner has the LWS account. Log into LWS Panel, open the intended hosting and locate WP Manager. For a new installation, use the WordPress installation action and verify the domain and target directory before confirming. An occupied location should be backed up rather than treated as empty space.

After installation, the detected-sites list lets you open management and administration for the relevant WordPress site. Check the title, HTTPS address, administrator access and a published page. Also verify database creation and its correspondence with the site. The expected result is an installation accessible at the correct domain, with access recoverable by its owner.

To undo a trial, delete only the test installation after identifying its files and database. Do not cancel the entire bundle to remove a draft. On an existing site, theme, plugin and user-management tools let you intervene from the panel; they do not replace a change inventory and restorable copy before an important action.

AI: distinguish site creation from technical actions

The AI-assisted WordPress builder starts with business information, a description, images and style choices. It helps build structure and initial content. This workflow differs from WP Manager’s AI Assistant, which interprets administration requests and may propose actions on site components or diagnostics. SiteBuilder Pro is another editor again, separate from WordPress.

The current WP Manager guide describes confirmation before sensitive actions. It also provides for consent to AI features: declining leaves ordinary management tools available. A more advanced chatbot is presented as being in testing. This prospect should not be turned into a feature already guaranteed for every account.

No numerical generation quota or complete detail of models and external processing was established in the selected pages. Check these points before using personal data or confidential content. For a change, read the proposed action, keep a copy and check the result. AI facilitates an operation; it guarantees neither textual accuracy nor plugin compatibility.

Updates, staging and remaining responsibilities

The catalog advertises automatic updates, and WP Manager offers core, theme and plugin management. The guide also describes snapshots and staging in the Backups page, with a maximum of three staging environments per site. These tools provide maintenance capabilities; their presence does not prove that a technician will fix every incompatibility within the bundle price.

The offer advertises a Let’s Encrypt certificate, application firewall, antimalware scan and network protection against denial-of-service attacks. These are advertised features, not a guarantee against every intrusion. After installation, verify HTTPS and administrator accounts; maintain components and retain individual access even when the provider protects its infrastructure.

To test a change, open WordPress in WP Manager, create a copy or rollback point using the available features and work on staging. Disable real emails, payments and external synchronization. Change one component at a time, then check appearance, login and business functions before any production deployment.

The expected result is a change validated against the site’s user journeys, with a recoverable previous state. If the test fails, discard the copy or return to its snapshot without overwriting production. Deploying the copy may replace recent data: a store must separately handle orders arriving during testing. Backups and the deployment schedule must remain consistent.

Backups: one month at the basic level, three months with an option

The detailed policy documents daily copies of files, MySQL databases and email for the relevant LWS Panel shared hosting services. The latest seven daily copies are kept, followed by weekly recovery points. For files and databases, the basic level provides one month and approximately ten versions; Business advertises three months and approximately nineteen versions.

Email requires a further distinction: the levels guide provides for paid intervention to restore ordinary mailboxes included with shared hosting. It reserves included email restoration for Mail Pro services or the Support Business option within the described periods. An automatic mailbox copy therefore does not establish access to free self-service restoration.

The decisive limit is size: the policy reserves basic self-service restoration for hosting accounts of no more than 20 GB. Above that, backups remain advertised but a managed intervention is required; according to the policy, the Business Option allows self-service without this limit. The levels guide lists a Backup Search service at 49 € before tax when restoration requires this intervention.

The commercial page mentions free recovery and archiving over several months. Use the terms specific to the data and option without promising three free months for every plan. The options guide lists Business at 5.99 € per month before tax; another public panel grid, however, shows a promotional 1.49 € and a crossed-out 5 €. These references differ: have the applicable price, duration and renewal specified in the quote. The 49 € before-tax charge for a one-off search is not the Business subscription.

An external copy remains useful before an important operation or contract end. Keep files and a database export together, check that media are present and retain the credentials needed for recovery. The existence of an older provider recovery point does not guarantee that the desired content is complete.

Workflow for downloading or restoring files

This workflow suits an owner of compatible shared hosting whose desired recovery point remains accessible. In LWS Panel, open the hosting, then Fichiers, Sauvegardes / Restaurations and the Sauvegardes Web tab. Choose the desired date. Downloading produces a copy to retrieve once the link is ready; this action does not put files back into production.

To restore, first identify the scope: all hosting, a specific file or folder, or an additional domain. Export the current state before overwriting, then launch only the appropriate action and monitor progress. Files do not return the database to the same date. In the Sauvegardes MySQL tab, choose the correct database and a consistent recovery point, then Télécharger la base to retain a copy. Restaurer la base is a separate action replacing current data; the Historique tab tracks progress.

The expected result is recovery of the desired data on the relevant pages and functions. If incorrect, the export taken before the operation provides the rollback point, with its associated database and recent writes to preserve. Above 20 GB, the guide directs users to Business or an intervention. Retrieve generated archives promptly: it also warns that files larger than 500 MB left on FTP storage may be deleted automatically. No restoration test was performed here.

Free migration: eligible volumes and site counts

The migration guide covers a site hosted elsewhere and a new LWS product ordered less than thirty days previously. It accepts several common CMSs including WordPress but specifically excludes WordPress.com, nonstandard variants such as BedRock, Drupal, some frameworks and Python, Ruby or Node.js applications. An application compatible with a server is therefore not necessarily eligible for this free service.

The scope advertises one site and two mailboxes for Perso, three sites and five mailboxes for Starter, and five sites and ten mailboxes for Performance. Total site volume to transfer is capped at 20 GB, and each mailbox at 10 GB. Paid interventions apply beyond the scope. Capacity for fifty sites in Performance therefore does not mean fifty free migrations.

Exchange and Google Workspace email are outside this standard transfer. Before choosing the bundle for migration, measure data and list available access. Clarify the accepted scope before requesting the service, then keep the old hosting active during verification. The guide does not constitute a completed transfer for your own installation.

Switchover workflow and returning to the old hosting

1. For assisted migration, prepare source access and open the request through the new hosting’s support. Specify sites, databases, mailboxes and volumes. Wait for scope confirmation and the destination copy, then verify the site before changing DNS. The documentation does not remove the need to supply a functioning source and usable access.
2. On the verification copy, check pages, images, administration and forms while disabling sends, payments and synchronized tasks. For a store, set a short freeze period or final synchronization to avoid losing orders created during copying. Retain the initial DNS zone and distinguish web records from email records.
3. After switching, check HTTPS and relevant functions at the destination, then retain the source until validation. If the site must roll back, restoring old DNS will not merge new writes. Retrieve orders and messages created in the meantime before any return. The goal is a complete destination with a documented schedule and recovery process.

French support: tickets and phone have different hours

Current documentation advertises technical ticket responses seven days a week from 7 to 22. The hotline is listed Monday to Friday from 9 to 19. The general claim of support 7 days a week should therefore not become continuous phone assistance. The AI chatbot is another channel, separate from a technician’s intervention.

The guide recommends a ticket from the client area for a technical question. Select the relevant hosting and appropriate category, then describe the time, address and exact error. Attach useful evidence without exposing secrets. A phone call may itself lead to a ticket being opened for specialist investigation.

Average times highlighted in the catalog are neither measurements made for this profile nor universal resolution commitments. Payment, contact-detail or refund questions belong to the sales department. For an intervention that overwrites data, define who may authorize it and which point should be restored. Actual response quality has not been evaluated through contact.

Automatic renewal, cancellation and guarantee

In LWS Panel, the renewal guide directs users to open the customer-ID menu, then Auto-renouvellement. The table shows services, expiration dates and payment methods. Selecting Aucun paiement suspends subsequent automatic charges according to the documentation. A payment may be initiated five days before expiry, or fifteen days beforehand for SEPA: check before that deadline.

Disabling this payment does not immediately delete the service or refund an invoice. The cancellation workflow uses the account menu, Résiliation, then the corresponding request. Verify the chosen service and consequences before confirming. Immediate deletion of a domain is different from ending hosting at expiry.

The commercial guarantee is advertised for thirty days for eligible hosting. The guide notably provides for deduction of the associated domain’s price; do not promise a full basket refund. In the account menu, the Remboursement action allows a request. Check its amount and how options are treated before deleting the product. Retain the accepted terms and a copy of all required data; disabling renewal does not submit this request for you.

Which projects suit LWS, and when to examine another route

Perso can be considered for a small brochure site or first blog when its databases and resources suffice. Starter is easier to assess for multiple independent installations thanks to its ten advertised databases. Performance expands quotas for a portfolio of sites, but actual capacity must still match simultaneous usage, not simply site count.

Two practical routes emerge. For a simple new site, installation in WP Manager or the AI WordPress builder reduces initial handling; review content and retain access. For an eligible existing site, assisted migration avoids manual copying, provided the source is prepared and the destination checked before DNS changes. In both cases, a consistent export supplies the rollback.

A project requiring strong isolation between clients, nighttime phone assistance or an application excluded from migration should compare another range or provider. Before deciding, assemble the normal annual budget, database limits and restoration cost suited to occupied volume. These parameters produce an actionable choice; no overall score or unmeasured performance recommendation is assigned.