WordPress Performance
Make WordPress fast on the pages that actually take traffic.
Core Web Vitals work across images, caching, assets, plugins, the database, theme overhead and hosting limits, measured on the URLs that matter commercially.
Measure first
A cache plugin is not a performance programme.
WordPress gets slow when templates query too much, images are unbounded, plugins add scripts to every page, and hosting cannot hold the peak. Speed work here starts with a baseline on commercial URLs, then attacks theme overhead, assets, caching, the database and the plugin list. Core Web Vitals are the language we report in. Hosting limits are named when they are the ceiling, because no front-end pass will invent capacity the server does not have.
Typical constraints
Slowness is usually a stack of small costs, not one villain.
- 01Core Web Vitals fail on templates that take the most traffic, not only on a lab home page.
- 02Images and third-party scripts were never given a budget.
- 03Caching is misconfigured or fighting a page builder and a pile of plugins.
- 04The database and theme queries have grown expensive as content accumulated.
- 05Hosting was chosen for price, and it now caps every other improvement.
- 06Each previous fix added another performance plugin instead of removing the cause.
How speed work is sequenced
Baseline, cost, change, recheck.
We do not start by installing a new optimisation plugin. The first output is a picture of where time is spent.
01
Measurement baseline
Field and lab data on agreed templates, plus a list of third-party tags and known host constraints.
02
Template and query cost
What the theme and WordPress queries do on category, product, article and landing templates.
03
Asset and cache work
Images, CSS, JavaScript and cache rules are changed against a budget, not against a plugin marketing page.
04
Plugin and theme debt
Scripts and features that do not earn their cost are removed or isolated. Some debt needs a rebuild.
05
Hosting limits
When the server or plan is the ceiling, that is stated. We will not pretend front-end tweaks can hide it.
06
Recheck and hold
The same URLs are measured after changes. Remaining risks and the habits that would regress them are documented.
What you receive
A measured pass with changes you can keep.
We report field and lab data on agreed URLs. Recommendations that require a rebuild or a host change are labelled as such.
01
Baseline on commercial URLs
Core Web Vitals and the main template costs on the pages that actually receive traffic and campaigns.
02
Image and asset plan
Formats, sizing, lazy loading and script budgets, including third-party tags that marketing will not give up lightly.
03
Caching and hosting review
Page, object and CDN caching checked against the host. Limits that only a plan change can fix are written down.
04
Plugin, theme and query pass
Unused plugins, expensive theme templates and database work that should not run on every request.
05
Recheck and hold notes
After changes, the same URLs are measured again, with a short list of habits that would undo the work.
When this is the right entry
Speed work is for sites that already have a job and are failing it.
- A WordPress site failing Core Web Vitals on templates that take organic or paid traffic.
- A WooCommerce catalogue that became slow as products and plugins accumulated.
- A marketing team blocked from campaigns because landing pages take too long to become usable.
- A host or CDN change that never produced the improvement someone sold.
- A site about to be redesigned, where performance debt should be named before new templates copy it.
What we judge
The useful result is a faster commercial URL and a stack that stays that way.
Clearer Core Web Vitals picture
The team knows which templates fail, why, and which fixes are in reach without a rebuild.
Less accidental cost on every request
Images, scripts, queries and plugins are reduced to what the page actually needs.
Hosting named as a constraint when it is
If the plan cannot hold the peak, that is an explicit recommendation, not a hidden caveat.
A hold list for the next campaign
Marketing and development know which additions would put the weight back on the page.
Related work
Speed work is evidenced with before-and-after measurements you already own.
We will not invent percentage gains on this page. When a performance engagement is cleared, it is listed in Work with the URLs and method, not a vanity score.
Published case studies will appear here when they are cleared.
Related services
Work that usually sits beside this.
- Technical SEOCrawlability, indexation, architecture and performance work that search engines can trust.
- WordPress SEOWordPress-specific architecture, templates and editorial workflows for durable rankings.
- Custom WordPress DevelopmentBespoke themes, blocks and integrations built around your product and operations.
Questions
Buying questions, answered directly.
No. Scores depend on hosting, third-party tags, content and the templates we are allowed to change. We commit to a baseline, a sequenced pass and a recheck on the agreed URLs.
Next move
Measure the slow pages before buying another plugin.
Share the URLs that take traffic and the host you are on. We will say whether a performance pass, a host change or a template rebuild is the constraint.