Slow sites lose the customer before the page finishes loading.
Three things make a site slow, almost always in this order: images nobody resized, a page builder loading code you never use, and plugins doing work on every visit. I fix those, harden the site while I am in there, and show you the numbers before and after.
Everything included, written out.
- A real audit first — measured on a throttled mobile connection, not on my fast laptop
- Every image resized, re-encoded to WebP and lazy-loaded below the fold
- Unused plugins removed, and the ones that stay loaded only where they are needed
- Caching and compression configured properly at the server
- Fonts self-hosted and preloaded, so text paints immediately
- Layout shift fixed — no more buttons moving as the page settles
- SSL, security headers, and login protection against brute force
- Automatic backups configured and one restore tested in front of you
- A written before-and-after report with the actual figures
- A full redesign — this is fixing the site you have
- Rewriting content or restructuring pages for SEO
- Hosting costs, if your current host is the real bottleneck
- Ongoing monitoring beyond the first 30 days
Need any of these? Say so on WhatsApp and I price it before we start. Nothing is added to your invoice afterwards.
The businesses I do this for most.
Sites built on a page builder
Elementor and its cousins load a great deal you never asked for. This is the most common job I do.
Anyone told to "improve Core Web Vitals"
Google reports LCP, INP and CLS. I fix the three, then show you the report going green.
Older sites that got slower
Five years of plugins and untouched images. Nothing is wrong, exactly — it just accumulated.
Businesses with rural customers
On one bar of signal, a heavy site never finishes loading, and that lost customer appears in no report.
Running today.
Four steps, all of them on WhatsApp.
- 01 · MESSAGE
You send a WhatsApp
Tell me what the business does. A price and a date come back in under ten minutes. No call, no form, no deck.
- 02 · BUILD
I build it
50% up front, then I work. Nothing you have already sent gets asked for twice.
- 03 · REVIEW
You see it on a link
Changes over WhatsApp, as a list or a voice note. Most jobs need one round.
- 04 · LAUNCH
It goes live
Balance on approval. Every login and source file is handed to you.
What people ask before they message me.
What will actually change?
You get a number before and a number after, measured the same way. If I cannot improve it meaningfully, I tell you that before taking money rather than after.
Will you break my site?
A full backup comes first, and I test a restore. Changes go on a staging copy where that is possible, and nothing goes live until you have seen it.
My host says the site is fine. Who is right?
Hosts measure their server, which is usually fine. Your customer measures a phone on mobile data, which is usually not. The second number is the one that matters.
Is this a one-off or ongoing?
One-off. I fix it, hand you the report, and tell you plainly what to avoid so it does not creep back — mostly: stop installing plugins you do not need.
Send me your web address. I will tell you what is slowing it down.
No deposit is taken from a message, and there is no call unless you want one. If I think you do not need this yet, I will say so.
