WordPress Speed Optimization
MY REFERENCES
A slow site loses on two fronts: visitors leave before the page opens, and Google keeps a slow site lower in rankings too. If you’re running ads, the damage doubles — the money you paid for the click goes to waste because the page never loaded.
The most common mistake in speed optimization is jumping straight to installing a caching plugin and tweaking settings. Caching is the last step. First you need to measure where the slowness is actually coming from, because you can’t paper over a server-side slowdown with caching.
Measure first, then intervene
The places to check, in order: the server’s first response time (TTFB), the state of the database, plugin load, the number of files generated by the theme and page builder, image size and format, and third-party scripts (ad pixels, chat widgets, fonts).
Every site has its bottleneck in a different place. On some sites, a 200-line plugin holds up the entire page; on others, the database hasn’t been cleaned in years, so every query slows down. Intervening without measuring risks breaking something that was already working.
A concrete example: my own site
The day I wrote this page, I looked at my own site. The database was 1,078 MB — an absurd number for a site with 11 pages and 6 posts. I found two sources: 3,713 page revisions that WordPress had kept (each one carrying a full copy of the page’s Elementor data), and a security plugin’s 178,577-line audit log.
I cleaned both out, optimized the tables, and added a setting to cap the revision count so it wouldn’t bloat again. Result: the database dropped to 54.7 MB, and the first response time went from 0.32 seconds to 0.08 seconds. Without installing a single plugin, without touching the design at all.
Making it stick
Speed optimization isn’t a one-time job. A new plugin gets installed, images get uploaded, and the database bloats again. That’s why when I finish the job, I don’t just make it fast — I also put limits in place that keep it from slowing down again.
At delivery, I provide written before/after measurements, what was changed and why, and what you should watch out for going forward. “I sped it up” means nothing without measurements to back it up.
How do we start? First, we talk about what you want and what’s realistic. If it works for you, I send the scope and price in writing, then we start. You can reach out via the contact page.
Frequently Asked Questions
Which caching plugin is best?
That’s the wrong question. A well-configured free plugin beats a poorly configured paid one. Also, if your problem isn’t actually solved by caching, it doesn’t matter which plugin you install. Measure first, then choose the tool.
If my site gets faster, will my rankings go up?
Speed alone doesn’t raise rankings; it’s one of many signals for Google. But slowness actively hurts, and it directly lowers your conversion rate. The clearest return on speed optimization isn’t in rankings — it’s getting more customers out of the same traffic.
Will I need to delete my plugins?
Some of them, probably yes — but I measure how much load each one brings first, I don’t guess and delete. If two plugins do the same job, or if a plugin has been sitting unused for years, we review those together. The decision is yours.
Can changes be made while my site is running — is there risk?
I take a file and database backup before every change, make changes one at a time, and check the site after each step. I don’t make bulk changes, so if a problem comes up, it’s clear which change caused it. A rollback path is ready at every step.
How do I work?
Work-hour packages
Tell me about your website and what you need on WhatsApp or by phone; we agree on a work block of somewhere between 5 and 40 hours and I start doing what is needed. What you get is not a calendar window — it is net working hours spent directly on your business. I can use 40 hours working three days straight, or deliberately spread it out and finish it over a year — whatever the work calls for. I do not spend my time estimating how long something will take, I spend it doing the work; every hour I spend has a lasting result on your site. We keep going for as long as you find it useful.
Why not monthly?
Is 40 hours a week?
On a fixed monthly fee both sides are watching the wrong thing: you watch a fixed cost, the other side watches how many more contracts like this they can line up. Working by the hour puts us both in front of the same thing — the real value of the work that got done. I know not having an upfront answer to "how much will this cost in total?" is the natural cost of this model. But instead of paying a fixed fee for months to a setup that is not producing results, you only pay for the qualified time spent on your work — and you see exactly where that time went, start to finish. That is why my clients keep coming back.