// services / speed and rendering
WordPress speed optimization service fixed from the server up
Most slow WordPress sites aren't missing a plugin. The time goes somewhere specific: the server, the delivery, the images, the scripts or the checkout. Book a call and I'll name the layer your load time goes into, measured on your own URLs.
// what it costs
- US$149Deep audit and growth report, one off, on Upwork
- US$999Audit and fixes, one off, on Upwork
- US$299 or US$750month to month, with a report every month
Audits from US$149, audit and fixes from US$999, and month to month plans at US$299 for maintenance or US$750 for growth. Booked and paid on Upwork.
What does a WordPress speed optimization service fix?
A WordPress speed optimization service fixes the layers under the page: how fast the server answers, what's cached, how the HTML travels, which images and scripts the browser waits for, and what WooCommerce does on pages nobody can cache. That's WordPress performance optimization in full, not a plugin install.
On a brochure site a page cache hides most of it. On a store it can't, because cart, checkout and logged-in customers bypass the cache. Google's three graded metrics get their own diagnosis on Core Web Vitals.
How would I diagnose this on your site?
This is the order I check it in on a WordPress or WooCommerce site, before changing anything. You'll get the findings back in writing, each tied to a number in your own Search Console.
See my full diagnosis process- i.
Uncached time to first byte on named URLs
Over a second means the fix starts on the server, and Query Monitor attributes that time to the plugin or theme that spent it.
- ii.
The same URLs through the cache
If cached and uncached numbers match, the page cache isn't serving at all.
- iii.
The waterfall on a throttled phone
Which request holds up the first paint: a font, a render blocking stylesheet, a slider script or the LCP image arriving late.
Checkout crawling while the homepage looks fine?
Book a call on UpworkWhere do your load times actually go?
A slow page loses its time in one of six places, and the symptom usually names it. When it's the first tap that feels stuck, what's slowing Interaction to Next Paint walks through the long tasks behind it.
| What you notice | The layer | What I check |
|---|---|---|
| Every page is slow, even simple ones | Server and database | Cached and uncached TTFB, PHP version, autoloaded options |
| Blank for a moment, then everything appears | Critical path | Render blocking resources, Google Fonts, and which element is the Largest Contentful Paint |
| Images pop in late on phones | Images and delivery | Served size against displayed size, WebP or AVIF, lazy loading rules |
| Text jumps around while it loads | Layout stability | Missing width and height, late fonts and injected banners, which is Cumulative Layout Shift |
| The first tap feels stuck | Runtime and third party | Long tasks, chat widgets, tag manager, delayed scripts landing together |
| Fast homepage, slow checkout | WooCommerce | Cart fragments, uncacheable pages, admin-ajax calls from plugins |
Which layer is actually slowing your WordPress site?
Naming the layer is the job. The fix after that is usually one setting, one exclusion or one rebuilt asset.
Server and database
PHP version and workers, a page cache that actually serves, whether that's a cache plugin like WP Rocket or LiteSpeed Cache or your host's own, Redis for what it can't cache, and the autoloaded options read on every request.
Delivery
Gzip or Brotli compression, HTTP/2, browser caching headers on static files, a content delivery network for distant visitors, and redirect chains that add a round trip before anything loads.
Critical path
Render blocking CSS and JavaScript, unused CSS removed, critical CSS inlined, self-hosted Google Fonts with a sensible font-display, and fetchpriority on the LCP image, with a preload only when the image isn't in the HTML. A slow Largest Contentful Paint usually traces back here.
Assets and third party
Image optimization to WebP or AVIF at real dimensions, lazy loading everything except the hero, and third party scripts like chat, ads and analytics kept off the critical path, which also cuts the HTTP request count.
Is your hosting or your plugins the real problem?
Usually both, and uncached response time says which matters more. If a bare staging install still takes over a second to generate, no front-end work will make it load faster, and I'll tell you your hosting provider's plan is the limit before you pay me to polish around it. If the bare install is quick and yours isn't, the weight's in the theme or the plugin list.
What database optimization is actually worth doing?
Database optimization gets oversold. Deleting old revisions won't speed up a page that loads one post; the bloat that matters is read on every request.
| Where the bloat sits | Why it costs speed | Safe to clean? |
|---|---|---|
| Autoloaded options in wp_options | Loaded on every request, cached or not | Yes, once each row's owner is confirmed |
| Expired transients | They pile up without an object cache | Yes, they're meant to go |
| Action Scheduler tables | Old jobs run to hundreds of thousands of rows | Completed and failed ones, yes |
Why does a WooCommerce checkout stay slow?
Cart, checkout and account pages skip the page cache by design, so every visit runs PHP and its database queries. Cart fragments add an uncacheable request to every page showing a cart count, plugin admin-ajax calls pile on top, and on shared hosting with few PHP workers a handful of shoppers at checkout can queue everyone else.
What's in WordPress speed work, and what sits elsewhere?
Builder layouts slowing a template are diagnosed on page builder SEO. No case study on this site measures speed work, so I'm not showing one.
Included
- Uncached and cached response time on named URLs
- Page cache, object cache, compression and CDN, with WooCommerce exclusions
- Images, fonts and scripts rebuilt off the critical path
- Database cleanup that's safe to run
Not included
- Deep single-metric LCP, INP or CLS work past the green threshold, which runs as Core Web Vitals work
- Rebuilding pages off a page builder
- Uptime monitoring and maintenance plans
What happens after you book a WordPress speed optimization service?
- i.
Named URLs timed first
The homepage, a category, a product and the cart, uncached and cached, so the call starts from load times, not adjectives.
- ii.
A fixed scope on Upwork
The layers at fault decide the work, and you sign off on it before anything's touched.
- iii.
Changes on staging, one layer at a time
Forms, cart and checkout get tested before anything goes live.
- iv.
The same URLs, timed again
Before and after on identical requests, with the field data read once it's caught up.
What else do people ask about WordPress speed?
Why is my WordPress site suddenly slow?
Something changed: a plugin update, a new slider or chat widget, a host move, or traffic outgrowing the plan. I compare uncached server time against the front-end waterfall to see which side changed, then date it against your deploys.
Do I need a WordPress speed optimization service, or will a plugin do it?
A cache plugin gets a simple site part of the way. Once there's a store, a page builder or a layer nobody can name, someone has to read the waterfall and the server timings and decide what to change. Moving hosts rarely replaces that.
How much do WordPress speed optimization services cost?
A page speed optimization service is priced by which layers are at fault, and checkout testing adds time, so there's no price here. You'll get a fixed quote on Upwork after the first timings.
Can you guarantee a load time?
Not a load time in seconds, because hosting and third-party scripts move it. What the terms guarantee in writing is this: speed projects ship with Core Web Vitals in the green on mobile, and if they aren't, I keep fixing at no charge until they are. Rankings aren't guaranteed.
How long does WordPress speed optimization take?
The timings on named URLs come first and don't take long. The fixes depend on which layers are at fault, and a store's checkout testing adds time, so the quote on Upwork carries a committed date for your site.
Is WP Rocket worth it?
On hosting with no page cache of its own, a plugin like WP Rocket is the quickest way to get one, and it's paid. On a LiteSpeed server, LiteSpeed Cache does that job for free. Neither fixes a slow uncached response, and two page caches on one site add conflicts, not speed.
Does a PageSpeed score of 100 matter?
Not for Google. It's one Lighthouse lab run ranking systems don't use, and chasing the last points often breaks something a customer needed.
Three posts cover the parts of this job people ask about most: how I find out why a WordPress site is slow before touching a plugin, clearing every cache layer when a change won't show, and putting Cloudflare in front of WordPress without hurting search. The rest are in the speed posts.
Is WordPress slow where it counts?
Send me the URL. I'll time your real templates cached and uncached, find where the seconds go, whether that's the server, the cache, images or a plugin, and fix them in that order.
Book a call on Upwork