SEO Service · Speed
A slow store does not throw errors. Orders simply do not complete. I find what is costing you those seconds — and fix it in the theme, the queries and the asset pipeline, not by installing another plugin on top.
Measured before and after, on the same connection, on your own URLs.
Core Web Vitals
Field data · 28-day rolling · mobileThe cost
Nothing in your dashboard reports this. Visitors leave during the wait, the cart is abandoned before payment clears, and the loss shows up months later as a conversion rate that has been sliding without explanation.
Speed is also a confirmed Google ranking signal through Core Web Vitals — a modest one, but the conversion cost is the part that shows up in your bank account. The causes are almost always the same handful of things, and none of them are visible from the WordPress admin.
Scope
Not a caching plugin installed and an invoice sent. These are the layers where the seconds genuinely live.
01
Page caching, object caching, and the hosting configuration that decides how fast the first byte arrives.
02
AVIF and WebP conversion, correct sizing per breakpoint, lazy loading below the fold, and explicit dimensions so nothing shifts.
03
Critical CSS inlined, the rest deferred, unused code removed per template, and scripts loaded only where they are needed.
04
Self-hosted, preloaded, subset to the characters you use, with the swap behaviour set so text is never invisible.
05
Autoloaded options, orphaned metadata, expired transients, and the slow queries that WooCommerce accumulates over years.
06
Cart fragments, uncached AJAX calls and third-party scripts that fire exactly when someone is ready to pay.
07
Measuring what each plugin costs in load time and queries, then replacing or removing the ones that are not worth it.
08
Reserved space for images, ads, embeds and banners, so the page stops jumping while it loads.
09
Assets served close to the visitor, with cache rules that do not break your cart or logged-in sessions.
10
Analytics, chat widgets, pixels and heatmaps deferred or removed. Often the single largest win, and the one nobody audits.
Deliverables
Speed work is either provable or it is marketing. Every engagement ends with the same two measurements, taken the same way.
Lab and field data, same URLs, same connection, dated screenshots. Nothing modelled or estimated.
Exactly which request holds up the render, and what it was replaced with. The reasoning, not just the score.
Built on a staging copy, tested through checkout, then pushed live with a rollback ready.
What will slow it down again — the plugin, the theme update, the new tracking pixel — so gains do not quietly erode.
How it works
Speed work changes how assets load. Done carelessly on a live site, it breaks checkout. It is built on a copy and tested end to end before it goes anywhere near your customers.
01
Lab and field baselines on your key templates: home, category, product, cart, checkout.
Day one
02
Every change made on a copy, with a full backup taken before anything starts.
Days two to four
03
Add to cart, checkout, payment and confirmation email tested end to end before deployment.
Day five
04
Pushed live with rollback ready, then measured again on the same scale for the report.
Day six
Packages
Every one is a one-off diagnosis with no commitment — the report is yours whether or not you continue. The fee is credited in full against your first month if you go on to a plan.
Small site
€39one-off
For brochure and service sites where a couple of templates carry everything.
Up to 10 pages · 48 hours
Written report. No video or call.
Medium site
€69one-off
The full diagnosis, with the reasoning explained rather than just listed.
11 to 20 pages · 3 working days
Best fit for most WordPress sites.
Large site
€89one-off
For bigger sites and stores, where cart and checkout are where the money leaks.
21 pages and up · 5 working days
Catalogues over 3,000 products quoted after a look.
The audit is deliberately a diagnosis — you can hand it to any developer. If you would rather I implement it, that is the €149 monthly plan: the fixes are made on staging, tested through checkout, deployed, then measured again on the same scale. Your audit fee comes off the first month, so the diagnosis effectively costs nothing.
The other five
Speed removes a barrier. Whether Google can find and understand the page is a different problem.
Crawling, indexation and the architecture underneath everything.
Learn more →Making each page the clearest answer to the query it targets.
Learn more →Where the commercial demand is, and which gaps you can win.
Learn more →Pages written to outrank what currently sits above you.
Learn more →Earned authority, with nothing that risks a penalty.
Learn more →FAQ
A little, and less than most agencies imply. Core Web Vitals are a confirmed ranking signal but a light one — you will not outrank a better page by being faster. The real return is conversion: the same traffic, more completed orders. If someone sells you speed work primarily as a ranking fix, they are overselling it.
You should, and it will help. A caching plugin handles maybe a third of the problem — the repeat-visit case. It cannot resize your images correctly per breakpoint, remove CSS your template never uses, defer a chat widget, or fix queries in a theme. On WooCommerce it often cannot cache the pages that matter most, because carts are per-session. That is where the rest of the work lives.
Both can be true. Server response is one number in a chain of many — a fast server can still deliver a page that takes six seconds to become usable because of what happens in the browser afterwards. The audit separates the two, so you know whether you have a hosting problem or a front-end problem before you pay to migrate.
This is the right thing to worry about — aggressive optimisation breaks carts, and it is the most common way speed work goes wrong. Everything is built on a staging copy, and the full path is tested before deployment: add to cart, checkout, payment, order confirmation and the confirmation email. A backup is taken first and rollback takes under a minute.
Usually not. Most sites I see have far more to gain from the front end than from a migration, and moving hosts carries its own risk. If your server response really is the ceiling, the audit will say so with the measurement attached — and I will tell you that rather than sell you optimisation that cannot work.
Sometimes it is, and that is an uncomfortable answer because rebuilding is expensive. Heavy page builders can be optimised a long way — usually to a passing score, occasionally not. The audit tells you how far your current setup can realistically go, so you can decide whether to optimise it or budget for a rebuild. I would rather you knew that before spending on either.
Until someone adds a new plugin, a tracking pixel or an unoptimised hero image — which in practice is a few months on an active site. You get a written note of what will erode the gains. If you ship changes regularly, ongoing monitoring is worth more than paying for the same optimisation again next year.
Next step
A full waterfall and Core Web Vitals analysis in 48 hours, with a prioritised fix list and the expected gain on each. The fee is credited if you continue.