WordPress performance optimization: how I took a site from 6 seconds to under 1

Straight answer: WordPress performance optimization starts with measuring, not with installing plugins. I run a full audit of Core Web Vitals, the load waterfall, DOM weight, TTFB and plugin overhead, then apply the highest-impact changes first: server-level caching, code splitting, removing render-blocking resources and CDN delivery. The result is a site that is green on mobile, with every change documented and verifiable in PageSpeed Insights.

What optimization is (and what it is not)

Optimization is understanding exactly what is holding your site back and attacking that, in order, without breaking anything along the way.

It is not blindly compressing images, not disabling things you will not be able to restore, and not chasing a 100 in a lab that does not resemble a phone on 4G with a limited data plan.

Every extra second of load time costs 7% of conversions. Not negotiable.

How I do it: my process in 4 phases

1. Real audit (day 1)

I measure your site with PageSpeed Insights and with field tools, not just the lab. I review the load waterfall to see what is blocking first render, how heavy your DOM is, and which plugins run on every page. I come out with a report of the problems ordered by real impact.

2. Server-level caching (days 2-3)

I work on caching where it actually pays off: on the server, with Redis or Nginx, not in PHP. I set rules so static assets are served from cache and dynamic content is generated when it should be. I verify nothing that needs to stay live gets frozen.

3. Code splitting and removing render-blocking (days 3-4)

I break up the files so the browser does not wait for the CSS and JS of sections further down the page. I load scripts deferred where the content allows it. I remove the styles that are being injected needlessly.

4. Delivery and verification (days 4-5)

I put the site behind a CDN, configure static asset caching and hand you the before-and-after report with real metrics. Anything that cannot be measured does not go in the report.

What your project includes

Full audit: Core Web Vitals, waterfall, plugins and TTFB
Server-level caching (Redis/Nginx)
Code splitting, lazy loading and end of render-blocking
Global CDN delivery
Before-and-after report with real metrics

Starting at USD 390. If your site also needs a clean redevelopment, we look at that as a separate project.

Why this is different from what you get elsewhere

I do not install generic cache plugins. One of those caches everything indiscriminately and sooner or later serves a visitor a stale version of your content, which is worse than having a slow site.

Every optimization I apply is surgical, documented and traceable. You know exactly what I changed, why I changed it and which metric moved. If something breaks, it reverts.

On top of that, I optimize for real connections. A 95 in Google’s Mountain View lab means nothing if your customer is in Santo Domingo on mobile data: there, the weight of the first response is what matters, and that is where I work.

Frequently asked questions

How long does it take? Three to five business days, depending on site size and how neglected it has been.

Do I need to change hosting? Not necessarily. If your current hosting does not allow server-level caching, I tell you before starting and quote it separately. I am not going to promise an optimization your infrastructure cannot support.

What if I already have a cache plugin installed? I audit it. If it is well configured it stays, if it is not it gets removed. What matters is the measured result, not the plugin brand.

Is content lost during optimization? No. Optimization does not touch content or data, only how it is served. And everything is backed up before starting.

Is your WordPress taking too long to load? Send me the URL and I will tell you what is holding it back and how much is on the table. No commitment, and I install nothing.