Too much loaded per page
A theme shipping every stylesheet and script it owns on every page, whether the page uses them or not.
[ WordPress / WordPress Speed Optimization ]
A perfect score on a synthetic test means nothing if the site feels slow on a phone. I work against the metrics your visitors actually experience, and against what search engines actually measure.
Free report first · Fixed price · Measured before and after
[ What makes it slow ]
Installing another caching plugin hides some of this. It does not remove any of it.
A theme shipping every stylesheet and script it owns on every page, whether the page uses them or not.
Unindexed lookups and bloated tables, usually made worse by years of accumulated revisions and expired transients.
Full-resolution uploads served to phones in formats a decade out of date.
Chat widgets, tag managers and tracking pixels blocking the page while they load.
Underpowered or badly tuned hosting, where the first byte arrives late no matter how good the front end is.
Content jumping as images and fonts arrive, which is both a ranking factor and genuinely irritating.
[ How it works ]
Real-user data and lab tests across templates and devices. You get a report showing exactly where the time goes, and what each fix is worth in seconds.
Worked in order of impact per hour: server response first, then payload, then rendering, then third parties.
Re-measured on the same tests and devices, with before-and-after numbers. Real-user metrics reflect the change over the following weeks.
[ What actually changes ]
Ordered by how much time each typically saves per hour of work, which is rarely the order plugin guides suggest.
[ Example engagement ]
A content-heavy site with a multipurpose theme, no object caching and full-size images. Server response and page weight addressed first, third-party scripts last.
Illustrative example of a typical engagement. Figures vary with the state of your systems and are not a guarantee of a specific outcome.
[ Free · 48 hours ]
I test your key templates on real devices and send back where the time goes, with the projected gain for each fix. No obligation to proceed.
[ Pricing ]
Tell me the number you have to work with. I'll tell you honestly what's achievable within it — and if it isn't enough, I'll say so before we start rather than halfway through.
Scope agreed in writing, price agreed in writing, before any work starts. No hourly creep and no invoice you haven't already approved.
For ongoing work — maintenance, monitoring, updates and small changes. Month to month, cancel whenever, no minimum term.
For a single bug or a short task where writing a full scope would cost more than simply doing the work.
Budget too tight for the whole thing? I'll often suggest doing the highest-value part first and the rest later, rather than doing all of it badly.
[ Questions ]
Possibly, but that is not the goal and I will not chase it at the expense of the site. Real-world load time and Core Web Vitals are what affect visitors and rankings; a synthetic score is a diagnostic tool, not the target.
Sometimes. If server response time is the bottleneck, no amount of front-end work fixes it. I will tell you plainly if hosting is the constraint, and what a move would gain you.
Work is done on staging and each change verified. Aggressive optimizations that risk breaking functionality are only applied with your agreement, and everything is reversible.
Where it is the right tool, yes — configured properly rather than installed and forgotten. Much of the gain usually comes from the server and the page itself, which no plugin can fix for you.
It is a real but modest ranking factor. The larger commercial effect is on conversion: slow pages lose visitors before they see anything, and that shows up in revenue before it shows up in rankings.
[ Related services ]
[ Let's talk ]
Describe the problem in a few lines and you'll get a real reply from the person who'd do the work โ same working day, no discovery call required.