How much does WordPress speed optimisation cost?

WordPress speed optimisation usually costs $150–$400 for a one-off audit, $300–$1,200 for a full code-level fix on a typical business site, and $50–$250 a month for an ongoing performance retainer (CreedAlly, Faisal Yaqoob). WooCommerce stores and heavy page-builder sites cost more, often $500–$2,000 for the fix (CreedAlly, Faisal Yaqoob). Page count barely matters. What sets the price is whatever is actually slowing the site down: hosting, theme, plugins, images or third-party scripts.

I've been building and fixing WordPress sites for 4+ years, and in my view the costliest speed job is usually the second one, after someone has already paid for the wrong fix. So this post covers what each price tier should buy you, and when you shouldn't pay for a tune-up at all.

How much does WordPress speed optimisation cost in 2026?

Short version: about $150–$400 for an audit, $300–$1,200 for a full code-level fix, $500–$2,000 for WooCommerce and $50–$250 a month for a retainer.

Those ranges come from two 2026 pricing guides, CreedAlly and Faisal Yaqoob, and agency price pages say much the same. SpeedyGo puts a full package for a straightforward WordPress site at $500–$1,500, rising to $1,500–$5,000 for complex layouts, custom code or large catalogues. Webaloha puts plain WordPress at $300–$1,000 and WordPress with Elementor at $400–$1,200.

Sources: CreedAlly, Faisal Yaqoob.

The audit and the settings-level tune-up share a price band because they're often sold as alternatives at the same price point: one tells you what's wrong, the other applies standard settings without much diagnosis.

What do speed optimisation providers actually charge?

Published prices run from $30 Fiverr gigs to $2,500 fixed packages, and most hourly rates sit between $50 and $150. Here's what some providers actually list:

The cheap end is mostly plugin configuration. That has some value, but you can do a lot of it yourself with a caching plugin like WP Rocket, which costs $59 a year. At the higher end you're paying for someone to find the real cause and change code without breaking things.

Look at how many of those providers charge separately for Core Web Vitals, too. A better PageSpeed score and passing Core Web Vitals are different jobs, so check which one is in the quote.

What should a one-off speed audit include?

A $150–$400 audit should give you real-user field data, a server response time check, root causes for your key pages and a fix list ranked by impact. It's worth paying for when you don't know why the site is slow, or when you want a second opinion before signing off a bigger quote. Look for:

• Field data, not just a lab score. Google judges Core Web Vitals on real visitors over 28 days. Good means LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1 for at least 75% of visits.
• Server response time (TTFB) checked first. If the host is slow, nothing you do on the page will fix it.
• Root causes, page by page. The home page, a key service or product page, and on a WooCommerce store the cart and checkout.
• A ranked fix list with rough effort for each item, so you can choose what to pay for.

You can get a decent first pass for free. Paste your PageSpeed Insights or Lighthouse report into my Page Speed Fix Planner. It tells you which Core Web Vitals pass or fail, what's causing each one, and the fixes ranked by impact and effort for your platform. If the plan comes back short and simple, you may not need a paid audit at all.

What does a full speed fix include for the money?

This is the tier most businesses need. For $300–$1,200 you should get work on all three Core Web Vitals (LCP, CLS and INP), plus caching, images, plugin bloat and a hosting check, with measurements before and after. On a standard site that means:

• LCP (loading): a properly sized, preloaded hero image, critical CSS inlined, render-blocking CSS and JavaScript deferred, fonts self-hosted and preloaded.
• CLS (layout shift): width and height set on images and embeds, space reserved for banners, cookie bars and ads, fonts that don't jump on load.
• INP (responsiveness): heavy JavaScript delayed or removed, and chat widgets, sliders and Google Tag Manager containers trimmed back.
• Caching: page caching, browser caching, a CDN, and object caching (Redis) on dynamic sites.
• Images: WebP or AVIF, correct sizes, lazy loading below the fold only.
• Plugin bloat: a plugin audit that removes or replaces slow plugins, plus a database clean-up of autoloaded options, transients and revisions.
• Hosting: a PHP version check, server settings and a straight answer on whether the host is the bottleneck.

I've written up the how-to side separately, so I won't repeat it here: fixing Core Web Vitals on WordPress and why WooCommerce stores get slow. If you can follow those yourself, you save the fee. If you can't, or you can't afford to break checkout, that's what you're paying a developer for.

What should an ongoing speed retainer cover?

$50–$250 a month (CreedAlly) should buy Core Web Vitals monitoring, updates tested on staging first, a monthly look at your key pages and a few hours for small fixes. You need it because sites slow down again. One new plugin, a marketing script dropped into Google Tag Manager or a theme update can undo a one-off fix within a few months. Elsner puts larger corporate sites that need performance tuning and formal reporting at $200–$500 a month.

Speed is normally one line in a wider WordPress maintenance retainer, next to backups, security and uptime, so price them together.

What makes WordPress speed optimisation cost more?

Six things push the price up:

• WooCommerce. Cart, checkout and account pages can't be page-cached, so the work moves to database queries, object caching and checkout scripts. Every change has to be tested against real orders.
• Page builders. Elementor and similar builders output deep, heavy markup. You can trim it, but only so far. I've covered how far in speeding up an Elementor site without rebuilding it.
• A low starting point. A site scoring 30 takes more hours than one scoring 70 (CreedAlly).
• Weak hosting. Cheap shared hosting caps how good TTFB can get. Sometimes the right fix is simply moving to a better host.
• Plugins you can't remove. If a slow plugin runs part of the business, it needs custom work around it or a replacement.
• Third-party scripts. Chat, reviews, heatmaps and ad pixels are often the real INP problem. Removing them means a conversation with marketing, not just a code change.

When does a rebuild beat a speed tune-up?

Rebuild when the theme or page builder is the bottleneck, or when you're due a redesign in the next 12 months anyway. If the foundations are sound and the problems are settings, images and a few bad plugins, a tune-up is fine. If you'd be paying someone to fight the theme, that money is better spent on a rebuild.

Signs a rebuild is the better spend:

• The theme or builder is the bottleneck, and you've already paid for one tune-up that didn't hold.
• You're planning a redesign anyway. Paying for a full speed fix on a site you'll replace next year rarely makes sense.
• The site is stacked with plugins doing jobs a few lines of custom code could handle.

Some of my best speed results came from builds, not tune-ups. The Nortek LED WooCommerce store, which I built from Figma on a custom Oxygen theme, reported 35% faster load times after launch. Orilite, built with custom PHP templates and ACF, reported 25% faster loads. For Wow Vastra, a UK fashion boutique on WooCommerce, I built a new homepage with a currency switcher and worldwide checkout, and it loads in 1.5 seconds. A rebuild costs more up front, but you don't end up paying for speed again a year later.

Is paying for speed optimisation worth it?

For most business sites that make money, yes. Faster mobile pages lift conversions, and there's decent data on it. Deloitte's Milliseconds Make Millions study found that a 0.1-second improvement in mobile site speed lifted retail conversions by 8.4% and average order value by 9.2%. Older Google research found 53% of mobile visits are abandoned when a page takes longer than three seconds to load. Core Web Vitals also feed Google's page experience signals, though content and relevance still count for more in rankings.

If your site is a five-page brochure with little traffic, don't overspend. A settings-level tune-up at the bottom of the range, or a weekend with a caching plugin, may be all it needs.

What should you ask a developer before you pay?

Ask how they'll measure results, which fixes are code and which are plugin settings, and how they'll test forms, tracking and checkout and roll back if something breaks.

• What will you measure before and after, and on which pages?
• Do you check server response time before touching plugins?
• Which fixes are code changes and which are plugin settings?
• How will you test forms, tracking and checkout afterwards?
• Do you work on a staging copy, and what's the rollback plan?
• What should we avoid doing afterwards so the site stays fast?

If most of the answers boil down to "we install our plugin stack", you're paying for something you could do yourself.

Your next step

Run your home page through PageSpeed Insights, then paste the report into the free Page Speed Fix Planner. You'll see which Core Web Vitals fail and what's behind them before you spend anything. If the plan calls for code-level work, a WooCommerce fix or a rebuild, have a look at my technical SEO and Core Web Vitals service or send me your report and I'll tell you which tier you actually need.