Largest Contentful Paint
The main image or heading rendering late. We remove render-blocking CSS and JavaScript, preload what matters, right-size and modernise images, and cut the server response time underneath it all.
Grow · Performance
WordPress speed optimization that fixes causes, not scores.
A green score in a testing tool is not the same as a fast site for the people using it. We work from field data, find what is actually costing you load time, and fix it at the source — so the improvement survives the next plugin update. That is what our WordPress speed optimization work is built to fix.
- Measured with real-user field data, not just lab scores
- Fixes at the source — not another caching plugin on top
- Before and after numbers you can show your board
Core Web Vitals — after rebuild
Field data
98
- LCP 4.8s → 0.9s
- INP 410ms → 88ms
- CLS 0.31 → 0.02
Typical result from a full optimization engagement.
The problem
When businesses come to us for WordPress speed optimization.
The score is green but users disagree
Lab tools test one page, on one connection, from one location, with an empty cache. Your customers arrive on mobile data with a full plugin stack running. Field data tells a very different story to a lab score.
Fast until somebody logs in
Page caching makes the homepage fly and does nothing for cart, checkout, My Account or any logged-in session. The pages closest to revenue are the ones caching cannot touch.
The speed plugin made it worse
Aggressive minification broke the layout, so half the optimisations got switched back off. Now there are three caching plugins fighting each other and nobody remembers which settings matter.
It got slow again in three months
Someone optimised images once and moved on. Then the database grew, revisions piled up, two plugins were added and the gains quietly disappeared. Speed without guardrails does not hold.
How it works
How it actually runs.
-
Field data
Real-user metrics first, so we optimise what your visitors actually experience.
-
Diagnose
Waterfall, server timing, database profiling and a cost-per-plugin breakdown.
-
Prioritise
Ranked by impact against effort, so the biggest wins land in the first week.
-
Fix
Applied on staging and reviewed, so nothing breaks in pursuit of a metric.
-
Verify
Before and after on the same pages, same conditions, with field data confirming it.
-
Guard
Budgets and monitoring so the gains do not quietly erode over the next quarter.
Results
What the work produced.
MediaOne Marketing
A homepage rebuild, and the 68-second save
The homepage was hand-written Tailwind inside code blocks, which broke on mobile and could not be edited by anyone but a developer. Partway through rebuilding it, every page save started timing out — and the newest thing on the site was our work. Rebuilt the homepage as proper Elementor widgets, every value a control so the team can edit it. Then benchmarked each plugin in isolation rather than guessing: the save…
68s → 1.5s
Elementor save time
1 of 14
plugins was the cause
Omni HRM
A consultancy losing people before the page arrived
An HR consultancy whose site had grown slow enough that visitors were leaving during the load. The usual advice at that point is to install a caching plugin and hope. Measured the load path first and fixed what was actually costing the time, rather than layering a cache over the problem and calling the number that came out of it a result.
Capabilities
The WordPress speed optimization stack we work in.
Measurement
- Core Web Vitals
- CrUX field data
- Lighthouse
- WebPageTest
- Search Console
- Real User Monitoring
- Query Monitor
Front end
- Critical CSS
- Script deferral
- Font loading
- WebP & AVIF
- Responsive images
- Lazy loading
- Preload & preconnect
Server & caching
- Redis object cache
- Varnish
- Full-page caching
- CDN
- PHP tuning
- HTTP/2 & HTTP/3
- Edge rules
Database
- Index tuning
- Slow query log
- Autoload cleanup
- Transient management
- Revision pruning
- HPOS order tables
Engagement
Three ways this usually runs.
Performance audit
Fixed fee
A written report with field and lab data, a cost-per-plugin breakdown, and a prioritised list of fixes ranked by impact against effort.
- 1–2 weeks
- No obligation to continue
- Yours to take elsewhere
Optimization sprint
Fixed price after audit
We implement the prioritised fixes on staging, verify each one against the same pages and conditions, then launch with before-and-after numbers documented.
- Dated milestone plan
- Verified on staging first
- Before/after report
Performance retainer
Monthly
Monitoring, performance budgets and a set number of hours each month, so new plugins and new content do not quietly undo the work.
- Rolling monthly
- Regression alerts
- Cancel any time
Questions
WordPress speed optimization questions, answered plainly.
If your WordPress speed optimization question is not covered here, send us the details and we will reply with a straight answer.
Why is my PageSpeed score green but the site still feels slow?
Because a lab score tests one page from one location with an empty cache, while your visitors arrive on real devices and real connections. Google ranks on field data from actual Chrome users, not on the lab score. We always start from field data, which is why our before-and-after numbers reflect what people genuinely experience.
Will a caching plugin fix this on its own?
Rarely. A caching plugin helps anonymous visitors on cacheable pages, and does nothing for cart, checkout, My Account or any logged-in session. It also cannot fix slow database queries, oversized images or a plugin loading its assets on every page. Caching is one layer of the answer, not the answer.
How much faster will my site actually get?
It depends entirely on what is wrong, which is why we audit before quoting. Sites carrying years of plugin accumulation and an untuned database usually see the largest gains. Sites already on good hosting with a lean stack see smaller but still meaningful ones. The audit tells you the realistic ceiling before you commit to the work.
Will speed work break my site's design?
Not the way we do it. Aggressive minification and asset combining are exactly what breaks layouts, which is why so many people switch their optimisations back off. Everything is applied and reviewed on staging first, and we would rather leave a smaller gain on the table than ship a broken page.
Do I need to change hosting?
Sometimes, and we will say so plainly if server response time is the bottleneck. Often it is not — a well-tuned site on mid-range hosting beats a bloated one on expensive hosting. We measure the server contribution specifically so the recommendation is based on your numbers, not a referral fee.
How do you stop it getting slow again?
Performance budgets and monitoring. We document what each page should weigh and how fast it should render, then alert on regressions so a new plugin or an unoptimised image gets caught in days rather than discovered a quarter later. The retainer exists for exactly this reason.
Where does WordPress speed optimization start?
With measurement, not plugins. Real-user field data tells you which metric is failing and on which pages — and the answer is frequently the database or the theme rather than anything a caching plugin touches.
The platform itself is documented at wordpress.org.
Will a caching plugin fix it?
It will help, and it will also hide the cause. We fix the source first so the improvement holds when the cache is cold.
Start here
Start your WordPress speed optimization project.
The more you can tell us, the more useful our first reply will be. No sales sequence — one of the people who would actually do the work reads this.
- We read it and look at your site
- You get a written reply with our honest read
- If it fits, we scope it properly
Prefer email? hello@dotance.com