Home
The first page people see. I measure it empty, then with a basket in progress: to your server, these are two different pages.
Online shop · WooCommerce, PrestaShop, Shopify
“My online shop is slow, I'm losing sales at the basket.”
I measure the pages that carry your revenue: home, category, product page, basket, checkout. Then I fix them, one change at a time, with the rollback ready.
Book my free scoping call
€890 excl. VAT · the Scan of your shop, with the firm price of the project
Every gain measured in production
Rollback ready for every change
What I measure
The five pages where the sale is won or lost
On WooCommerce, PrestaShop or Shopify, I measure the response time of the pages that take a visitor all the way to payment. Each fix is measured before and after, in production. Whatever gains nothing is removed.
Category
Filters, sorting, thumbnails: the page where customers compare, and the one that gets heavier with every plugin added.
Product page
The main photo, the price, the add button. I look for whatever delays them appearing.
Basket
Built for each customer, it partly escapes the cache. That's often where the time goes.
Checkout
The order funnel, right through to confirmation. The last page before the sale has to respond without keeping anyone waiting.
The online shop Scan
11 checks, including the ones an automated speed test can't see
A free speed test reads a single address, once, with an empty cache. It never presents itself as a crawler and doesn't compare the displayed price with the price declared to search engines. The Scan covers those blind spots, read-only: no order placed, no form sent.
- What delays the main image: the server, or a theme script. Changing host doesn't fix a script.
- The real weight of each page, and the share of code repeated twice.
- Caching as Google sees it: when it comes back, does your server send the whole page again, or “nothing has changed”?
- One single address for your shop: with or without www, over http or https, only one responds, the others point to it.
- Your language versions, also declared where free tools don't look, and every announced address checked.
- Product pages a machine can read: name, price, availability, image, and the declared price equal to the displayed price.
- Search crawlers from Google and ChatGPT: allowed in, or turned away by your firewall.
- Working files published by mistake (backups, logs), spotted without ever being opened.
- Your customer reviews: verifiable, or anonymous in the eyes of a search engine.
- Local search: a page that answers “your business, your town”.
- Google Search Console: connected, with the sitemap submitted and read.
How I fix
One change at a time, with production as the only judge
- 1A plan in batches
The Scan sorts the fixes into batches. For each batch, you know what it touches and what it should gain. - 2Each change deployed on its own
It's tried on a copy of the site, then deployed on its own in production. The rollback is ready before deployment. - 3Measured with and without
I measure the page with the change, then without, under the same conditions. Whatever gains nothing is removed. - 4Production decides
The test site never decides: it has neither your visitors, nor your baskets, nor your load.
+113 ms
On a live online shop, a change that promised −247 ms on the test site gave +113 ms in production. It was removed within 4 minutes. That's why only the measurement in production decides.
What it delivered
On a live online shop, in August 2026
−39%
Basket response time: −39%. Order funnel: −34%. The home page with a basket in progress went from 1.022 s to 0.130 s. 4 batches deployed, 4 batches kept: each one was measured in production before being kept.
What comes next
Once the shop is fast, what keeps it that way
My own testing ground is my online shop: nearly 100,000 visitors a month.
Security
I look for backdoors in the database and on disk, I renew the secrets (passwords, access keys) and I check every administrator account. After that, 7 security checks run every night, and you're only alerted when something changes.
Order e-mails
Confirmation, dispatch, invoice: the e-mails your customer receives, redone and easy to read. On a live online shop: 14 order e-mails redone, in French and English, deliverability rated 9.8 out of 10.
Till and website stock
Till stock and website stock aligned every night: a one-off item no longer sells twice. On my online shop, this double-sale safeguard has been active since 7 September 2026.
Price monitoring
Your competitors' prices checked at the frequency you choose. On my online shop, every week, for more than a year. See price monitoring
Product pages in bulk
Product pages created in bulk from your file, with no re-typing. On my online shop, 400 products go live every month with no data entry. See automation
The price
One price to know before you start
The Scan of your shop costs €890 excl. VAT. It hands you the costed findings, the batch plan and the firm price of the project, valid for 60 days. You then decide, batch by batch, on your own figures. If there's nothing worth fixing, I'll tell you.
Online shop Scan
€890 excl. VAT
The five pages that carry your revenue measured, the 11 checks, the batch plan
Delivered within 5 working days of receiving access. The project batches: firm price handed to you with the Scan, valid for 60 days, 30% deposit on order. The Pilot is an optional monthly plan, cancellable with 30 days' notice; its price is handed to you with the price of the project.
Book my scoping callThe scoping call, 30 minutes, is free. See the Scan, Sprint, Pilot method
Frequently asked questions
What I'm asked before signing
My site already has a caching plugin. What's the point?
A caching plugin serves pages that have already been built faster. The basket and the checkout are built for each customer, and that's where the sale happens. I measure those pages, in production. I also measure what your plugin actually does: some settings slow the site down instead of speeding it up. Each setting stays if it gains, and goes if it gains nothing.
Do you work on my live site?
Yes, because that's where your customers buy. Each change is first tried on a copy of your site, then deployed on its own in production, with the rollback ready before deployment. I let you know before each deployment, and I measure the page with and without the change.
How long before I see a result?
The Scan is delivered within 5 working days of receiving access, with the costed findings, the batch plan and the firm price of the project, valid for 60 days. After that, each batch is measured as soon as it's deployed: you see its gain, or its lack of gain, without waiting for the end of the project. After delivery, 30 days of fine-tuning are included.
What if a fix makes the site worse?
It's removed. Each change goes out on its own, with its rollback ready, and it's measured before and after. On a live online shop, a change that promised −247 ms on the test site gave +113 ms in production: it was removed within 4 minutes. That's why only the measurement in production decides.
Which platforms?
WooCommerce, PrestaShop and Shopify. On WooCommerce and PrestaShop, I work on the server, the theme and the plugins. On Shopify, hosting is handled by Shopify: I work on the theme, the apps and the pages that carry your revenue. Another platform? Let's talk about it on the scoping call.
How many sales is your basket letting slip?
In 30 minutes on the phone, free of charge, we look together at the pages that carry your revenue, and I tell you whether a Scan is worth it.
Book my slot