M
marc dumont ·
Menu
Status
Available for new work
Working with
🇬🇧 UK · 🇺🇸 US · 🇪🇺 Europe
13+y in web development
Elsewhere
© 2026 Marc Dumont
Service · 04 · Performance
Available

Performance and Core Web Vitals.

Slow sites hurt rankings, conversions, and the patience of the person trying to use them. I diagnose what's actually slowing your WordPress site down, then fix the things that move the needle. Real measurements before and after, written up so you know exactly what changed.

Typical scope
10–40 hours
Timeline
2–4 weeks
Rate
$55 / hour
Engagement
Hourly, scoped per audit

What's included.

A performance engagement starts with measurement, not assumptions. Most are structured as an audit followed by a fix phase, so you can decide whether to commission the fixes once you've seen the diagnosis. Most projects include:

  • Baseline measurement using Lighthouse, PageSpeed Insights, GTmetrix, and WebPageTest. Captures real Core Web Vitals (LCP, FID, CLS) plus the underlying metrics that explain them.
  • Real User Monitoring data review where available (from GA4, Google Search Console, or any RUM tool you have installed)
  • Identification of render-blocking resources, including scripts, fonts, and stylesheets loading in the wrong order or at the wrong priority
  • Image and asset optimisation assessment, including format choices (AVIF, WebP), lazy loading behaviour, and asset sizing
  • Plugin audit, identifying plugins that are slow, unnecessary, or duplicating work
  • Database optimisation where bloat or slow queries are part of the problem
  • Server, host, and CDN configuration review, including caching layers, HTTP/2 or HTTP/3, and compression settings
  • WooCommerce-specific tuning for stores (WooCommerce performance is its own discipline)
  • Implementation of fixes, prioritised by impact-to-effort ratio
  • Post-fix measurement using the same tools as the baseline, so the improvement is documented
  • Written summary, with what was changed, why, and what to watch for going forward

The audit phase often surfaces things that won't be fixed in the same engagement (server changes, design changes, content changes). The summary calls those out so you know what's left on the table.

What's not included.

Being clear about what's outside the scope is part of giving you a realistic estimate. A performance engagement doesn't include:

  • Full site rebuilds. If the site's underlying architecture is the problem, no amount of caching will fix it. I'll tell you if that's the diagnosis, and we can talk about whether a rebuild makes more sense.
  • Design changes for performance reasons. I can flag where design decisions are hurting performance (heavy hero videos, oversized images), but design changes belong with your designer.
  • Hosting migrations. If your host is part of the problem, migration is a separate engagement (covered under Bespoke or Integrations depending on scope).
  • Long-term performance monitoring. Ongoing performance tracking is part of the Support and maintenance service.
  • SEO content strategy. Performance affects rankings, but content strategy is its own thing and belongs with someone whose full-time job it is.

How an audit runs.

Most performance engagements run in two phases: audit, then fix. You can commission the audit alone if you want a diagnosis without committing to the work. The shape looks roughly like this:

01

Brief

A short conversation about what you're seeing (slow page loads, poor Core Web Vitals scores, a Google Search Console warning, a drop in conversions). No estimate yet; the diagnosis comes first.

02

Baseline

I run the site through a battery of measurement tools, looking at both lab data (Lighthouse, GTmetrix) and real-world data (Core Web Vitals from Search Console, RUM data if available). I document the current state in detail.

03

Diagnosis

A written summary of what's actually slowing the site down, ranked by impact. Sometimes the answer is one thing (a single bloated plugin, a misconfigured cache); sometimes it's a dozen small things compounding.

04

Estimate for fixes

Once you've seen the diagnosis, I give you a realistic estimate for the fix work, prioritised by impact-to-effort ratio. You can choose to fix everything, or just the items that move the needle most.

05

Fixes and measurement

I implement the agreed fixes, then re-run the same measurements to document the improvement. The final summary tells you what changed and what's still on the table.

Scope, honestly.

Most performance engagements run 10–40 hours and 2–4 weeks from kick-off to delivery. The number depends on:

  • How bad the starting point is. A site that's mostly fine but missing a few wins is quick. A site that's been accumulating plugins, themes, and quick fixes for five years takes longer to untangle.
  • How much rebuilding the fixes require. Tweaking caching settings is fast. Replacing a slow page builder, refactoring custom code, or restructuring database queries takes meaningful time.
  • Whether the host is helping or hurting. Some hosts have caching, CDN, and image optimisation built in. Others don't, and getting those services in place is part of the work.
  • How aggressive you want to be. A reasonable improvement (good Core Web Vitals scores, decent loading times) is usually achievable in 10–20 hours. Going from 'good' to 'excellent' usually takes longer and yields diminishing returns.

I bill hourly at $55 / hour (GBP / USD / ZAR via the currency switcher), with a time log you can audit at any point. I don't promise specific percentage gains in advance. Real results depend on the starting point. What I can promise is honest measurement before and after, and clear recommendations on what's worth fixing.

What I measure and tune with.

Performance work uses a different set of tools to standard development. Common ones:

Measurement

PageSpeed Insights · GTmetrix · WebPageTest · Lighthouse · Chrome DevTools · Query Monitor · New Relic · Google Search Console · GA4

Caching and performance plugins

WP Rocket · LiteSpeed Cache · FlyingPress · W3 Total Cache · Perfmatters · Asset CleanUp · Autoptimize

Image optimisation

ShortPixel · Smush · Imagify · EWWW Image Optimizer · native AVIF / WebP delivery

CDN and edge

Cloudflare (CDN, APO, Workers, Polish) · BunnyCDN · KeyCDN

Database and code

WP-CLI for database optimisation · custom query review · plugin audit and consolidation · render-blocking script and font tuning

Hosting and server

reviewing host caching layers, PHP versions, server-level settings · recommending host changes where the host is the bottleneck

The full directory of tools I work with sits on the Tools page, where each has its own breakdown.

Specific questions.

All services FAQ →

Four questions that come up specifically about performance work. General FAQs on cost, timeline, and pricing sit on the Services page.

Can you guarantee a specific Core Web Vitals score?
No. I won't commit to a specific number before measuring, because the answer depends entirely on what I find. What I will commit to is honest measurement before and after, and clear recommendations on what's worth fixing. In practice, most engagements produce significant improvements; I just won't put a percentage on it up front.
Will optimising my site break anything?
It shouldn't, but the risk is real, especially on heavily customised sites. I work in a staging environment, test the full site after each significant change, and keep rollback plans ready. If something does break in production, fixing it is part of the engagement.
Can you fix Core Web Vitals warnings in Google Search Console?
Usually yes. Search Console reports Core Web Vitals based on real user data, so warnings tend to point at genuine field-level issues. I diagnose the underlying cause (often a mix of slow images, render-blocking scripts, and layout shifts) and fix what's actionable.
Do you handle performance for WooCommerce stores?
Yes, and WooCommerce performance is its own thing. The standard caching and optimisation rules don't apply cleanly to dynamic pages like cart, checkout, and account dashboards. I tune WooCommerce stores differently to content sites, with object caching, careful cache exclusions, and store-specific settings.

Related work.

Case study coming soon

A performance engagement for an e-commerce client

A real performance audit and fix engagement, with the measurements, the fixes, and what mattered most. Detailed write-up in progress.

Notify me when it's ready →
Get started

Site running slowly?

A short message about what you're seeing (slow loading, poor scores, a Search Console warning) is enough for me to give you a first response. If you've already run a Lighthouse or GTmetrix report, even better. Share the link.

Other services.

All services →
SERVICE / 01
Available

Bespoke WordPress development

Custom WordPress builds in Elementor, designed around how your business actually works. I handle the full path from design translation to launch, including the customisation, the ACF fields, and the bits no one tells you about until you're three weeks in.

Typical 40–120 hrs
Learn more →
SERVICE / 02
Available

WooCommerce and online stores

WooCommerce builds for B2C and B2B clients across the UK, US and Europe. Product catalogues, payment gateways, tax configuration, shipping logic. All set up properly so you're not fighting the platform six months in.

B2C and B2B
Learn more →
SERVICE / 03
Project-based

Integrations and custom work

The work that doesn't fit neatly into a template. CRM hookups, payment platforms, booking systems, headless setups, custom plugins, and bespoke functionality. Usually the kind of work that's been sitting in your backlog because no one wanted to touch it.

Scoped per engagement
Learn more →
SERVICE / 05
Monthly

Support and maintenance

Updates, backups, security monitoring, and a person who picks up when something breaks. For clients who'd rather get on with their business than learn what a PHP error means.

Monthly retainer
Learn more →
WordPressElementorWooCommerceLong-term partnershipsTransparent hourly pricingWordPressElementorWooCommerceLong-term partnershipsTransparent hourly pricing