<WordPress Speed Optimization/>

Core Web Vitals work for agency clients, measured on real user data, not a lab score screenshot.

A slow client site is your problem before it is theirs. It costs conversions, it costs rankings, and it is the first thing a competing agency points at in a pitch. Most WordPress sites are slow for boring, fixable reasons: images nobody sized, scripts loading on every page for one feature, a database full of years of revisions, and caching that was switched on and never tuned. We find which of those apply to the site in front of us, fix them on staging, and give you a before and after you can show the client. All of it under your brand, with an NDA signed first.

// what's included

What we fix

Core Web Vitals

Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, worked on the pages that actually get traffic rather than the homepage alone.

Full Performance Audit

A written report with what is slow, why, what it costs in seconds, and what fixing it involves. Plain enough to forward to the client without editing.

Script & CSS Cleanup

Render blocking removed, unused CSS and JavaScript identified, third party scripts deferred or dropped where they earn nothing.

Image Pipeline

Correct sizing, modern formats, lazy loading below the fold, and priority hints on the hero image so the main content paints first.

Database & Query Work

Revision and transient cleanup, slow query identification, indexes where they help, and object caching for sites doing real work on every request.

Caching Setup

Page, object and browser caching configured for the site's actual behaviour, including the pages that must never be cached, like carts and account areas.

WooCommerce Performance

Cart fragment handling, product query optimisation and checkout speed, measured on product and checkout pages where store revenue is decided.

Before & After Reporting

Field data and lab data captured on both sides of the work, so you can show the client a result rather than describe one.

// how it works

How an optimisation runs

You Send the Site

URL, hosting details and any known problem pages. We do not need client contact, just access and your account manager's version of what the complaint is.

We Audit & Report

We measure real user data and lab data, profile the server, and write up what is slow and why. You get the report and a fixed quote for the fixes before anything is touched.

You Approve the Scope

You decide what gets done and at what pace, so the work fits the client's budget. Nothing is changed on a live site without your sign off.

We Implement on Staging

Fixes go on a copy first, then get tested for breakage: forms, checkout, sliders, popups and anything else that depends on scripts we moved.

We Deploy & Measure Again

Changes go live, results are measured again, and you get the before and after. Field data keeps improving for about four weeks afterwards, which we explain in the report.

// standards

How we work on performance

Real user field data is the target, not just a lab score
Every change tested on staging before it reaches a live site
A written record of what changed, so future problems are traceable
Server response time measured separately from front end work
Product, checkout and landing pages measured, not only the homepage
Caching configured and tuned to the site rather than switched on and left
Clear reporting on where the biggest gains are available, including hosting and plugins
Report written to be handed straight to the client or your own developers

// guarantee

Working with us

NDA signed before any work starts
No mb3techs branding on reports or in the site
We never contact your client, at any point
Scope confirmed the same day you send the brief
30 days of bug fixes after the work, included

Start a project

// faq

Speed optimisation questions

We give you measured targets rather than a number picked at random. Most sites we take on move into the green on Core Web Vitals for real users. We audit first and share the realistic gain for that specific site, so you can quote your client with confidence and show them the numbers afterwards.

They measure two different things, and knowing the difference is useful. PageSpeed Insights runs a lab test on a throttled connection, while Google ranks on field data from real visitors, which is what Core Web Vitals measures. We work to the field data and explain it clearly, so you can walk the client through the results.

Every change is made on staging first and tested before it goes near the live site. Caching, script deferral and CSS work all get checked against checkouts, forms and sliders, and you receive a written list of what changed, so the work stays transparent and easy to follow.

Yes, and stores need a different approach. Cart pages cannot be cached the way a brochure page can, cart fragments cause most of the slowness, and product pages carry more queries. Optimising a store on its homepage alone tells you nothing useful.

It is usually a combination: image sizes, render blocking scripts, the plugin stack, database queries, caching setup and the hosting environment. We identify which of those apply to the site in front of us and fix the causes, so the improvement holds rather than fading after a few weeks.

Sometimes hosting is part of the picture, and we will show you the data either way. Server response time is measured separately from the front end work, so you can see exactly where the gains are available. Where a hosting move makes sense, we recommend suitable options and can handle the migration for you.

An audit takes a couple of days. Implementation is usually a few days to a couple of weeks depending on the site and the testing involved. Field data in Search Console reflects the change over about 28 days, which is helpful to share with the client upfront so they know when to look.

The audit is a fixed price. Implementation is quoted from what the audit finds, so every line is based on measured data. If you would prefer the audit alone and want your own team to implement it, the report is written to be handed straight to a developer.

// next step

Send us a slow site and we will tell you why it is slow

You get a written audit with the causes, the likely gain from each fix, and a fixed quote for the work, so you can present the client with a clear plan and a measurable result.

Get a fixed quote